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

priya shet · priya shet · commit 00e58ceed5a9 · 2023-04-15T16:59:12.000-05:00
diff --git a/articles/operator-nexus/howto-cluster-metrics-configuration-management.md b/articles/operator-nexus/howto-cluster-metrics-configuration-management.md
@@ -14,12 +14,12 @@ ms.custom: template-how-to
 When the user deploys a Cluster, a standard set of metrics are enabled for collection. For the list of metrics, see
 [List of Metrics Collected](List-of-metrics-collected.md).
 
-Users can't control the behavior (enable or disable) for collection of these included standard metrics. Though, users can control the collection of some optional metrics that aren't part of the link to the list. To enable this experience, users will have to create and update a MetricsConfiguration resource for a cluster. By default, creation of this MetricsConfiguration resource doesn't change the collection of metrics. User will have to update the resource to enable or disable these optional metrics collection.  
+Users can't control the behavior (enable or disable) for collection of these included standard metrics. Though, users can control the collection of some optional metrics that aren't part of the link to the list. To enable this experience, users have to create and update a MetricsConfiguration resource for a cluster. By default, creation of this MetricsConfiguration resource doesn't change the collection of metrics. User has to update the resource to enable or disable these optional metrics collection.  
 
 > [!NOTE] 
 > * For a cluster, at max, only one MetricsConfiguration resource can be created.
 > * Users need to create a MetricsConfiguration resource to check a list of optional metrics that can be controlled. 
-> * Deletion of the MetricsConfiguration resource will result in the standard set of metrics being restored.
+> * Deletion of the MetricsConfiguration resource results in the standard set of metrics being restored.
 
 ## How to manage cluster metrics configuration
 
@@ -48,25 +48,25 @@ az networkcloud cluster metricsconfiguration create \
 > * The default metrics collection interval for standard set of metrics is set to every 5 minutes. Changing the `collectionInterval` will also impact the collection frequency for default standard metrics.
 > * There can be only one set of metrics configuration defined per cluster. The resource is created with the name `default`.
 
-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.
+Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
 
 ### Metrics Configuration elements
 
 | Parameter name                        | Description                                                                                        |
 | --------------------------------------| -------------------------------------------------------------------------------------------------- |
 | CLUSTER                               | Resource Name of Cluster                                                                           |
-| LOCATION                              | The Azure Region where the Cluster will be deployed                                                | 
+| LOCATION                              | The Azure Region where the Cluster is deployed                                                     | 
 | CLUSTER_EXTENDED_LOCATION_ID          | The Cluster extended Location from Azure portal                                                    |
 | COLLECTION_INTERVAL                   | The collection frequency for default standard metrics                                              |
 | RESOURCE_GROUP                        | The Cluster resource group name                                                                    |
 | TAG_KEY1                              | Optional tag1 to pass to Cluster create                                                            |
 | TAG_VALUE1                            | Optional tag1 value to pass to Cluster Create                                                      |
 | TAG_KEY2                              | Optional tag2 to pass to Cluster create                                                            |
 | TAG_VALUE2                            | Optional tag2 value to pass to Cluster create                                                      |
-| 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            |
+| METRIC_TO_ENABLE_1                    | Optional metric1 that is enabled in addition to the default metrics            |
+| METRIC_TO_ENABLE_2                    | Optional metric2 that is 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.
+Specifying `--no-wait --debug` options in az cli command results 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 show \
  --resource-group "<RESOURCE_GROUP>"
 ```
 
-This command will return a JSON representation of the metrics configuration.
+This command returns a JSON representation of the metrics configuration.
 
 ## Updating a metrics configuration
 
@@ -96,18 +96,18 @@ az networkcloud cluster metricsconfiguration update \
 
 The `collection-interval` can be updated independently of `enabled-metrics` list. Omit fields that aren't being changed.
 
-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.
+Specifying `--no-wait --debug` options in az cli command results 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
 
-Deletion of the metrics configuration will return the cluster to an unaltered configuration. To delete a metrics configuration, use the below command:
+Deletion of the metrics configuration returns the cluster to an unaltered configuration. To delete a metrics configuration, use the below command:
 
 ```azurecli
 az networkcloud cluster metricsconfiguration delete \
  --cluster-name "<CLUSTER>" \
  --resource-group "<RESOURCE_GROUP>"
 ```
 
-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.
+Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
 
 
diff --git a/articles/operator-nexus/howto-configure-cluster.md b/articles/operator-nexus/howto-configure-cluster.md
@@ -70,7 +70,7 @@ You can instead create a Cluster with ARM template/parameter files in
 | Parameter name            | Description                                                                                                           |
 | ------------------------- | --------------------------------------------------------------------------------------------------------------------- |
 | CLUSTER_NAME              | Resource Name of the Cluster                                                                                          |
-| LOCATION                  | The Azure Region where the Cluster will be deployed                                                                   |
+| LOCATION                  | The Azure Region where the Cluster is deployed                                                                  |
 | CL_NAME                   | The Cluster Manager Custom Location from Azure portal                                                                 |
 | CLUSTER_RG                | The cluster resource group name                                                                                       |
 | LAW_ID                    | Log Analytics Workspace ID for the Cluster                                                                            |
@@ -110,7 +110,7 @@ You can instead create a Cluster with ARM template/parameter files in
 
 ### Cluster validation
 
-A successful Operator Nexus Cluster creation will result in the creation of an AKS cluster
+A successful Operator Nexus Cluster creation results in the creation of an AKS cluster
 inside your subscription. The cluster ID, cluster provisioning state and
 deployment state are returned as a result of a successful `cluster create`.
 
@@ -136,7 +136,7 @@ Cluster create Logs can be viewed in the following locations:
 Once a Cluster has been created, the deploy cluster action can be triggered.
 The deploy Cluster action creates the bootstrap image and deploys the Cluster.
 
-Deploy Cluster will initiate a sequence of events to occur in the Cluster Manager
+Deploy Cluster initiates a sequence of events to occur in the Cluster Manager
 
 1.  Validation of the cluster/rack properties
 2.  Generation of a bootable image for the ephemeral bootstrap cluster
