diff --git a/WindowsServerDocs/get-started/removed-deprecated-features-windows-server.md b/WindowsServerDocs/get-started/removed-deprecated-features-windows-server.md
index 81827ca4ab..6706407083 100644
--- a/WindowsServerDocs/get-started/removed-deprecated-features-windows-server.md
+++ b/WindowsServerDocs/get-started/removed-deprecated-features-windows-server.md
@@ -51,7 +51,7 @@ We're no longer actively developing these features and might remove them from a
 | Hyper-V Virtual Switch on LBFO | The Hyper-V Virtual Switch no longer has the capability to be bound to an LBFO team. Instead, it must be bound via [Switch Embedded Teaming (SET)](/azure/azure-local/concepts/host-network-requirements#switch-embedded-teaming-set). This change only applies to Hyper-V. LBFO is still fully supported for other non-Hyper-V scenarios. |
 | Launching SConfig from a command prompt | Starting with Windows Server 2022, `SConfig` is launched by default when you sign into a server running the Server Core installation option. Moreover, PowerShell is now the default shell on Server Core. If you exit `SConfig`, you get to a regular interactive PowerShell window. Similarly, you can opt out from SConfig autolaunch. In this case, a PowerShell window pops up at sign-in. In either scenario, you can launch SConfig from PowerShell by running `SConfig`. |
 | New EKUs for VBS enclaves | VBS enclaves are supported on Windows Server 2025 and later. *Existing* enclaves with the EKU 1.3.6.1.4.1.311.76.57.1.15 signature are still supported on Windows Server 2022 as long as they remain unchanged and don't require re-signing. |
-| Windows Deployment Services (WDS) boot.wim image deployment | The operating system deployment functionality of WDS is being partially deprecated. Workflows that rely on `boot.wim` from Windows Server 2022 installation media show a nonblocking deprecation notice, but the workflows aren't impacted.<br><br>Windows 11 workflows and workflows for future versions of Windows Server that rely on `boot.wim` from installation media are blocked.<br><br>Alternatives to WDS, such as [Microsoft Configuration Manager](/mem/configmgr/) or the [Microsoft Deployment Toolkit](/windows/deployment/deploy-windows-mdt/get-started-with-the-microsoft-deployment-toolkit) (MDT), provide a better, more flexible, and feature-rich experience for deploying Windows images. We recommend that you use one of these solutions instead.<br><br>WDS PXE boot isn't affected. You can still use WDS to PXE-boot devices to custom boot images. You can also still [run setup from a network share](/windows-hardware/manufacture/desktop/deploy-a-custom-image). Workflows that use custom `boot.wim` images, such as with Configuration Manager or MDT, aren't impacted. |
+| Windows Deployment Services (WDS) boot.wim image deployment | The operating system deployment functionality of WDS is being partially deprecated. Workflows that rely on `boot.wim` from Windows Server 2022 installation media show a nonblocking deprecation notice, but the workflows aren't impacted.<br><br>Windows 11 workflows and workflows for future versions of Windows Server that rely on `boot.wim` from installation media are blocked.<br><br>Alternatives to WDS, such as [Microsoft Configuration Manager](/mem/configmgr/), provide a better, more flexible, and feature-rich experience for deploying Windows images.<br><br>WDS PXE boot isn't affected. You can still use WDS to PXE-boot devices to custom boot images. You can also still [run setup from a network share](/windows-hardware/manufacture/desktop/deploy-a-custom-image). Workflows that use custom `boot.wim` images, such as with Configuration Manager or MDT, aren't impacted. |
 | Windows Internet Name Service (WINS) | WINS is a legacy computer name registration and resolution service. You should replace WINS with Domain Name System (DNS). For more information, see [Windows Internet Name Service (WINS)](../networking/technologies/wins/wins-top.md). |
 | XDDM-based remote display driver | Starting with this release, Remote Desktop Services uses a Windows Display Driver Model (WDDM) based indirect display driver (IDD) for a single-session remote desktop. Support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent software vendors that use XDDM-based remote display drivers should plan a migration to the WDDM driver model. For more information on implementing remote indirect display drivers, see [Updates for IddCx versions 1.4 and later](/windows-hardware/drivers/display/iddcx1.4-updates). |