Fix typos and formatting in cluster configuration doc

Author: jmmason70

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

@@ -147,7 +147,7 @@ You can find examples for an 8-Rack 2M16C SKU cluster using these two files:
 
 ### Cluster validation
 
-A successful Operator Nexus Cluster creation results in the creation of a Azure resource
+A successful Operator Nexus Cluster creation results in the creation of an Azure resource
 inside your subscription. The cluster ID, cluster provisioning state, and
 deployment state are returned as a result of a successful `cluster create`.
 
@@ -169,13 +169,13 @@ Cluster create Logs can be viewed in the following locations:
 1. Azure portal Resource/ResourceGroup Activity logs.
 2. Azure CLI with `--debug` flag passed on command-line.
 
-### Set Deployment Thresholds
+### Set deployment thresholds
 
 There are two types of deployment thresholds that can be set on a cluster prior to cluster deployment.  They are `compute-deployment-threshold` and `update-strategy`.
 
-***--compute-deployment-threshold - The validation threshold indicating the allowable failures of compute nodes during environment hardware validation.***
+**--compute-deployment-threshold - The validation threshold indicating the allowable failures of compute nodes during environment hardware validation.**
 
-If `compute-deployment-threshold` is not set, the default are as follows:
+If `compute-deployment-threshold` is not set, the defaults are as follows:
 ```
       "strategyType": "Rack",
       "thresholdType": "PercentSuccess",
@@ -194,7 +194,7 @@ az networkcloud cluster update --name "<clusterName>" /
 --subscription <subscriptionID>
 ```
 
-### Validate update:
+### Validate update
 
 ```
 az networkcloud cluster show --resource-group "<resourceGroup>" --name "<clusterName>" | grep -a3 computeDeploymentThreshold
@@ -207,10 +207,10 @@ az networkcloud cluster show --resource-group "<resourceGroup>" --name "<cluster
     "value": 97
 ```
 
-In this example, if less than 97% of the compute nodes being deployed pass hardware validation, the cluster deployment will fail.  ***NOTE:  All kubernetes control plane (KCP) and nexus management plane (NMP) must pass hardware validation.***  If 97% or more of the compute nodes being deployed pass hardware validation, the cluster deployment will continue to the bootstrap provisioning phase.  During compute bootstrap provisioning, the `update-strategy` (below) is used for compute nodes.
+In this example, if less than 97% of the compute nodes being deployed pass hardware validation, the cluster deployment will fail.  **NOTE:  All kubernetes control plane (KCP) and nexus management plane (NMP) must pass hardware validation.**  If 97% or more of the compute nodes being deployed pass hardware validation, the cluster deployment will continue to the bootstrap provisioning phase.  During compute bootstrap provisioning, the `update-strategy` (below) is used for compute nodes.
 
 
-***--update-strategy - The strategy for updating the cluster indicating the allowable compute node failures during bootstrap provisioning.***
+**--update-strategy - The strategy for updating the cluster indicating the allowable compute node failures during bootstrap provisioning.**
 
 If the customer requests an `update-strategy` threshold that it is different from the default of 80%, you can run the following cluster update command.
 
@@ -222,11 +222,11 @@ threshold-value="<thresholdValue>" wait-time-minutes=<waitTimeBetweenRacks> /
 --subscription <subscriptionID>
 ```
 
-strategy-type can be "Rack" (Rack by Rack) OR "PauseAfterRack" (Wait for customer response to continue)
+The strategy-type can be "Rack" (Rack by Rack) OR "PauseAfterRack" (Wait for customer response to continue).
 
-threshold-type can be "PercentSuccess" OR "CountSuccess"
+The threshold-type can be "PercentSuccess" OR "CountSuccess".
 
-If updateStrategy is not set, the default are as follows:
+If updateStrategy is not set, the defaults are as follows:
 
 ```
       "strategyType": "Rack",
@@ -285,7 +285,8 @@ az networkcloud cluster show --resource-group "<resourceGroup>" /
 
 In this example, if less than 10 compute nodes being provisioned in a rack fail to provision (on a rack by rack basis), the cluster deployment will fail.  If 10 or more of the compute nodes are successfully provisioned, cluster deployment moves on to the next rack of compute nodes.
 
-***NOTE:  Deployment thresholds cannot be changed after cluster deployment has started.***
+>[!NOTE]
+>Deployment thresholds cannot be changed after cluster deployment has started.
 
 
 ## Deploy Cluster