edits

windows/deployment/do/TOC.yml

@@ -27,7 +27,7 @@
       href: delivery-optimization-test.md
 - name: Microsoft Connected Cache
   items:
-    - name: What is Microsoft Connected Cache
+    - name: What is Microsoft Connected Cache?
       href: waas-microsoft-connected-cache.md
     - name: MCC for Enterprise and Education
       items:

windows/deployment/do/mcc-ent-edu-overview.md

@@ -6,7 +6,7 @@ ms.prod: windows-client
 author: amymzhou
 ms.author: amyzhou
 ms.topic: article
-ms.date: 12/31/2017
+ms.date: 05/09/2023
 ms.technology: itpro-updates
 ms.collection: tier3
 ---
@@ -19,14 +19,12 @@ ms.collection: tier3
 - Windows 11
 
 > [!IMPORTANT]
-> Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+> - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-
+> - We're still accepting Enterprise and Education customers to join the early preview. To register your interest, fill out the survey located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup).
-> [!NOTE]
-> We're still accepting Enterprise and Education customers to join the early preview. To register your interest, fill out the survey located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup).
 
 Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be deployed to as many Windows servers, bare-metal servers, or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune.
 
-Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For Microsoft Connected Cache in Configuration Manager (generally available starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
+Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
 
 ## Supported scenarios
 
@@ -48,7 +46,7 @@ For the full list of content endpoints that Microsoft Connected Cache for Enterp
 
 ## How it works
 
-MCC is a hybrid (mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.  
+MCC is a hybrid (mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It's built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC is a Linux IoT Edge module running on the Windows Host OS.  
 
 1. The Azure Management Portal is used to create MCC nodes.
 1. The MCC container is deployed and provisioned to the server using the installer provided in the portal.
@@ -56,7 +54,7 @@ MCC is a hybrid (mix of on-premises and cloud resources) SaaS solution built as
 1. Microsoft end-user devices make range requests for content from the MCC node.
 1. The MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
 1. Subsequent requests from end-user devices for content will now come from cache.
-1. If the MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
+1. If the MCC node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers.
 
 The following diagram displays an overview of how MCC functions:
 

windows/deployment/do/mcc-isp-create-provision-deploy.md

@@ -6,7 +6,7 @@ ms.prod: windows-client
 author: nidos
 ms.author: nidos
 ms.topic: article
-ms.date: 12/31/2017
+ms.date: 05/09/2023
 ms.technology: itpro-updates
 ms.collection: tier3
 ---
@@ -18,7 +18,7 @@ ms.collection: tier3
 - Windows 10
 - Windows 11
 
-This article outlines how to create, provision, and deploy your Microsoft Connected Cache nodes. The creation and provisioning of your cache node takes place in Azure portal. The deployment of your cache node will require downloading an installer script that will be run on your cache server.
+This article outlines how to create, provision, and deploy your Microsoft Connected Cache nodes. The creation and provisioning of your cache node takes place in Azure portal. The deployment of your cache node requires downloading an installer script that will be run on your cache server.
 
 > [!IMPORTANT]
 > Before you can create your Microsoft Connected Cache, you will need to complete the [sign up process](mcc-isp-signup.md). You cannot proceed without signing up for our service.
@@ -37,7 +37,7 @@ During the configuration of your cache node, there are many fields for you to co
 
 ### Client routing
 
-Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you'll be able to route your clients to your cache node.
+Before serving traffic to your customers, client routing configuration is needed. During the configuration of your cache node in Azure portal, you're able to route your clients to your cache node.
 
 Microsoft Connected Cache offers two ways for you to route your clients to your cache node. The first method of manual entry involves uploading a comma-separated list of CIDR blocks that represents the clients. The second method of setting BGP (Border Gateway Protocol) is more automatic and dynamic, which is set up by establishing neighborships with other ASNs. All routing methods are set up within Azure portal.
 
@@ -53,7 +53,11 @@ You can manually upload a list of your CIDR blocks in Azure portal to enable man
 
 BGP (Border Gateway Protocol) routing is another method offered for client routing. BGP dynamically retrieves CIDR ranges by exchanging information with routers to understand reachable networks. For an automatic method of routing traffic, you can choose to configure BGP routing in Azure portal.
 
-Microsoft Connected Cache includes Bird BGP which enables the cache node to 1) establish iBGP peering sessions with routers, route servers, or route collectors within operator networks and 2)  act as a route collector. The operator will start the iBGP peering session from the Microsoft Connected Cache side using the Azure management portal and then start the session with the Microsoft Connected Cache node from the router.
+Microsoft Connected Cache includes Bird BGP, which enables the cache node to:
+ - Establish iBGP peering sessions with routers, route servers, or route collectors within operator networks 
+ - Act as a route collector 
+
+The operator starts the iBGP peering session from the Microsoft Connected Cache side using the Azure management portal and then starts the session with the Microsoft Connected Cache node from the router.
 
 In the example configuration below:
 - The operator ASN is 65100
@@ -64,7 +68,7 @@ In the example configuration below:
 
     :::image type="content" source="images/mcc-isp-bgp-diagram.png" alt-text="A diagram that shows the relationship between the cache node and other ASNs/routers when using BGP. BGP routing allows the cache node to route to other network providers with different ASNs." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::  
 
-To set up and enable BGP routing for your cache node, follow these steps below:
+To set up and enable BGP routing for your cache node, follow the steps below:
 
 1. Navigate to **Settings** > **Cache nodes**. Select the cache node you wish to provision.
 

windows/deployment/do/mcc-isp-overview.md

@@ -6,7 +6,7 @@ ms.prod: windows-client
 author: amymzhou
 ms.author: amyzhou
 ms.topic: article
-ms.date: 12/31/2017
+ms.date: 05/09/2023
 ms.technology: itpro-updates
 ms.collection: tier3
 ---

windows/deployment/do/waas-microsoft-connected-cache.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 ms.author: carmenf
 ms.topic: article
 ms.technology: itpro-updates
-ms.date: 12/31/2017
+ms.date: 05/09/2023
 ms.collection: tier3
 ---
 

windows/deployment/update/media-dynamic-update.md

@@ -8,7 +8,7 @@ ms.author: mstewart
 manager: aaroncz
 ms.topic: article
 ms.technology: itpro-updates
-ms.date: 12/31/2017
+ms.date: 05/09/2023
 ms.reviewer: stevedia
 ---