Apply suggestions from code review

Co-authored-by: Marina Bashtovaya <[email protected]>

Author: priyamshet

articles/operator-nexus/howto-baremetal-run-read.md

@@ -78,13 +78,15 @@ These commands do not require `arguments`:
 
 All other inputs are required. 
 
-Multiple commands can be provided in json format to `--commands` option.  Each `command` specifies command and the arguments.
+Multiple commands can be provided in json format to `--commands` option.
 
 For a command with multiple arguments, provide as a list to `arguments` parameter. See [Azure CLI Shorthand](https://github.com/Azure/azure-cli/blob/dev/doc/shorthand_syntax.md) for instructions on constructing the `--commands` structure.
 
-These commands can be long running so the recommendation is to set `--limit-time-seconds` to at least 600 seconds (10 minutes). The `Debug` option or running multiple extracts might take longer that 10 minutes.
+These commands can be long running so the recommendation is to set `--limit-time-seconds` to at least 600 seconds (10 minutes). Running multiple extracts might take longer that 10 minutes.
 
-This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait` option.
+This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait --debug` options. In that case, follow the instructions on [how to track asynchronous operation](https://learn.microsoft.com/en-us/azure/operator-nexus/howto-track-async-operations-cli).
+
+When an optional argument `--output-directory` is provided, the output result will be downloaded and extracted to the local directory.
 
 ### This example executes the `hostname` command and a `ping` command.
 
@@ -101,7 +103,7 @@ In the response, an HTTP status code of 202 is returned as the operation is perf
 ## Checking command status and viewing output
 
 
-Sample output looks something like this and provides a link to the zipped output file(tar.gz) from the command execution. The tar.gz file name can be used to identify the file in the Storage account of the Cluster Manager resource group.  You can also use the link to directly access the output zip file. Download the output file from storage blob to a local directory by specifying the directory path in the optional argument `--output-directory`.
+Sample output looks something like below. It prints the top 5K characters of the result to the screen for convenience and provides a short-lived link to the storage blob containing the command execution result. You can use the link to download the zipped output file (tar.gz).
 
 ```azurecli
   ====Action Command Output====
@@ -117,7 +119,7 @@ Sample output looks something like this and provides a link to the zipped output
 
   ================================
   Script execution result can be found in storage account:
-  https://cm49vr6vnc6kst.blob.core.windows.net/bmm-run-command-output/a8e0a5fe-3279-46a8-b995-51f2f98a18dd-action-bmmrunreadcmd.tar.gz?se=2023-04-14T06%3A37%3A00Z&sig=ZlN6t%2F534OpmEE545Xie7feHupKSU4v6XYfZTKG6WVo%3D&sp=r&spr=https&sr=b&st=2023-04-14T02%3A37%3A00Z&sv=2019-12-12
+  https://<storage_account_name>.blob.core.windows.net/bmm-run-command-output/a8e0a5fe-3279-46a8-b995-51f2f98a18dd-action-bmmrunreadcmd.tar.gz?se=2023-04-14T06%3A37%3A00Z&sig=XXX&sp=r&spr=https&sr=b&st=2023-04-14T02%3A37%3A00Z&sv=2019-12-12
 ```
 
 See [How To BareMetal Review Output Run-Read](howto-baremetal-review-read-output.md) for instructions on locating the output file in the Storage Account. You can also use the link to directly access the output zip file.

articles/operator-nexus/howto-cluster-metrics-configuration-management.md

@@ -49,7 +49,7 @@ az networkcloud cluster metricsconfiguration create \
 > * There can be only one set of metrics configuration defined per cluster. The resource is created with the name `default`.
 
 
-Specifying `--debug` in az cli command will result in the tracking operation status in the returned command output. This operation status can be queried to monitor the progress of the operation. See: [How-to track asynchronous operations](howto-track-async-operations-cli.md).
+Specifying `--no-wait --debug` options in az cli command will result in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
 
 ## Retrieving a metrics configuration
 
@@ -79,7 +79,7 @@ az networkcloud cluster metricsconfiguration update \
  --resource-group "<RESOURCE_GROUP>"
 ```
 
-The change may include either or both of the updatable fields, `collectionInterval` or `enabledMetrics`. The `collectionInterval` can be updated independently of `enabledMetrics`. Omit fields that aren't being changed.
+The `collection-interval` can be updated independently of `enabled-metrics` list. Omit fields that aren't being changed.
 
 Specifying `--debug` in az cli will result in the tracking operation status in the returned command output. This operation status can be queried to monitor the progress of the operation. See: [How-to track asynchronous operations](howto-track-async-operations-cli.md).