diff --git a/windows/deployment/planning/windows-11-removed-features.md b/windows/deployment/planning/windows-11-removed-features.md
index da5a28c992..447473ea86 100644
--- a/windows/deployment/planning/windows-11-removed-features.md
+++ b/windows/deployment/planning/windows-11-removed-features.md
@@ -26,5 +26,5 @@ The following features and functionalities have been removed from the installed
 
 |Feature    |  Details and mitigation  | Removed in version |
 | ----------- | --------------------- | ------ |
-| WDS image deployment | End to end WDS deployment workflows that use **boot.wim** from installation media are affected. For more information, see [Windows Deployment Services (WDS) boot.wim support](../wds-boot-support.md) | Windows 11 |
+| Windows Deployment Services (WDS) image deployment | End to end WDS deployment workflows that use **boot.wim** from installation media are affected. For more information, see [Windows Deployment Services (WDS) boot.wim support](../wds-boot-support.md) | Windows 11 |
 
diff --git a/windows/deployment/wds-boot-support.md b/windows/deployment/wds-boot-support.md
index cf45e04e2e..37ede74a28 100644
--- a/windows/deployment/wds-boot-support.md
+++ b/windows/deployment/wds-boot-support.md
@@ -25,7 +25,7 @@ When you PXE-boot from a WDS server that uses the **boot.wim** file from install
 
   ![WDS deprecation notice](images/wds-deprecation.png)
 
-## Deployment scenarios impacted
+## Deployment scenarios affected
 
 The table below provides support details for specific deployment scenarios.
 
@@ -38,7 +38,7 @@ The table below provides support details for specific deployment scenarios.
         <th>Windows Server 2016</th>
         <th>Windows Server 2019</th>
         <th>Windows Server 2022</th>
-        <th>Windows Windows 11</th>
+        <th>Windows 11</th>
     </tr>
     <tr>
         <th rowspan="6" valign="middle">Boot image version</th>
@@ -89,17 +89,17 @@ The table below provides support details for specific deployment scenarios.
 
 Alternatives to WDS, such as [Microsoft Endpoint Configuration Manager](/mem/configmgr/) and [Microsoft Deployment Toolkit](/mem/configmgr/mdt/) (MDT) provide a better, more flexible, and feature-rich experience for deploying Windows images. 
 
-## Not impacted
+## Not affected
 
-WDS PXE boot is not affected by this change. You can still use WDS to PXE boot devices with a custom boot images, but you will no longer be able to use **boot.wim** as the boot image, and run Windows Setup in WDS mode.
+WDS PXE boot is not affected by this change. You can still use WDS to PXE boot devices with custom boot images, but you cannot use **boot.wim** as the boot image and run Windows Setup in WDS mode.
 
-You can still run Windows Setup from a network share. Workflows that leverage a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
+You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this change.
 
 ## Summary
 
 - Windows 11 workflows that rely on **boot.wim** from installation media will be blocked. You cannot perform an end to end deployment of Windows 11 using only WDS.
 - Windows 10, Windows Server 2019, and previous operating system versions are not affected by this change.
-- Windows Server 2022 workflows that rely on **boot.wim** from installation media will show a non-blocking deprecation notice that can be dismissed, but the workflow is not blocked.
+- Windows Server 2022 workflows that rely on **boot.wim** from installation media will show a non-blocking deprecation notice. The notice can be dismissed, and currently the workflow is not blocked.
 - Windows Server workflows after Windows Server 2022 that rely on **boot.wim** from installation media are blocked.
 
 If you currently use WDS with **boot.wim** from installation media for end-to-end operating system deployment, and your OS version is not supported, deprecated, or blocked, it is recommended that you use deployment tools such as MDT, Configuration Manager, or a non-Microsoft solution with a custom boot.wim image.