fix: update messages (#976)

messages/tree.export.md

@@ -46,8 +46,8 @@ Directory in which to generate the JSON files; default is current directory.
 
 # PlanJsonWarning
 
-After Nov 10, 2024, the JSON output for `--plan` will no longer include the `saveRefs` and `resolveRefs` properties.
+Starting on Nov 10, 2024, the JSON output for `--plan` will no longer include the `saveRefs` and `resolveRefs` properties.
 
 # LegacyDeprecation
 
-After Nov 10, 2024, this command will no longer be available. Use `data export tree`.
+Starting on Nov 10, 2024, this command will no longer be available. Use `data export tree` instead.

messages/tree.import.md

@@ -22,9 +22,9 @@ Plan definition file to insert multiple data files.
 
 # flags.plan.description
 
-Unlike the `--files` flag, the files listed in the plan definition file **can** contain more then 200 records. These will be automatically batched to comply with that limit.
+Unlike when you use the `--files` flag, the files listed in the plan definition file **can** contain more then 200 records. When the CLI executes the import, it automatically batches the records to comply with the 200 record limit set by the API.
 
-The file order matters--records with lookups to records in another file should be listed AFTER that file Example: you're loading Account and Contact records, and the contacts have references to those Accounts. The Accounts file should come before the Contacts file.
+The order in which you list the files in the plan definition file matters. Specifically, records with lookups to records in another file should be listed AFTER that file. For example, let's say you're loading Account and Contact records, and the contacts have references to those accounts. Be sure you list the Accounts file before the Contacts file.
 
 The plan definition file has the following schema:
 

src/commands/data/import/tree.ts

@@ -37,6 +37,7 @@ export default class Import extends SfCommand<ImportResult[]> {
     plan: Flags.file({
       char: 'p',
       summary: messages.getMessage('flags.plan.summary'),
+      description: messages.getMessage('flags.plan.description'),
       exactlyOne: ['files', 'plan'],
       exists: true,
     }),