Mark ups

Author: jenSheasby

articles/operator-nexus/TOC.yml

@@ -406,6 +406,14 @@
       items:
         - name: Troubleshoot Resource Health alerts
           href: troubleshoot-resource-health-alerts.md
+        - name: Troubleshoot failed volume attachments
+          href: troubleshoot-failed-volume-attachments.md
+        - name: Troubleshoot storage control plane connectivity issues.
+          href: troubleshoot-storage-control-plane-disconnected.md
+        - name: Troubleshoot unhealthy Container Storage Interface (CSI) pods
+          href: troubleshoot-unhealthy-container-storage-interface.md
+        - name: Troubleshoot Unhealthy Network File System pods
+          href: troubleshoot-network-file-system-unhealthy.md
         - name: Troubleshoot Unhealthy or Degraded Storage Appliance
           href: troubleshoot-unhealthy-degraded-storage-appliance.md
     - name: Storage Appliance

articles/operator-nexus/media/navigate-network-fabric-portal.png

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting failed volume attachments
+title: Troubleshoot failed volume attachments
 description: Troubleshooting Azure Resource Health alerts about failed volume attachments
 author: jensheasby
 ms.author: jensheasby
@@ -8,7 +8,7 @@ ms.topic: troubleshooting
 ms.service: azure-operator-nexus
 ---
 
-# Troubleshooting failed volume attachments - Azure Resource Health
+# Troubleshoot failed volume attachments - Azure Resource Health
 
 This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
 reporting failed volume attachments in Azure Resource Health.
@@ -25,10 +25,10 @@ where a high percentage of volume attachments are failed, indicating a more seri
 
 This alert may be seen at the same time as the `ControlPlaneStorageConnectivityUnhealthyVIP` alert. In this
 case, the lost connectivity on the storage control plane is likely the cause of the failed attachments. You
-should follow the [troubleshooting guide for that issue]. If after resolving that incident, this alert persists,
+should follow the [Troubleshooting guide for that issue]. If after resolving that incident, this alert persists,
 return to this guide.
 
 If control plane connectivity issues are not the root cause, you should raise a ticket with Microsoft, quoting the
 text of this troubleshooting guide, and the Azure resource ID of the affected cluster.
 
-[troubleshooting guide for that issue]: ./troubleshoot-storage-control-plane-disconnected.md
+[Troubleshooting guide for that issue]: ./troubleshoot-storage-control-plane-disconnected.md

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

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting unhealthy NFS pods
+title: Troubleshoot unhealthy NFS pods
 description: Troubleshooting Azure Resource Health alerts about NFS
 author: jensheasby
 ms.author: jensheasby
@@ -8,7 +8,7 @@ ms.topic: troubleshooting
 ms.service: azure-operator-nexus
 ---
 
-# Troubleshooting unhealthy NFS pods - Azure Resource Health
+# Troubleshoot unhealthy NFS pods - 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.
@@ -20,7 +20,7 @@ operations for `nexus-shared` volumes in the tenant layer. Therefore, if a clust
 existing `nexus-shared` volumes may experience data plane disruption, and new `nexus-shared` volumes may
 fail to be created.
 
-## Troubleshooting
+## Troubleshoot
 
 You should raise a ticket with Microsoft, quoting the text of this troubleshooting guide, and the Azure
 resource ID of the affected cluster.

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

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting storage control plane connectivity issues.
+title: Troubleshoot storage control plane connectivity issues.
 description: Troubleshooting Azure Resource Health alerts about control plane connectivity issues.
 author: jensheasby
 ms.author: jensheasby
@@ -8,7 +8,7 @@ ms.topic: troubleshooting
 ms.service: azure-operator-nexus
 ---
 
-# Troubleshooting control plane connectivity issues - Azure Resource Health
+# Troubleshoot control plane connectivity issues - Azure Resource Health
 
 This article provides troubleshooting advice and escalation methods for Operator Nexus clusters that are
 reporting issues with control plane connectivity in Azure Resource Health.
@@ -25,7 +25,7 @@ categories of alert have different symptoms:
   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
+## Troubleshoot
 
 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.

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

@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting unhealthy CSI (storage)
+title: Troubleshoot unhealthy CSI (storage)
 description: Troubleshooting Azure Resource Health alerts about unhealthy CSI pods (storage)
 author: jensheasby
 ms.author: jensheasby
@@ -8,7 +8,7 @@ ms.topic: troubleshooting
 ms.service: azure-operator-nexus
 ---
 
-# Troubleshooting unhealthy CSI pods (storage) - Azure Resource Health
+# Troubleshoot unhealthy CSI pods (storage) - Azure Resource Health
 
 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.
@@ -20,7 +20,7 @@ responsible for control plane operations for volumes in the undercloud. If these
 relying on `nexus-volume` storage may fail to come up, or existing workloads may not be able to be migrated.
 You may also experience issues provisioning new cloud services networks.
 
-## Troubleshooting
+## Troubleshoot
 
 You should raise a support ticket with Microsoft, quoting the text of this troubleshooting guide, and the Azure
 resource ID of the affected cluster.