fix: messages for "org list metadata-types"

Author: jshackell-sfdc

messages/list.metadata.md

@@ -2,6 +2,8 @@
 
 Use this command to identify individual components in your manifest file or if you want a high-level view of particular metadata types in your org. For example, you can use this command to return a list of names of all the CustomObject or Layout components in your org, then use this information in a retrieve command that returns a subset of these components.
 
+The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API Functions permission.
+
 # summary
 
 List the metadata components and properties of a specified type.
@@ -22,7 +24,7 @@ List the metadata components and properties of a specified type.
 
 # flags.api-version.summary
 
-API version to use; default is the latest API version.
+API version to use; default is the most recent API version.
 
 # flags.output-file.summary
 

messages/metadata-types.md

@@ -1,47 +1,37 @@
 # description
 
-Use this information to identify the syntax needed for a <name> element in package.xml. The most recent API version is
-the default, or you can specify an older version.
+The information includes Apex classes and triggers, custom objects, custom fields on standard objects, tab sets that define an app, and many other metadata types. Use this information to identify the syntax needed for a <name> element in a manifest file (package.xml).
 
-The default target username is the admin user for the default scratch org. The username must have the Modify All Data
-permission or the Modify Metadata permission (Beta). For more information about permissions, see Salesforce Help.
+The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API Functions permission.
 
 # summary
 
-display details about the metadata types enabled for your org
+Display details about the metadata types that are enabled for your org.
 
 # examples
 
-- $ <%= config.bin %> <%= command.id %> -a 43.0
+- Display information about all known and enabled metadata types in the org with alias "my-dev-org" using API version 57.0:
 
-- $ <%= config.bin %> <%= command.id %> -o [email protected]
+  $ <%= config.bin %> <%= command.id %> --api-version 57.0 --target-org my-dev-org
 
-- $ <%= config.bin %> <%= command.id %> -f /path/to/outputfilename.txt
+- Display only the metadata types that aren't yet supported by Salesforce CLI in your default org and write the results to the specified file:
 
-- $ <%= config.bin %> <%= command.id %> -o [email protected] -f /path/to/outputfilename.txt
+  $ <%= config.bin %> <%= command.id %> --output-file /path/to/outputfilename.txt --filter-known
 
-# flags.api-version
+# flags.api-version.summary
 
-API version to use
+API version to use; default is the most recent API version.
 
-# flags.output-file
+# flags.output-file.summary
 
-path to the file where results are stored
+Pathname of the file in which to write the results.
 
-# flags.filterknown
+# flags.filter-known.summary
 
-filter metadata known by the CLI
-
-# flagsLong.apiversion
-
-The API version to use. The default is the latest API version
+Filter the known metadata types from the result to display only the types not yet fully supported by Salesforce CLI.
 
-# flagsLong.output-file
-
-The path to the file where the results of the command are stored. Directing the output to a file makes it easier to
-extract relevant information for your package.xml manifest file. The default output destination is the console.
+filter metadata known by the CLI
 
-# flagsLong.filterknown
+# flags.output-file.description
 
-Filters all the known metadata from the result such that all that is left are the types not yet fully supported by the
-CLI.
+Directing the output to a file makes it easier to extract relevant information for your package.xml manifest file. The default output destination is the terminal or command window console.

src/commands/org/list/metadata-types.ts

@@ -23,23 +23,22 @@ export class ListMetadataTypes extends SfCommand<DescribeMetadataResult> {
     'api-version': Flags.orgApiVersion({
       aliases: ['apiversion', 'a'],
       deprecateAliases: true,
-      summary: messages.getMessage('flags.api-version'),
+      summary: messages.getMessage('flags.api-version.summary'),
     }),
     loglevel,
     'target-org': requiredOrgFlagWithDeprecations,
     'output-file': Flags.file({
       aliases: ['resultfile'],
       deprecateAliases: true,
       char: 'f',
-      summary: messages.getMessage('flags.output-file'),
-      description: messages.getMessage('flagsLong.output-file'),
+      summary: messages.getMessage('flags.output-file.summary'),
+      description: messages.getMessage('flags.output-file.description'),
     }),
     'filter-known': Flags.boolean({
       aliases: ['filterknown'],
       deprecateAliases: true,
       char: 'k',
-      summary: messages.getMessage('flags.filterknown'),
-      description: messages.getMessage('flagsLong.filterknown'),
+      summary: messages.getMessage('flags.filter-known.summary'),
       hidden: true,
     }),
   };