W-21371395: fix: edit the help, add a topic desc for "lightning"

messages/lightning.dev.app.md

@@ -4,7 +4,7 @@ Preview a Lightning Experience app locally and in real-time, without deploying i
 
 # description
 
-Use Local Dev (Beta) to see local changes to your app in a real-time preview that you don't have to deploy or manually refresh. To let you quickly iterate on your Lightning web components (LWCs) and pages, your app preview automatically refreshes when Local Dev detects source code changes.
+Use Local Dev to see local changes to your app in a real-time preview that you don't have to deploy or manually refresh. To let you quickly iterate on your Lightning web components (LWCs) and pages, your app preview automatically refreshes when Local Dev detects source code changes.
 
 When you edit these local files with Local Dev enabled, your org automatically reflects these changes.
 
@@ -17,7 +17,9 @@ To apply any other local changes not listed above, you must deploy them to your
 
 When you make changes directly in your org (like saving new component properties), they're automatically deployed to your live app. To update your local version of the app with those changes, you must retrieve them from your org using the `sf project retrieve start` command.
 
-To learn more about Local Dev enablement, considerations, and limitations, see the Lightning Web Components Developer Guide.
+If you run the command without flags, it displays a list of devices for you to choose from. Then it lists the apps that it found in your local DX project for you to choose. Use the --device or --name flags to bypass the questions. The command also asks if you want to enable Local Dev in your org if it isn't already.
+
+To learn more about Local Dev enablement, considerations, and limitations, see the Lightning Web Components Developer Guide (https://developer.salesforce.com/docs/platform/lwc/guide/get-started-test-components.html).
 
 # flags.name.summary
 
@@ -33,15 +35,15 @@ ID of the mobile device to display the preview if device type is set to `ios` or
 
 # error.fetching.app-id
 
-Unable to determine App Id for %s
+Unable to determine App Id for %s.
 
 # error.device.notfound
 
-Unable to find device %s
+Unable to find device %s.
 
 # error.device.google.play
 
-Google Play devices are not supported. %s is a Google Play device. Please use a Google APIs device instead.
+Google Play devices aren't supported. %s is a Google Play device. Use a Google APIs device instead.
 
 # spinner.device.boot
 
@@ -87,7 +89,9 @@ Note: Your desktop browser requires additional configuration to trust the local
 
 - Preview the default app for the target org "myOrg" in a desktop environment:
   <%= config.bin %> <%= command.id %> --target-org myOrg
+
 - Preview the app "myApp" for the target org "myOrg" in a desktop environment:
   <%= config.bin %> <%= command.id %> --name MyApp --target-org myOrg --device-type desktop
+
 - Preview the default app for target org "myOrg" on an iOS device:
   <%= config.bin %> <%= command.id %> --target-org myOrg --device-type ios --device-id "iPhone 15 Pro Max"

messages/lightning.dev.component.md

@@ -1,6 +1,6 @@
 # summary
 
-[Beta] Preview LWC components in isolation.
+Preview LWC components in isolation.
 
 # description
 
@@ -14,35 +14,38 @@ When running the development server, these changes are immediately reflected:
 - Adding or updating internal component dependencies
 - Modifying static resources used by the component
 
-See the LWC Development Guide for more information about component development best practices and limitations.
+If you run the command without flags, it displays a list of components that it found in your local DX project for you to choose to preview. Use the --name flag to bypass the question. The command also asks if you want to enable Local Dev in your org if it isn't already.
+
+See the LWC Developer Guide for more information about component development best practices and limitations (https://developer.salesforce.com/docs/platform/lwc/guide/get-started-best-practices.html).
 
 # flags.name.summary
 
 Name of a component to preview.
 
 # flags.client-select.summary
 
-Launch component preview without selecting a component
+Launch component preview without selecting a component.
 
 # error.directory
 
-Unable to find components
+Unable to find components.
 
 # error.component
 
-Unable to determine component name
+Unable to determine component name.
 
 # error.component-metadata
 
-Failed to parse component metadata at: %s
+Failed to parse component metadata at: %s.
 
 # error.component-not-found
 
-Unable to find component with name: %s
+Unable to find component with name: %s.
 
 # examples
 
-- Select a component and launch the component preview:
+- Select a component interactively and launch the component preview; use your default org:
   <%= config.bin %> <%= command.id %>
-- Launch component preview for "myComponent":
-  <%= config.bin %> <%= command.id %> --name myComponent
+
+- Launch component preview for "myComponent"; use the org with alias "myscratch":
+  <%= config.bin %> <%= command.id %> --name myComponent --target-org myscratch

messages/lightning.dev.site.md

@@ -1,6 +1,6 @@
 # summary
 
-[Beta] Preview an Experience Builder site locally and in real-time, without deploying it.
+Preview an Experience Builder site locally and in real-time, without deploying it.
 
 # description
 
@@ -15,15 +15,18 @@ When you edit these local files with Local Dev enabled, your org automatically r
 
 To apply any other local changes not listed above, you must deploy them to your org using the `sf project deploy start` command. Then republish your site and restart the server for the Local Dev experience.
 
+If you run the command without flags, it displays a list of Experience Builder sites that it found in your local DX project for you to choose from. Use the --name flag to bypass the question. The command also asks if you want to enable Local Dev in your org if it isn't already.
+
 For more considerations and limitations, see the Lightning Web Components Developer Guide.
 
 # flags.name.summary
 
-Name of the Experience Builder site to preview. It has to match a site name from the current org.
+Name of the Experience Builder site to preview. It must match a site name from the current org.
 
 # examples
 
-- Select a site to preview from the org "myOrg":
+- Select a site to preview from the org with alias "myOrg":
   <%= config.bin %> <%= command.id %> --target-org myOrg
-- Preview the site "Partner Central" from the org "myOrg":
-  <%= config.bin %> <%= command.id %> --name "Partner Central" --target-org myOrg
+
+- Preview the site "Partner Central" from your default org:
+  <%= config.bin %> <%= command.id %> --name "Partner Central" 

package.json

@@ -80,6 +80,7 @@
     "topics": {
       "lightning": {
         "external": true,
+        "description": "Commands to work with Lightning applications.",
         "subtopics": {
           "dev": {
             "description": "Preview applications and sites locally and in real-time, without deploying them."