diff --git a/windows/application-management/manage-windows-mixed-reality.md b/windows/application-management/manage-windows-mixed-reality.md
index 6a7151bd3a..4c7ed498e8 100644
--- a/windows/application-management/manage-windows-mixed-reality.md
+++ b/windows/application-management/manage-windows-mixed-reality.md
@@ -16,12 +16,13 @@ ms.date: 10/17/2017
 
 -   Windows 10
 
-Windows 10, version 1709 (also known as the Fall Creators Update), introduces [Windows Mixed Reality](https://blogs.windows.com/windowsexperience/2017/08/28/windows-mixed-reality-holiday-update/). 
+Windows 10, version 1709 (also known as the Fall Creators Update), introduces [Windows Mixed Reality](https://blogs.windows.com/windowsexperience/2017/08/28/windows-mixed-reality-holiday-update/). Organizations that use Windows Server Update Services (WSUS) must take action to [enable Windows Mixed Reality](#enable). Any organization that wants to prohibit use of Windows Mixed Reality can [block the installation of the Mixed Reality Portal](#block).
 
-## enable
 
-Setting up Mixed Reality on Enterprise Network 
-To enable downloading Windows Mixed Reality software (feature on demand package), IT admin need to do the following. 
+<span id="enable" />
+## Enable Windows Mixed Reality in WSUS
+
+To enable users to download Windows Mixed Reality software (feature on demand package), IT admin need to do the following. 
 Enterprises that are using Creator’s Update clients + WSUS can approve Windows Mixed Reality package by unblocking the following KBs (I’m double checking with WSD to confirm the KB numbers) 
 4016509
 3180030
@@ -31,7 +32,14 @@ Enterprises that use RS3 client will not be able to install FOD directly from WS
 Have user manually install the Mixed Reality Software 
 IT admin can create Side by side feature store (shared folder) using instructions here:
 https://technet.microsoft.com/en-us/library/jj127275(v=ws.11).aspx
- 
+
+
+<span id="block" /> 
 ## block
 
 Since MRP is an app and blocking this app is sufficient for your scenario, via AppLocker should be sufficient for now. To make sure enterprise understand it, please file a doc bug to publish the instruction of leveraging AppLocker CSP to block Mixed Reality Portal and control Oasis. In the doc, AppLocker CSP doc is here: https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/applocker-csp it has a list of inbox app that could be controlled by this CSP, MRP/Oasis needs to be listed there as well. Provide the content and assign to Maricia – cpub writer for CSP. 
+
+
+## Related topics
+
+- [Mixed reality](https://developer.microsoft.com/windows/mixed-reality/mixed_reality)
\ No newline at end of file