Acrolint troubleshooting doc

Author: pjw711

articles/operator-nexus/troubleshoot-multiple-storage-appliances.md

@@ -24,32 +24,36 @@ If you see these issues, perform these checks:
 
 - Confirm that you correctly configured the prerequisites for both storage appliances. The initial IP address configuration is different for each storage appliance. See [the platform prerequisites](./howto-platform-prerequisites.md) for the correct configuration.
 - Confirm that Network Fabric Controller and Network Fabric are successfully provisioned.
-- Confirm that you have opened a support ticket for Network Fabric second storage appliance port enablement and that the ticket has been closed.
+- Confirm that you have opened a support ticket to enable Network Fabric support for the second storage appliance. Confirm the ticket has been closed.
 - Check that the Azure CLI command you ran included the configuration for the second storage appliance and specified an aggregator rack SKU that supports a second storage appliance. See [cluster creation with multiple storage appliances](/howto-configure-cluster.md#create-the-cluster-using-azure-cli---multiple-storage-appliances) for details.
 
-If any of the configuration was incorrect, delete the Nexus cluster, apply the correct initial storage appliance configuration and/or open a support ticket for Network Fabric enablement, and then recreate the cluster with the correct configuration.
+If any of the configurations was incorrect:
+
+- Delete the Nexus cluster
+- Apply the correct initial storage appliance configuration and/or open a support ticket for Network Fabric enablement
+- Recreate the cluster with the correct configuration.
 
 ## Nexus-volume Persistent Volume Claim (PVC) on the wrong storage appliance
 
-PVCs using the nexus-volume storage class can select the storage appliance to use for backing storage using the `storageApplianceName` annotation. If this annotation is not present the PVC will use the first storage appliance. You can check this by using `kubectl get pvc <pvcName>` and checking the `storageApplianceName` annotation. The value tells you which storage appliance the PVC is using.
+PVCs using the nexus-volume storage class can select the storage appliance to use for backing storage using the `storageApplianceName` annotation. If this annotation isn't present, the PVC uses the first storage appliance. You can check this by using `kubectl get pvc <pvcName>` and checking the `storageApplianceName` annotation. The value tells you which storage appliance the PVC is using.
 
-If you wanted to create the PVC on the other storage appliance then you must delete and recreate the PVC, and then provide the correct annotation. There is no support for moving the volumes consumed by a PVC between storage appliances.
+If you wanted to create the PVC on the other storage appliance then you must delete and recreate the PVC, and then provide the correct annotation. There's no support for moving the volumes consumed by a PVC between storage appliances.
 
 ## Failure to create nexus-volume PVC
 
-A PVC will fail to create if the `storageApplianceName` annotation is present but does not match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` annotation is correct by:
+A PVC fails to create if the `storageApplianceName` annotation is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` annotation is correct by:
 
-1. Opening the Cluster (Operator Nexus) resource in the Azure Portal
+1. Opening the Cluster (Operator Nexus) resource in the Azure portal
 1. Clicking on Rack definitions in the resource menu.
 1. Navigating to the aggregator rack and selecting Storage Appliance definitions.
 
 The `storageApplianceName` annotation must match one of the storage appliances in the Storage Appliance definitions list. You must delete the PVC and recreate it with the correct annotation to resolve this issue.
 
-## CSN fails to create
+## Cloud Service Network (CSN) fails to create
 
-A CSN will fail to create if the `storageApplianceName` Azure resource tag is present but does not match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` Azure resource tag is correct by:
+A CSN fails to create if the `storageApplianceName` Azure resource tag is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` Azure resource tag is correct by:
 
-1. Opening the Cluster (Operator Nexus) resource in the Azure Portal
+1. Opening the Cluster (Operator Nexus) resource in the Azure portal
 1. Clicking on Rack definitions in the resource menu.
 1. Navigating to the aggregator rack and selecting Storage Appliance definitions.