Acrolinx and style fixes

Author: denrea

articles/operator-nexus/TOC.yml

@@ -13,7 +13,7 @@
       href: concepts-compute.md
     - name: Storage overview
       href: concepts-storage.md
-    - name: Cluster Deployment
+    - name: Cluster deployment
       href: concepts-cluster-deployment-overview.md
     - name: Network Fabric
       expanded: false

articles/operator-nexus/azure-operator-nexus-faq.md

@@ -70,7 +70,7 @@ The Azure Operator Nexus doesn't offer the capability to select specific racks o
 ### In the event of a network disruption between the cluster manager and on-premises servers during deployment, can the process be resumed once connectivity is restored?
 It depends on the cluster's status: if the cluster is failed, it needs to be deleted and redeployed. However, if the cluster is still deploying, it undergoes a reconcile process, allowing the deployment process to continue.
 
-### Does cluster deploy wait for all the computes node provisioned?
+### Does cluster deploy wait for all the compute node provisioned?
 The deployment process will continuously retry the provisioning of compute nodes until all nodes are successfully provisioned. When the cluster reaches the defined threshold, cluster status changes to running. However, the remaining nodes continue undergoing the provisioning process until they too are successfully provisioned.
 
 ## Compute

articles/operator-nexus/concepts-cluster-deployment-overview.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Operator Nexus cluster deployment overview
-description: Get an overview of cluster deployment overview for Azure Operator Nexus.
+description: Get an overview of cluster deployment for Azure Operator Nexus.
 author: sbatchu
 ms.author: sbatchu
 ms.service: azure-operator-nexus
@@ -12,11 +12,11 @@ ms.custom: template-concept
 # Azure Operator Nexus cluster
 Azure Operator Nexus is built on basic constructs like compute servers, storage appliances, and network fabric devices. Azure Operator Nexus cluster represents an on-premises deployment of the platform. The lifecycle of platform-specific resources is dependent on the cluster state.
 
-## Cluster Deployment Overview
+## Cluster deployment overview
 
 During the cluster deployment, cluster undergoes various lifecycle phases, which have specific roles designated to ensure the target state is achieved.
 
-### Hardware Validation Phase:
+### Hardware Validation phase:
 
 Hardware Validation is initiated during the cluster deployment process, assessing the state of hardware components for the machines provided through the Cluster's rack definition. Based on the results of these checks and any user skipped machines, a determination is done on whether sufficient nodes passed and/or are available to meet the thresholds necessary for deployment to continue.
 
@@ -29,7 +29,7 @@ Hardware validation results for a given server are written into the Log Analytic
 
 This article provides instructions on how to check hardware results information [Troubleshoot Hardware validation](troubleshoot-hardware-validation-failure.md)
 
-### Bootstrap Phase:
+### Bootstrap phase:
 
 Once the Hardware Validation is successful, bootstrap image is generated for cluster deploy action on the cluster manager. This image iso URL is used to bootstrap the ephemeral node, which would deploy the target cluster components, which are provisioning the kubernetes control plane (KCP), Nexus Management plane (NMP), and storage appliance. These various states are reflected in the cluster status, which these stages are executed as part of the ephemeral bootstrap workflow.