From 2f52fff7844b4ea8643be4c5d5732c3645dd8000 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 17 Dec 2024 11:55:22 -0800
Subject: [PATCH] Update windows-autopatch-hotpatch-updates.md

Style/grammar/specificity tweak.
---
 .../manage/windows-autopatch-hotpatch-updates.md                | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 5e16a7ada2..bb9a220536 100644
--- a/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md
+++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md
@@ -47,7 +47,7 @@ Key value: `**HotPatchRestrictions=1**`
 > [!IMPORTANT:]
 > 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`) then restart the device to turn on CHPE usage.  
+If you choose to no longer use Hotpatch updates you can clear the CHPE disasble flag (`HotPatchRestrictions=0`) then restart the device to turn on CHPE usage.  
 
 ## Eligible devices