Linting

Author: jenSheasby

articles/operator-nexus/media/interface-out-pkts.png renamed to articles/operator-nexus/media/interface-out-packets.png

@@ -10,17 +10,16 @@ ms.service: azure-operator-nexus
 
 # Troubleshooting failed volume attachments - Azure Resource Health
 
-This article provides troubleshooting advice and escalation methods for Operator Nexus clusters which are
+This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
 reporting failed volume attachments in Azure Resource Health.
 
 ## Symptoms
 
-This alert indicates that volumes are failing to attach in the undercloud. This can lead to delays in
-bringing up workloads in the tenant layer, or migrating existing workloads to a new node. If the cluster
-has been marked as degraded, this implies at least 1 volume is failing to attach - in this case the problem
-may be limited to this specific volume, and the impact radius is small. If the cluster has been marked as
-unhealthy, a high percentage of volumes on at least 1 node are failing to attach, indicating a more serious
-incident.
+This alert indicates that volumes are failing to attach in the undercloud. Failed volume attachments can lead
+to delays in bringing up workloads in the tenant layer, or migrating existing workloads to a new node. A
+cluster in degraded state has at least one failed volume attachment - in this case the problem may be limited
+to this specific volume, and the impact radius is small. A cluster in unhealthy state has at least one node
+where a high percentage of volume attachments are failed, indicating a more serious incident.
 
 ## Troubleshooting
 

articles/operator-nexus/troubleshoot-failed-volume-attachments.md

@@ -10,8 +10,8 @@ ms.service: azure-operator-nexus
 
 # Troubleshooting unhealthy NFS pods - Azure Resource Health
 
-This article provides troubleshooting advice and escalation methods for Operator Nexus clusters which are
-reporting unhealthy NFS pods in Azure Resource Health.
+This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
+reporting unhealthy Network File System (NFS) pods in Azure Resource Health.
 
 ## Symptoms
 

articles/operator-nexus/troubleshoot-nfs-unhealthy.md renamed to articles/operator-nexus/troubleshoot-network-file-system-unhealthy.md

