Merge branch 'priyshet/networkCloudCLIupdates' of github.com:priyamshet/azure-docs-pr-pshet into priyshet/networkCloudCLIupdates

Author: priya shet

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

@@ -102,7 +102,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 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).
+Sample output looks something like below. It prints the top 4K 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====

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

@@ -66,6 +66,8 @@ Specifying `--no-wait --debug` options in az cli command will result in the exec
 | METRIC_TO_ENABLE_1                    | Optional metric1 that have been chosen to be enabled in addition to the default metrics            |
 | METRIC_TO_ENABLE_2                    | Optional metric2 that have been chosen to be enabled in addition to the default metrics            |
 
+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
 
 After a metrics configuration is created, it can be retrieved using a `az rest` command:
@@ -81,9 +83,7 @@ This command will return a JSON representation of the metrics configuration.
 
 ## Updating a metrics configuration
 
-Much like the creation of a metrics configuration, an update can be performed to change the configuration. 
-
-This command is used to patch properties of the provided metrics configuration of cluster, or update the tags assigned to the metrics configuration. 
+Much like the creation of a metrics configuration, an update can be performed to change the configuration or update the tags assigned to the metrics configuration. 
 
 ```azurecli
 az networkcloud cluster metricsconfiguration update \
@@ -96,7 +96,7 @@ az networkcloud cluster metricsconfiguration update \
 
 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).
+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.
 
 ## Deleting a metrics configuration
 
@@ -108,5 +108,6 @@ az networkcloud cluster metricsconfiguration delete \
  --resource-group "<RESOURCE_GROUP>"
 ```
 
-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).
+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.
+
 

articles/operator-nexus/howto-configure-cluster.md

@@ -152,9 +152,11 @@ az networkcloud cluster deploy \
   --name "$CLUSTER_NAME" \
   --resource-group "$CLUSTER_RESOURCE_GROUP" \
   --subscription "$SUBSCRIPTION_ID" \
-  --no-wait
+  --no-wait --debug 
 ```
 
+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).
+
 ## Cluster deployment validation
 
 View the status of the cluster: