fix: edit messages

Author: jshackell-sfdc

messages/convert.mdapi.md

@@ -8,6 +8,8 @@ To use Salesforce CLI to work with components that you retrieved via Metadata AP
 
 To convert files from the source format back to the metadata format, run "<%= config.bin %> project convert source".
 
+To convert multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --manifest and --source-dir.
+
 # examples
 
 - Convert metadata formatted files in the specified directory into source formatted files; writes converted files to your default package directory:
@@ -32,11 +34,11 @@ File path to manifest (package.xml) of metadata types to convert.
 
 # flags.metadata-dir.summary
 
-Comma-separated list of paths to the local metadata files to convert.
+Root of directory or zip file of metadata formatted files to convert.
 
 # flags.metadata.summary
 
-Comma-separated list of metadata component names to convert.
+Metadata component names to convert.
 
 # flags.manifest.description
 

messages/convert.source.md

@@ -10,6 +10,8 @@ To convert Metadata API–formatted files into the source format, run "<%= confi
 
 To specify a package name that includes spaces, enclose the name in single quotes.
 
+To convert multiple components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --manifest and --source-dir.
+
 # examples
 
 - Convert source-formatted files in the specified directory into metadata-formatted files; writes converted files into a new directory:
@@ -38,11 +40,11 @@ Path to the manifest (package.xml) file that specifies the metadata types to con
 
 # flags.source-dir.summary
 
-Comma-separated list of paths to the local source files to convert.
+Paths to the local source files to convert.
 
 # flags.metadata.summary
 
-Comma-separated list of metadata component names to convert.
+Metadata component names to convert.
 
 # flags.manifest.description
 

messages/delete.source.md

@@ -8,6 +8,8 @@ Use this command to delete components from orgs that don’t have source trackin
 
 When you run this command, both the local source file and the metadata component in the org are deleted.
 
+To delete multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --manifest and --source-dir.
+
 # examples
 
 - Delete all local Apex source files and all Apex classes from the org with alias "my-scratch":
@@ -32,11 +34,11 @@ When you run this command, both the local source file and the metadata component
 
 # flags.source-dir.summary
 
-Comma-separated list of source file paths to delete.
+Source file paths to delete.
 
 # flags.metadata.summary
 
-Comma-separated list of names of metadata components to delete.
+Metadata components to delete.
 
 # flags.no-prompt.summary
 

messages/list.ignored.md

@@ -1,16 +1,28 @@
+# summary
+
+Check your local project package directories for forceignored files.
+
 # description
 
-check your local project package directories for forceignored files
+When deploying or retrieving metadata between your local project and an org, you can specify the source files you want to exclude with a .forceignore file. The .forceignore file structure mimics the .gitignore structure. Each line in .forceignore specifies a pattern that corresponds to one or more files. The files typically represent metadata components, but can be any files you want to exclude, such as LWC configuration JSON files or tests.
 
 # examples
 
-- $ <%= config.bin %> <%= command.id %>
+- List all the files in all package directories that are ignored:
+
+  <%= config.bin %> <%= command.id %>
+
+- List all the files in a specific directory that are ignored:
+
+  <%= config.bin %> <%= command.id %> --source-dir force-app
+
+- Check if a particular file is ignored:
 
-- $ <%= config.bin %> <%= command.id %> --source-dir force-app
+  <%= config.bin %> <%= command.id %> --source-dir package.xml
 
-# flags.source-dir
+# flags.source-dir.summary
 
-file or directory of files that the command checks for foreceignored files
+File or directory of files that the command checks for foreceignored files.
 
 # invalidSourceDir
 

messages/manifest.create.md

@@ -17,11 +17,13 @@ See https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/met
 
 Use --manifest-name to specify a custom name for the generated manifest if the pre-defined ones don’t suit your needs. You can specify either --manifest-type or --manifest-name, but not both.
 
+To include multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --include-packages and --source-dir.
+
 # examples
 
-- Create a manifest for deploying or retrieving all Apex classes:
+- Create a manifest for deploying or retrieving all Apex classes and custom objects:
 
-  $ <%= config.bin %> <%= command.id %> --metadata ApexClass
+  $ <%= config.bin %> <%= command.id %> --metadata ApexClass --metadata CustomObject
 
 - Create a manifest for deleting the specified Apex class:
 
@@ -37,7 +39,7 @@ Use --manifest-name to specify a custom name for the generated manifest if the p
 
 # flags.include-packages.summary
 
-Comma-separated list of package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in packages is ignored.
+Package types (managed, unlocked) whose metadata is included in the manifest; by default, metadata in packages is ignored.
 
 # flags.from-org.summary
 
@@ -57,11 +59,11 @@ Directory to save the created manifest.
 
 # flags.source-dir.summary
 
-Comma-separated list of paths to the local source files to include in the manifest.
+Paths to the local source files to include in the manifest.
 
 # flags.metadata.summary
 
-Comma-separated list of names of metadata components to include in the manifest.
+Names of metadata components to include in the manifest.
 
 # success
 

src/commands/project/list/ignored.ts

@@ -18,7 +18,7 @@ export type SourceIgnoredResults = {
 };
 
 export class Ignored extends SfCommand<SourceIgnoredResults> {
-  public static readonly summary = messages.getMessage('description');
+  public static readonly summary = messages.getMessage('summary');
   public static readonly description = messages.getMessage('description');
   public static readonly examples = messages.getMessages('examples');
   public static readonly requiresProject = true;
@@ -29,7 +29,7 @@ export class Ignored extends SfCommand<SourceIgnoredResults> {
       char: 'p',
       aliases: ['sourcepath'],
       deprecateAliases: true,
-      summary: messages.getMessage('flags.source-dir'),
+      summary: messages.getMessage('flags.source-dir.summary'),
     }),
   };