diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml
index 560f759c03..0f9b776ed3 100644
--- a/windows/deployment/do/TOC.yml
+++ b/windows/deployment/do/TOC.yml
@@ -46,19 +46,19 @@
         - name: Configure, provision and deploy cache node
           items:
           - name: Deploy MCC to Linux
-            href: mcc-ent-deploy-linux.md
+            href: mcc-ent-deploy-to-linux.md
           - name: Deploy MCC to Windows
-            href: mcc-ent-deploy-windows.md
+            href: mcc-ent-deploy-to-windows.md
         - name: Using CLI to create and manage cache nodes
           href: mcc-ent-manage-cache-using-CLI.md 
         - name: Verify cache node functionality
           href: mcc-ent-verify-cache-node.md
         - name: Monitor cache node
-          href: mcc-ent-monitor-cache.md
+          href: mcc-ent-monitoring.md
         - name: Update MCC
-          href: mcc-ent-update-cache.md 
+          href: mcc-ent-update-cache-node.md 
         - name: Uninstall cache node
-          href: mcc-ent-uninstall.md     
+          href: mcc-ent-uninstall-cache-node.md     
       - name: Resources
         items:
         - name: Frequent Asked Questions
diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md
index 2169c9bb24..9cfe7c3246 100644
--- a/windows/deployment/do/mcc-ent-prerequisites.md
+++ b/windows/deployment/do/mcc-ent-prerequisites.md
@@ -32,9 +32,6 @@ This article details the requirements and recommendations for using Microsoft Co
 
 ## Cache node host machine requirements
 
-   > [!NOTE]
-   > If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations.
-
 ### General requirements
 
 - Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC.
diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md
index 7ef5d63115..32cd0edc45 100644
--- a/windows/deployment/do/mcc-ent-verify-cache-node.md
+++ b/windows/deployment/do/mcc-ent-verify-cache-node.md
@@ -18,7 +18,7 @@ appliesto:
 
 This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly.
 
-These steps should be taken after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine.
+These steps should be taken after deploying MCCE caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
 
 ## Steps to verify functionality of MCCE cache node
 
@@ -36,7 +36,7 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
 
     If successful, the Windows client device should begin to download a small image file from the MCCE cache node.
 
-1. To check how much content an individual Windows client has pulled from an MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/en-us/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
+1. To check how much content an individual Windows client has pulled from an MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
 
     You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".