@@ -25,15 +25,15 @@ These alerts are generated based on the status of the resource and its dependenc
 | `1PExtensionsFailedInstall`                                                                            | [Requires to contact support](#please-contact-support)                |
 | `ClusterHeartbeatConnectionStatusDisconnectedClusterManagerOperationsAreAffectedPossibleNetworkIssues` | [Troubleshoot Cluster heartbeat connection status shows disconnected] |
 | `ClusterHeartbeatConnectionStatusTimedoutPossiblePerformanceIssues`                                    | [Troubleshoot Cluster heartbeat connection status shows disconnected] |
-| `AttachmentFailuresDegraded` and `AttachmentFailuresUnhealthy`                                         | [Troubleshoot failed volume attachments]                              |
-| `NFSPodDegraded` and `NFSPodUnhealthy`                                                                 | [Troubleshoot NFS unhealthy]                                          |
-| `CSIControllerUnhealthy`, `CSINodeDegraded` and `CSINodeUnhealthy`                                     | [Troubleshoot unhealthy CSI (storage)]                                |
-| `ControlPlaneStorageConnectivityDegraded` and `ControlPlaneStorageConnectivityUnhealthyVIP`            | [Troubleshoot storage control plane disconnected]                     |
+| `AttachmentFailuresDegraded`, and `AttachmentFailuresUnhealthy`                                        | [Troubleshoot failed volume attachments]                              |
+| `NFSPodDegraded`, and `NFSPodUnhealthy`                                                                | [Troubleshoot NFS unhealthy]                                          |
+| `CSIControllerUnhealthy`, `CSINodeDegraded`, and `CSINodeUnhealthy`                                    | [Troubleshoot unhealthy CSI (storage)]                                |
+| `ControlPlaneStorageConnectivityDegraded`, and `ControlPlaneStorageConnectivityUnhealthyVIP`           | [Troubleshoot storage control plane disconnected]                     |
 
 [Troubleshoot Cluster heartbeat connection status shows disconnected]: ./troubleshoot-cluster-heartbeat-connection-status-disconnected.md
 [Troubleshoot failed volume attachments]: ./troubleshoot-failed-volume-attachments.md
-[Troubleshoot NFS unhealthy]: ./troubleshoot-nfs-unhealthy.md
-[Troubleshoot unhealthy CSI (storage)]: ./troubleshoot-unhealthy-csi.md
+[Troubleshoot NFS unhealthy]: ./troubleshoot-network-file-system-unhealthy.md
+[Troubleshoot unhealthy CSI (storage)]: ./troubleshoot-unhealthy-container-storage-interface.md
 [Troubleshoot storage control plane disconnected]: ./troubleshoot-storage-control-plane-disconnected.md
 
 ## Please contact support

articles/operator-nexus/troubleshoot-resource-health-alerts.md

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting storage control plane connectitivy issues.
+title: Troubleshooting storage control plane connectivity issues.
 description: Troubleshooting Azure Resource Health alerts about control plane connectivity issues.
 author: jensheasby
 ms.author: jensheasby
@@ -10,40 +10,39 @@ ms.service: azure-operator-nexus
 
 # Troubleshooting control plane connectivity issues - Azure Resource Health
 
-This article provides troubleshooting advice and escalation methods for Operator Nexus clusters which are
+This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
 reporting issues with control plane connectivity in Azure Resource Health.
 
 ## Symptoms
 
 This alert indicates that there are issues connecting to the storage control plane from the cluster. The two
 categories of alert have different symptoms:
 
-- If the cluster is marked as degraded, this means there has been a loss of redundancy to the storage control
-  plane. This means that one of the controllers is experiencing connectivity issues. The cluster will continue
-  to function, but this issue should be quickly fixed to restore redundancy to the system.
-- If the cluster is marked as unhealthy, this means the storage control plane is completely unreachable from
-  the cluster. New workloads which depend on `nexus-volume` volumes will not come up, and existing workloads
-  which rely on `nexus-volume` volumes will not be able to be migrated to a new node. Additonally, new cloud
-  services networks cannot be created.
+- A degraded cluster has lost redundancy to the storage control plane. This means that one of the controllers
+  is experiencing connectivity issues. The cluster continues to function, but this issue should be quickly
+  fixed to restore redundancy to the system.
+- An unhealthy cluster is unable to reach the storage control plane. New workloads that depend on `nexus-volume`
+  volumes cannot come up, and existing workloads that rely on `nexus-volume` volumes cannot be migrated to a
+  new node. Additionally, new cloud services networks cannot be created.
 
 ## Troubleshooting
 
 The cluster may be marked as degraded during a storage appliance upgrade, since these upgrades take controllers
 offline one by one. The cluster should return to healthy status after the upgrade is complete.
 
 If an upgrade is not the root cause, you should check if there are any issues with the management switches in
-the aggregator rack. Follow these steps to check for issues:
+the aggregator rack, by following these steps:
 
 1. Start on the cluster (Operator Nexus) resource overview page. Click the link to the network fabric resource.
    :::image type="content" source="media/navigate-network-fabric-portal.png" alt-text="Screenshot of a cluster resource, with the network fabric link highlighted." lightbox="media/navigate-network-fabric-portal.png":::
-2. Go to `Infrastructue->Devices`, and search for the aggregator rack management switches. Ensure they are succesfully
+2. Go to `Infrastructue->Devices`, and search for the aggregator rack management switches. Ensure they are successfully
    provisioned and enabled.
-   :::image type="content" source="media/navigate-mgmt-switch-portal.png" alt-text="Screenshot of the Infrastructure tab of a network fabric resource." lightbox="media/snavigate-mgmt-switch-portal.png":::
+   :::image type="content" source="media/navigate-mgmt-switch-portal.png" alt-text="Screenshot of the Infrastructure tab of a network fabric resource." lightbox="media/navigate-mgmt-switch-portal.png":::
 3. Click on a management switch, and go to the `Monitoring->Metrics` tab. Select `Interface Out Pkts`, then apply splitting
    on the `Interface Name` dimension.
-   :::image type="content" source="media/interface-out-pkts.png" alt-text="Screenshot of a metric showing the outward packets of a management switch." lightbox="media/interface-out-pkts.png":::
-4. Check for any interfaces where the packets has suddenly dropped to zero. If you find any, you should reseat any affected
-   cables.
+   :::image type="content" source="media/interface-out-packets.png" alt-text="Screenshot of a metric showing the outward packets of a management switch." lightbox="media/interface-out-packets.png":::
+4. Check for any interfaces where the number of packets suddenly dropped to zero. If you find any, you should reseat
+   any affected cables.
 5. Repeat the check for the second management switch.
 
 If upgrade or management switch problems are not the root cause, you should raise a ticket with Microsoft, quoting

articles/operator-nexus/troubleshoot-storage-control-plane-disconnected.md

@@ -10,7 +10,7 @@ ms.service: azure-operator-nexus
 
 # Troubleshooting unhealthy CSI pods (storage) - Azure Resource Health
 
-This article provides troubleshooting advice and escalation methods for Operator Nexus clusters which are
+This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
 reporting unhealthy Container Storage Interface (CSI) pods in Azure Resource Health.
 
 ## Symptoms