Update windows-updates-dont-install-on-vm-cluster-hosts.md

Edit review per CI 7765

Author: przlplx

support/windows-server/virtualization/windows-updates-dont-install-on-vm-cluster-hosts.md

@@ -27,17 +27,17 @@ You experience one or more of these symptoms:
 
 ## Cause
 
-These issues occur when checkpoints (sometimes known as snapshots) for the VMs in the cluster grow too large. Checkpoints generate large VMRS files, which consume disk space and can disrupt the migration process. Disruptions and insufficient disk space can further cause operations to time out and updates to fail to install.
+These issues occur if checkpoints (sometimes known as snapshots) for the VMs in the cluster grow too large. Checkpoints generate large VMRS files. Such files which consume disk space and can disrupt the migration process. Disruptions and insufficient disk space can further cause operations to time out and updates to fail to install.
 
 For more information about checkpoints, see [Using checkpoints to revert virtual machines to a previous state](/windows-server/virtualization/hyper-v/checkpoints).
 
 ## Resolution
 
-Before you start, verify that you have admin access to the cluster hosts. Make sure you've backed up all critical data and configuration information.
+Before you start, verify that you have admin access to the cluster hosts. Make sure you back up all critical data and configuration information.
 
 The following procedures assume that you're familiar with the Windows Update service and [Cluster-Aware Updating overview](/windows-server/failover-clustering/cluster-aware-updating).
 
-To resolve this issue, select one of the following solutions.
+To resolve this issue, use one of the following solutions.
 
 ### Solution 1: Manually update all hosts to the latest version
 
@@ -46,15 +46,15 @@ To resolve this issue, select one of the following solutions.
 
 Follow these steps on each cluster host:
 
-1. To identify the most recently installed update, on the host computer, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
+1. To identify the most recently installed update on the host computer, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
 1. Download and install the most recent compatible update for the host. You can use any of the following tools to access updates:
 
    - Windows Update
    - Windows Server Update Services (WSUS)
    - The [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/)
 
-1. If needed, restart the host.
-1. After the update process finishes, review the host's update history. Make sure the update installed.
+1. If it's necessary, restart the host.
+1. After the update process finishes, review the host's update history. Make sure that the update installed successfully.
 
 ### Solution 2: Schedule CAU to occur during a maintenance window, and temporarily disable Windows Update services
 
@@ -75,11 +75,11 @@ Use this solution to prevent conflicts between CAU and the Windows Update servic
    1. Right-click the service, select **Properties**, and then set **Startup type** to **Disabled**.
    1. To stop the service, select **Stop**.
 
-1. After the subsequent maintenance window ends, check each host's update history to make sure that the updates installed. To check a host's update history, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
-1. Use the Services console to re-enable the Windows Update service (in the service properties, set **Startup type** to **Automatic**, and then select **Start**).
+1. After the subsequent maintenance window ends, check each host's update history to make sure that the updates installed successfully. To check a host's update history, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
+1. Use the Services console to re-enable the Windows Update service. In the service properties, set **Startup type** to **Automatic**, and then select **Start**.
 
    > [!IMPORTANT]
-   > This final step ensures that your hosts continue to receive security updates.
+   > This final step make sure that your hosts continue to receive security updates.
 
 ### Solution 3: Remove checkpoints that you don't need
 
@@ -88,11 +88,11 @@ Don't try to use VM checkpoints for long-term backup storage. Typically, checkpo
 > [!NOTE]
 > Use this procedure during a maintenance window. When you delete a checkpoint, Windows merges the related differencing disk into the parent VHDX of the VM. For large VMs, this operation can be time-consuming and resource-intensive.
 
-When you don't need the checkpoints anymore, follow these steps to remove the checkpoints:
+When you no longer need the checkpoints, follow these steps to remove the checkpoints:
 
 1. Open the Hyper-V Manager or your preferred virtualization management tool.
 1. Go to the VM that has checkpoints.
-1. Review the checkpoints and confirm that you don't need them.
-1. Delete each checkpoint. If necessary, confirm that you want to delete the checkpoint.
-1. Check the VM to make sure that the checkpoints gone, and the disk space is reclaimed.
+1. Review the checkpoints, and confirm that you don't need them.
+1. Delete each checkpoint. If it's necessary, confirm that you want to delete the checkpoint.
+1. Check the VM to make sure that the checkpoint is removed and the disk space is reclaimed.
 1. Try again to install the updates on the cluster hosts.