Updated pages based on feedback

Author: matternst7258

articles/operator-nexus/concepts-rack-resiliency.md

@@ -1,5 +1,5 @@
 ---
-title: Operator Nexus Rack Resiliency
+title: Operator Nexus rack resiliency
 description: Document how rack resiliency works in Operator Nexus Near Edge
 ms.topic: article
 ms.date: 01/05/2024
@@ -12,31 +12,31 @@ ms.service: azure-operator-nexus
 
 The Nexus service is engineered to uphold control plane resiliency across various compute rack configurations.
 
-### Instances with three or more compute racks
+## Instances with three or more compute racks
 
 Operator Nexus ensures the availability of three active control plane nodes in instances with three or more compute racks. For configurations exceeding two compute racks, an extra spare node is also maintained. These nodes are strategically distributed across different racks to guarantee control plane resiliency, when possible.
 
 During runtime upgrades, Operator Nexus implements a sequential upgrade of the control plane nodes, thereby preserving resiliency throughout the upgrade process.
 
-Three compute racks
+Three compute racks:
 
 |  Rack 1    | Rack 2  | Rack 3   | 
 |------------|---------|----------|
 | KCP        | KCP    | KCP       |
 | KCP-spare  | MGMT   |  MGMT     |
 
-Four or more compute racks
+Four or more compute racks:
 
 |  Rack 1 | Rack 2  | Rack 3   | Rack 4   |
 |---------|---------|----------|----------|
 | KCP     | KCP     | KCP      | KCP-spare|
 | MGMT    | MGMT    | MGMT     | MGMT     |
 
-### Instances with less than three compute rack
+## Instances with less than three compute racks
 
 Operator Nexus maintains an active control plane node and, if available, a spare control plane instance. For instance, a two-rack configuration has one active Kubernetes Control Plane (KCP) node and one spare node.
 
-Two compute racks
+Two compute racks:
 
 | Rack 1     | Rack 2   |
 |------------|----------|
@@ -46,7 +46,7 @@ Two compute racks
 > [!NOTE] 
 > Operator Nexus supports control plane resiliency in single rack configurations by having three management nodes within the rack. For example, a single rack configuration with three management servers will provide an equivalent number of active control planes to ensure resiliency within a rack.
 
-## Impacts to on-prem instance
+## Impacts to on-premises instance
 
 In disaster situations when the control plane loses quorum, there are impacts to the Kubernetes API across the instance. This scenario can impact a workload's ability to read and write Customer Resources (CRs) and talk across racks. 
 

articles/operator-nexus/troubleshoot-control-plane-quorum.md

@@ -1,5 +1,5 @@
 ---
-title: Troubleshoot Control Plane Quorum Loss
+title: Troubleshoot control plane quorum loss
 description: Document how to restore control plane quorum loss
 ms.topic: article
 ms.date: 01/18/2024