diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md
index 76c71d2c577..5e16a7ada26 100644
--- a/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md
+++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md
@@ -31,20 +31,23 @@ Hotpatch updates are [Monthly B release security updates](/windows/deployment/up
 - The [Hotpatch quality update report](../monitor/windows-autopatch-hotpatch-quality-update-report.md) provides a per policy level view of the current update statuses for all devices that receive Hotpatch updates.
 
 ## Operating system configuration prerequisites 
-To prepare a device to receive hotpatch updates, configure the following device-side operating system settings. Failure to configure these settings will result in the device not being offered the hotpatch update or being unable to apply all the hotpatch updates, leaving some vulnerabilities unmitigated.
+
+To prepare a device to receive Hotpatch updates, configure the following operating system settings on the device. You must configure these settings for the device to be offered the Hotpatch update and to apply all Hotpatch updates.
 
 ### Virtualization based security (VBS)
-VBS must be enabled for a device to be offered hotpatch updates. For information on how to set and detect VBS enabled, see [Virtualization-based Security (VBS)](https://learn.microsoft.com/en-us/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity?tabs=security).
+
+VBS must be turned on for a device to be offered Hotpatch updates. For information on how to set and detect VBS enabled, see [Virtualization-based Security (VBS)](/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity?tabs=security).
 
 ### Arm 64 devices must disable compiled hybrid PE usage (CHPE) (Arm 64 CPU Only)
-The following requirement only appies to Arm 64 CPU devices when using hotpatch updates. Hotpatch updates are not compatible with servicing CHPE OS binaries located in the %SystemRoot%\SyChpe32 folder. In order to ensure all the hotpatch updates take effect, you must set the CHPE disable flag and restart the device to disable CHPE usage. You only need to set this flag one time. The registry setting will persist through updates. To disable CHPE, set the following registry key:
-Path: **HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management**
-Key value: **HotPatchRestrictions=1**
+
+This requirement only applies to Arm 64 CPU devices when using Hotpatch updates. Hotpatch updates aren't compatible with servicing CHPE OS binaries located in the `%SystemRoot%\SyChpe32` folder. To ensure all the Hotpatch updates are applied, you must set the CHPE disable flag and restart the device to disable CHPE usage. You only need to set this flag one time. The registry setting remains applied through updates. To disable CHPE, set the following registry key:
+Path: `**HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management**`
+Key value: `**HotPatchRestrictions=1**`
 
 > [!IMPORTANT:]
-> This setting is required becuase it forces the operating system to use the emulation x86-only binaries insetad of CHPE binaries on Arm 64 devices. CHPE binaries include native Arm 64 code to improve performance so you excluding them may impact performance or compatibility. Be sure to > test application compatibility or performance impacts before rolling out hotpatch updates widely on Arm 64 CPU based devices.
+> This setting is required because it forces the operating system to use the emulation x86-only binaries insetad of CHPE binaries on Arm 64 devices. CHPE binaries include native Arm 64 code to improve performance, excluding the CHPE binaries might affect performance or compatibility. Be sure to test application compatibility and performance before rolling out hotpatch updates widely on Arm 64 CPU based devices.
 
-If you choose to no longer use Hotpatch updates you can clear the flag (HotPatchRestrictions=0) and restart the computer which will reenable CHPE usage.  
+If you choose to no longer use hotpatch updates you can clear the flag (`HotPatchRestrictions=0`) then restart the device to turn on CHPE usage.  
 
 ## Eligible devices
 
@@ -83,7 +86,7 @@ For more information about the release calendar for Hotpatch updates, see [Relea
 1. Go to the **Quality updates** tab.
 1. Select **Create**, and select **Windows quality update policy (preview)**.
 1. Under the **Basics** section, enter a name for your new policy and select Next.
-1. Under the **Settings** section, set **"When available, apply without restarting the device ("hotpatch")** to **Allow**. Then, select **Next**.
+1. Under the **Settings** section, set **"When available, apply without restarting the device ("Hotpatch")** to **Allow**. Then, select **Next**.
 1. Select the appropriate Scope tags or leave as Default and select **Next**.
 1. Assign the devices to the policy and select **Next**.
 1. Review the policy and select **Create**.