Updated text

Author: ronmiab

azure-stack/hci/manage/suspend-resume-cluster-maintenance.md

@@ -20,11 +20,11 @@ This article describes how to suspend a cluster node for planned maintenance, su
 
 ## Suspend a cluster node
 
-To suspsend a cluster node we first suspend the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool.
+To suspend a cluster node, first suspend the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool.
 
-To suspend a cluster node follow these steps:
+To suspend a cluster node, follow these steps:
 
-1. Logon to one of the cluster nodes with a user that has local administrator permissions.
+1. Log on to one of the cluster nodes with a user that has local administrator permissions.
 1. To suspend the cluster node, run this command:
 
     ```powershell
@@ -44,7 +44,7 @@ To suspend a cluster node follow these steps:
     > [!NOTE]
     > Running this command may take some time, depending on the number of VMs that need to be migrated.
 
-1. Then, to confirm that the node is successfully suspended, run this command.
+1. Confirm that the node is successfully suspended.
 
     ```powershell
     Get-clusternode
@@ -61,19 +61,19 @@ To suspend a cluster node follow these steps:
     ASRRlS3lRl5Ull      Paused       Node
     ```
 
-1. Next, remove the node from the active Arc VM Configuration to ensure that no new VMs are placed on the node. **This step can only be done using PowerShell**.
+1. To ensure that no new VMs are placed on the node, remove the node from the active Arc VM Configuration. **This step can only be done using PowerShell**.
 
     ```powershell
     Remove-MocPhysicalNode -nodeName “MachineName”
     ```
 
 ## Resume a cluster node
 
-To resume a cluster node we first resume the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool.
+To resume a cluster node, first resume the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool.
 
-To resume a cluster node follow these steps:
+To resume a cluster node, follow these steps:
 
-1. Logon to one of the cluster nodes with a user that has local administrator permissions.
+1. Log on to one of the cluster nodes with a user that has local administrator permissions.
 1. To resume the cluster node, run this command:
 
     ```powershell
@@ -93,7 +93,7 @@ To resume a cluster node follow these steps:
     > [!NOTE]
     > Running this command may take some time, depending on the number of VMs that need to be migrated.
 
-1. Then, to confirm that the node is successfully resumed, run this command:
+1. Confirm that the node is successfully resumed.
 
     ```powershell
     Get-clusternode
@@ -110,13 +110,13 @@ To resume a cluster node follow these steps:
     ASRRlS3lRl5Ull      Paused       Node
     ```
 
-1. Next, add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**.
+1. Add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**.
 
     ```powershell
     Remove-MocPhysicalNode -nodeName “MachineName”
     ```
 
-1. Verify that your storage pool is healthy. Run this command:
+1. Verify that your storage pool is healthy.
 
     ```powershell
     Get-Storagepool -friendlyname “SU_Pool1”
@@ -133,4 +133,4 @@ To resume a cluster node follow these steps:
     ```
 
     > [!NOTE]
-    > If the pool is not reported as healthy, check the status of the storage repair jobs using the `get-storagejob command`.
+    > If the pool is not reported as healthy, check the status of the storage repair jobs using the `get-storagejob` command.