mcc-branding

windows/deployment/do/TOC.yml

@@ -33,21 +33,21 @@
   items:
     - name: What is Microsoft Connected Cache?
       href: waas-microsoft-connected-cache.md
-    - name: MCC for Enterprise and Education
+    - name: Connected Cache for Enterprise and Education
       items:
-      - name: MCC for Enterprise and Education Overview
+      - name: Connected Cache for Enterprise and Education Overview
         href: mcc-ent-edu-overview.md
       - name: Requirements
         href: mcc-enterprise-prerequisites.md
       - name: Deploy Microsoft Connected Cache
         href: mcc-enterprise-deploy.md
-      - name: Update or uninstall MCC
+      - name: Update or uninstall Connected Cache
         href: mcc-enterprise-update-uninstall.md
       - name: Appendix
         href: mcc-enterprise-appendix.md
-    - name: MCC for ISPs
+    - name: Connected Cache for ISPs
       items:
-      - name: MCC for ISPs Overview
+      - name: Connected Cache for ISPs Overview
         href: mcc-isp-overview.md
       - name: How-to guides
         items:  
@@ -67,7 +67,7 @@
           href: mcc-isp-vm-performance.md
         - name: Support and troubleshooting
           href: mcc-isp-support.md
-        - name: MCC for ISPs (early preview)
+        - name: Connected Cache for ISPs (early preview)
           href: mcc-isp.md
 - name: Endpoints for Microsoft Connected Cache content and services
   href: delivery-optimization-endpoints.md 

windows/deployment/do/mcc-isp-cache-node-configuration.md

@@ -27,8 +27,8 @@ All cache node configuration takes place within Azure portal. This article outli
 | Field Name | Expected Value| Description |
 | -- | --- | --- |
 | **Cache node name** | Alphanumeric string that contains no spaces  | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later. |
-| **Server IP address** | IPv4 address  | IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. |
+| **Server IP address** | IPv4 address  | IP address of your Microsoft Connected Cache server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. |
-| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, 10,000 Mbps.|
+| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your Connected Cache based on the specifications of your hardware. For example, 10,000 Mbps.|
 | **Enable cache node** | Enable or Disable | You can choose to enable or disable a cache node at any time. |
 
 ## Storage
@@ -42,6 +42,6 @@ All cache node configuration takes place within Azure portal. This article outli
 
 | Field Name | Expected Value| Description |
 | -- | --- | --- |
-| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
+| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the Connected Cache server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
 | **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. |
 | **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. |

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

@@ -84,7 +84,7 @@ To set up and enable BGP routing for your cache node, follow the steps below:
 1. Under **Routing information**, select the routing method you would like to use. For more information, see [Client routing](#client-routing).
 
     - If you choose **Manual routing**, enter your address range/CIDR blocks.  
-    - If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship. Use your ASN, the one used to sign up for MCC. MCC will be automatically assigned as the same ASN as the neighbor.
+    - If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship. Use your ASN, the one used to sign up for Microsoft Connected Cache. Connected Cache will be automatically assigned as the same ASN as the neighbor.
     > [!NOTE]
     > **Prefix count** and **IP Space** will stop displaying `0` when BGP is successfully established.
 
@@ -96,12 +96,12 @@ Once the user executes the cache server provisioning script, resources are creat
 
 #### IoT Edge
 
-IoT Edge performs several functions important to manage MCC on your edge device:
+IoT Edge performs several functions important to manage Connected Cache on your edge device:
 
-1. Installs and updates MCC on your edge device.
+1. Installs and updates Connected Cache on your edge device.
 1. Maintains Azure IoT Edge security standards on your edge device.
-1. Ensures that MCC is always running.
+1. Ensures that Connected Cache is always running.
-1. Reports MCC health and usage to the cloud for remote monitoring.
+1. Reports Connected Cache health and usage to the cloud for remote monitoring.
 
 #### Docker container engine
 
@@ -121,7 +121,7 @@ There are five IDs that the device provisioning script takes as input in order t
 #### Provision your server
 
 > [!IMPORTANT]
-> Have you correctly mounted your disk? Your MCC will not be successfully installed without this important step. Before provisioning your server, ensure your disk is correctly mounted by following the instructions here: [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk).
+> Have you correctly mounted your disk? Your Connected Cache will not be successfully installed without this important step. Before provisioning your server, ensure your disk is correctly mounted by following the instructions here: [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk).
 
 :::image type="content" source="images/mcc-isp-deploy-cache-node-numbered.png" alt-text="Screenshot of the server provisioning tab within cache node configuration in Azure portal.":::
 
@@ -145,8 +145,8 @@ There are five IDs that the device provisioning script takes as input in order t
 | Field Name | Expected Value| Description |
 |---|---|---|
 | **Cache node name** | Alphanumeric string that contains no spaces  | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later. |
-| **Server IP address** | IPv4 address  | IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. |
+| **Server IP address** | IPv4 address  | IP address of your Connected Cache server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. |
-| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, 10,000 Mbps.|
+| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your Connected Cache based on the specifications of your hardware. For example, 10,000 Mbps.|
 | **Enable cache node** | Enable or Disable | You can choose to enable or disable a cache node at any time. |
 
 ### Storage fields
@@ -164,6 +164,6 @@ There are five IDs that the device provisioning script takes as input in order t
 
 | Field Name | Expected Value| Description |
 |---|---|---|
-| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
+| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the Connected Cache server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 |
 | **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. |
 | **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. |

windows/deployment/do/mcc-isp-faq.yml

@@ -28,7 +28,7 @@ sections:
       - question: What will Microsoft Connected Cache do for me? How will it impact our customers?
         answer: As an ISP, your network can benefit from reduced load on your backbone and improve customer download experience for supported Microsoft static content. It will also help you save on CDN costs.  
       - question: I already peer with Microsoft(8075). What benefit will I receive by adding Microsoft Connected Cache to my network?
-        answer: MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC.  
+        answer: Microsoft Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing Connected Cache.  
       - question: Is there a non-disclosure agreement to sign?
         answer: No, a non-disclosure agreement isn't required.
       - question: What are the prerequisites and hardware requirements?
@@ -79,7 +79,7 @@ sections:
       - question: Is IPv6 supported?
         answer: No, we don't currently support IPV6. We plan to support it in the future.   
       - question: Is Microsoft Connected Cache stable and reliable?
-        answer: We have already successfully onboarded ISPs in many countries and regions around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of MCC before expanding to more customers.
+        answer: We have already successfully onboarded ISPs in many countries and regions around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of Connected Cache before expanding to more customers.
       - question: How does Microsoft Connected Cache populate its content?
         answer: Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There's no off-peak cache fill necessary. Microsoft Connected Cache will reach out to different CDN providers just like a client device would. The traffic flow from Microsoft Connected Cache will vary depending on how you currently transit to each of these CDN providers. The content can come from third party CDNs or from AFD.
       - question: What CDNs does Microsoft Connected Cache pull content from?
@@ -99,7 +99,7 @@ sections:
         answer: First, check that the email under the NOC role is correct in your PeeringDB page. If the email associated with NOC role is correct, search for an email from the sender "microsoft-noreply@microsoft.com" with the email subject - "Here's your Microsoft Connected Cache verification code" in your Spam folders. Still can't find it? Ensure that your email admin rules allow emails from the sender `microsoft-noreply@microsoft.com`.
       - question: I noticed I can set up BGP for routing. How does BGP routing work for Microsoft Connected Cache?
         answer: BGP routing can be set up as an automatic method of routing traffic. To learn more about how BGP is used with Microsoft Connected Cache, see [BGP Routing](mcc-isp-create-provision-deploy.md#bgp-routing).
-      - question: I have an active MCC, but I'm noticing I hit the message limit for my IoT Hub each day. Does this affect my MCC performance and should I be concerned?
+      - question: I have an active Connected Cache, but I'm noticing I hit the message limit for my IoT Hub each day. Does this affect my Connected Cache performance and should I be concerned?
-        answer: Even when the quota of 8k messages is hit, the MCC functionality isn't affected. Your client devices continue to download content as normal. You also won't be charged above the 8k message limit, so you don't need to worry at all about getting a paid plan. MCC will always be a free service. So if functionality isn't impacted, what is? Instead, messages about the configuration or edge deployment would be impacted. This means that if there was a request to update your MCC and the daily quota was reached, your MCC might not update. In that case, you would just need to wait for the next day to update. This is only a limitation of the early preview and isn't an issue during public preview.
+        answer: Even when the quota of 8k messages is hit, the Connected Cache functionality isn't affected. Your client devices continue to download content as normal. You also won't be charged above the 8k message limit, so you don't need to worry at all about getting a paid plan. Connected Cache will always be a free service. So if functionality isn't impacted, what is? Instead, messages about the configuration or edge deployment would be impacted. This means that if there was a request to update your Connected Cache and the daily quota was reached, your Connected Cache might not update. In that case, you would just need to wait for the next day to update. This is only a limitation of the early preview and isn't an issue during public preview.
       - question: What do I do if I need more support and have more questions even after reading this FAQ page?
         answer: For further support for Microsoft Connected Cache, visit [Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview)](mcc-isp-support.md).

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

@@ -1,6 +1,6 @@
 ---
-title: MCC for ISPs Overview
+title: Microsoft Connected Cache for ISPs Overview
-description: Overview of Microsoft Connected Cache for ISPs. Learn about how MCC works, supported scenarios, and supported content.
+description: Overview of Microsoft Connected Cache for ISPs. Learn about how Connected Cache works, supported scenarios, and supported content.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: overview
@@ -18,7 +18,7 @@ ms.date: 05/23/2024
 
 # Microsoft Connected Cache for ISPs overview
 
-Microsoft Connected Cache (MCC) for Internet Service Providers (preview) is a free software-only caching solution that delivers Microsoft content. MCC can be deployed free of charge to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, MCC can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing.
+Microsoft Connected Cache for Internet Service Providers (preview) is a free software-only caching solution that delivers Microsoft content. Connected Cache can be deployed free of charge to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, Connected Cache can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing.
 
 ## Supported scenarios
 
@@ -41,40 +41,40 @@ For the full list of content endpoints that Microsoft Connected Cache for ISPs s
 
 ### Are you already peering with 8075?
 
-MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC.
+Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing Connected Cache.
 
 :::image type="content" source="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png" alt-text="Chart containing Peering vs Cache Content Traffic." lightbox="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png":::
 
-## How MCC works
+## How Connected Cache works
 
 :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png":::
 
-The following steps describe how MCC is provisioned and used:
+The following steps describe how Connected Cache is provisioned and used:
 
-1. The Azure portal is used to create and manage MCC nodes.
+1. The Azure portal is used to create and manage Connected Cache nodes.
 
-1. A shell script is used to provision the server and deploy the MCC application.
+1. A shell script is used to provision the server and deploy the Connected Cache application.
 
-1. A combination of the Azure portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the MCC server.
+1. A combination of the Azure portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the Connected Cache server.
 
     - The publicly accessible IPv4 address of the server is configured on the portal.
 
-    - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
+    - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the Connected Cache node.
 
-    - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the MCC node.
+    - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the Connected Cache node.
 
         > [!NOTE]
         > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.
 
-1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding MCC node.
+1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding Connected Cache node.
 
-1. Microsoft clients make the range requests for content from the MCC node.
+1. Microsoft clients make the range requests for content from the Connected Cache node.
 
-1. An MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+1. An Connected Cache node gets 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 be served from cache.
 
-1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
+1. If the Connected Cache node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
 
 ### Hardware recommendation
 

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

@@ -36,7 +36,7 @@ During sign-up, a verification code is sent to your NOC email address present in
 
 #### Unable to re-sign up
 
-Delete any MCC resource that you're using before you resign up for the service. Deleting any existing MCC resource unlocks your ASN, which allows you to successfully sign up.
+Delete any Microsoft Connected Cache resource that you're using before you resign up for the service. Deleting any existing Connected Cache resource unlocks your ASN, which allows you to successfully sign up.
 
 ### Cache Node Errors  
 
@@ -100,9 +100,9 @@ iotedge check -verbose
 
 ## Diagnose and Solve Problems
 
-If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
+If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your Connected Cache resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
 
-You can find **Diagnose and solve problems** on the left pane within your MCC resource.
+You can find **Diagnose and solve problems** on the left pane within your Connected Cache resource.
 
 :::image type="content" source="images/mcc-isp-diagnose-solve.png" alt-text="A screenshot of Azure portal showing the Diagnose and Solve problems tab on the left hand pane of Azure portal." lightbox="images/mcc-isp-diagnose-solve.png":::
 

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

@@ -33,7 +33,7 @@ To view which version your cache nodes are currently on, navigate to the **Cache
 There are two main steps required to uninstall your cache node:
 
 1. Remove your cache node from Azure portal
-1. Run the uninstall script to cleanly remove MCC from your server
+1. Run the uninstall script to cleanly remove Microsoft Connected Cache from your server
 
 You must complete both steps to ensure a clean uninstall of your cache node.
 
@@ -50,7 +50,7 @@ The **uninstallmcc.sh** script removes the following components:
 - IoT Edge
 - Edge Agent
 - Edge Hub
-- MCC
+- Connected Cache
 - Moby CLI
 - Moby engine
 

windows/deployment/do/mcc-isp-verify-cache-node.md

@@ -49,7 +49,7 @@ Sign into the [Azure portal](https://www.portal.azure.com) and navigate to the *
 
 It can take a few minutes for the container to deploy after you've saved the configuration.
 
-To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
+To validate a properly functioning Microsoft Connected Cache, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
 
 ```bash
 wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com

windows/deployment/do/mcc-isp-vm-performance.md

@@ -25,7 +25,7 @@ The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install
 
 #### NIC requirements
 
-- Multiple NICs on a single MCC instance are supported using a *link aggregated* configuration.
+- Multiple NICs on a single Microsoft Connected Cache instance are supported using a *link aggregated* configuration.
 - 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
 
 #### Drive performance
@@ -55,9 +55,9 @@ Change the following settings to maximize the egress in virtual environments:
 
 1. Enable **Single Root I/O Virtualization (SR-IOV)** in the following three locations:
 
-    - The BIOS of the MCC virtual machine
+    - The BIOS of the Connected Cache virtual machine
-    - The network card properties of the MCC virtual machine
+    - The network card properties of the Connected Cache virtual machine
-    - The hypervisor for the MCC virtual machine
+    - The hypervisor for the Connected Cache virtual machine
 
     Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment.
 

windows/deployment/do/mcc-isp.md

@@ -1,6 +1,6 @@
 ---
 title: Microsoft Connected Cache for ISPs
-description: This article contains details about the early preview for Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs).
+description: This article contains details about the early preview for Microsoft Connected Cache for Internet Service Providers (ISPs).
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
@@ -24,57 +24,57 @@ appliesto:
 
 ## Overview
 
-Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within operator networks. MCC can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads.
+Microsoft Connected Cache preview is a software-only caching solution that delivers Microsoft content within operator networks. Connected Cache can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads.
 
 Microsoft Connected Cache is a hybrid application, in that it's a mix of on-premises and cloud resources. It's composed of a Docker-compatible Linux container deployed to your server and a cloud management portal. Microsoft chose Azure IoT Edge as a secure and reliable control plane. For more information on IoT Edge, see the [Appendix](#appendix). Even though your scenario isn't related to IoT, Azure IoT Edge is our secure Linux container deployment and management infrastructure.
 
-## How MCC works
+## How Connected Cache works
 
 :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png":::
 
-The following steps describe how MCC is provisioned and used:
+The following steps describe how Connected Cache is provisioned and used:
 
-1. The Azure Management Portal is used to create and manage MCC nodes.
+1. The Azure Management Portal is used to create and manage Connected Cache nodes.
 
-1. A shell script is used to provision the server and deploy the MCC application.
+1. A shell script is used to provision the server and deploy the Connected Cache application.
 
-1. A combination of the Azure Management Portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the MCC server.
+1. A combination of the Azure Management Portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the Connected Cache server.
 
     - The publicly accessible IPv4 address of the server is configured on the portal.
 
-    - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node.
+    - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the Connected Cache node.
 
-    - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the MCC node.
+    - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the Connected Cache node.
 
         > [!NOTE]
         > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.
 
-1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding MCC node.
+1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding Connected Cache node.
 
-1. Microsoft clients make the range requests for content from the MCC node.
+1. Microsoft clients make the range requests for content from the Connected Cache node.
 
-1. An MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+1. A Connected Cache node gets 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 be served from cache.
 
-1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
+1. If the Connected Cache node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
 
-## ISP requirements for MCC
+## ISP requirements for Connected Cache
 
 Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit  [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding.
 
 <!-- ### Azure subscription
 
-The MCC management portal is hosted within Azure. It's used to create the Connected Cache Azure resource and IoT Hub resource. Both are *free* services.
+The Connected Cache management portal is hosted within Azure. It's used to create the Connected Cache Azure resource and IoT Hub resource. Both are *free* services.
 
 > [!NOTE]
 > If you request Exchange or Public peering in the future, business email addresses must be used to register ASNs. Microsoft doesn't accept Gmail or other non-business email addresses.
 
-Your Azure subscription ID is first used to provision MCC services and enable access to the preview. The MCC server requirement for an Azure subscription will cost you nothing. If you don't have an Azure subscription already, you can create an Azure [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure free account FAQ](https://azure.microsoft.com/free/free-account-faq/). *Don't submit a trial subscription* as you'll lose access to your Azure resources after the trial period ends.
+Your Azure subscription ID is first used to provision Connected Cache services and enable access to the preview. The Connected Cache server requirement for an Azure subscription will cost you nothing. If you don't have an Azure subscription already, you can create an Azure [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure free account FAQ](https://azure.microsoft.com/free/free-account-faq/). *Don't submit a trial subscription* as you'll lose access to your Azure resources after the trial period ends.
 
 The resources used for the preview, and in the future when this product is ready for production, will be free to you - like other caching solutions.
 
-### Hardware to host the MCC
+### Hardware to host the Connected Cache
 
 This recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
 
@@ -87,12 +87,12 @@ This recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC
 
 #### NIC requirements
 
-- Multiple NICs on a single MCC instance are supported using a *link aggregated* configuration.
+- Multiple NICs on a single Connected Cache instance are supported using a *link aggregated* configuration.
 - 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
 
 ### Sizing recommendations
 
-The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice. The following recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
+The Connected Cache module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a physical server or VM of your choice. The following recommended configuration can egress at a rate of 9 Gbps with a 10 Gbps NIC.
 
 | Component  | Minimum | Recommended |
 |---|---|---|
@@ -102,28 +102,28 @@ The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a
 | Memory | 8 GB | 32 GB or greater |
 | Cores | 4 | 8 or more  | -->
 
-<!-- ## Steps to deploy MCC
+<!-- ## Steps to deploy Connected Cache
 
-To deploy MCC:
+To deploy Connected Cache:
 
 1. [Provide Microsoft with your Azure subscription ID](#provide-microsoft-with-your-azure-subscription-id)
-2. [Create the MCC Resource in Azure](#create-the-mcc-resource-in-azure)
+2. [Create the Connected Cache Resource in Azure](#create-the-mcc-resource-in-azure)
 3. [Create a Cache Node](#create-an-mcc-node-in-azure)
 4. [Configure Cache Node Routing](#edit-cache-node-information)
-5. [Install MCC on a physical server or VM](#install-mcc)
+5. [Install Connected Cache on a physical server or VM](#install-mcc)
-6. [Verify properly functioning MCC server](#verify-properly-functioning-mcc-server)
+6. [Verify properly functioning Connected Cache server](#verify-properly-functioning-mcc-server)
 7. [Review common issues if needed](#common-issues)
 
 ## Provide Microsoft with your Azure subscription ID
 
-As part of the MCC preview onboarding process, an Azure subscription ID must be provided to Microsoft.
+As part of the Connected Cache preview onboarding process, an Azure subscription ID must be provided to Microsoft.
 
 > [!IMPORTANT]
 > For information about creating or locating your subscription ID, see [Steps to obtain an Azure subscription ID](#steps-to-obtain-an-azure-subscription-id).
 
-### Create the MCC resource in Azure
+### Create the Connected Cache resource in Azure
 
-The MCC Azure management portal is used to create and manage MCC nodes. An Azure subscription ID is used to grant access to the preview and to create the MCC resource in Azure and cache nodes.
+The Connected Cache Azure management portal is used to create and manage Connected Cache nodes. An Azure subscription ID is used to grant access to the preview and to create the Connected Cache resource in Azure and cache nodes.
 
 Operators who have been given access to the program will be sent a link to the Azure portal, which will allow you to create this resource.
 
@@ -140,20 +140,20 @@ Operators who have been given access to the program will be sent a link to the A
     > [!IMPORTANT]
     > Don't select *Connected Cache Resources*, which is different from **Microsoft Connected Cache**.
 
-1. Select **Create** on the next screen to start the process of creating the MCC resource.
+1. Select **Create** on the next screen to start the process of creating the Connected Cache resource.
 
     :::image type="content" source="./images/mcc-isp-create.png" alt-text="Screenshot of the Create option for the Microsoft Connected Cache service.":::
 
-1. Fill in the following required fields to create the MCC resource:
+1. Fill in the following required fields to create the Connected Cache resource:
 
     - Choose the **Subscription** that you provided to Microsoft.
 
     - Azure resource groups are logical groups of resources. Create a new **Resource group** and choose a name for it.
 
-    - Choose **(US) West US** for the **Location** of the resource. This choice won't impact MCC if the physical location isn't in the West US, it's just a limitation of the preview.
+    - Choose **(US) West US** for the **Location** of the resource. This choice won't impact Connected Cache if the physical location isn't in the West US, it's just a limitation of the preview.
 
         > [!NOTE]
-        > Your MCC resource won't create properly if you don't select **(US) West US**.
+        > Your Connected Cache resource won't create properly if you don't select **(US) West US**.
 
     - Specify a **Connected Cache Resource Name**.
 
@@ -173,13 +173,13 @@ If you get the error message "Validation failed" in the Azure portal, it's likel
 
 If you get the error message "Could not create marketplace item" in the Azure portal, use the following steps to troubleshoot:
 
-- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create an MCC resource.
+- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create an Connected Cache resource.
 
 - Make sure that you're using the same subscription that you provided to Microsoft and you have privileges to create an Azure resource.
 
 - If the issue persists, clear your browser cache and start in a new window.
 
-### Create an MCC node in Azure
+### Create an Connected Cache node in Azure
 
 1. After you successfully create the resource, select **Go to resource**.
 
@@ -196,9 +196,9 @@ If you get the error message "Could not create marketplace item" in the Azure po
     | Field name | Expected value | Description |
     |--|--|--|
     | **Cache Node Name** | Alphanumeric name that includes no spaces. | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later. |
-    | **Server IP Address** | IPv4 Address | IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. *The IP address must be publicly accessible.* |
+    | **Server IP Address** | IPv4 Address | IP address of your Connected Cache server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. *The IP address must be publicly accessible.* |
-    | **Max Allowable Egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, `10,000` Mbps. |
+    | **Max Allowable Egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your Connected Cache based on the specifications of your hardware. For example, `10,000` Mbps. |
-    | **Address Range/CIDR Blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: `2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24` |
+    | **Address Range/CIDR Blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the Connected Cache server as a comma separated list. For example: `2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24` |
     | **Enable Cache Node** | Enable or Disable | **Enable** permits the cache node to receive content requests. </br>**Disable** prevents the cache node from receiving content requests. </br>Cache nodes are enabled by default. |
 
     :::image type="content" source="./images/mcc-isp-create-cache-node-fields.png" alt-text="Screenshot of the available fields on the Create Cache Node page.":::
@@ -213,7 +213,7 @@ If you get the error message "Could not create marketplace item" in the Azure po
      | Field name | Description |
      |--|--|
      | **IP Space** | Number of IP addresses that will be routed to your cache server. |
-    | **Activation Keys** | Set of keys to activate your cache node with the MCC services. Copy the keys for use during install. The CustomerID is your Azure subscription ID. |
+    | **Activation Keys** | Set of keys to activate your cache node with the Connected Cache services. Copy the keys for use during install. The CustomerID is your Azure subscription ID. |
 
 1. Enter the information to create the cache node, and then select **Create**.
 
@@ -229,13 +229,13 @@ See the following example with all information entered:
 
 :::image type="content" source="./images/mcc-isp-create-node-form.png" alt-text="Screenshot of the Create Cache Node page with all information entered.":::
 
-Once you create the MCC node, it will display the installer instructions. For more information on the installer instructions, see the [Install Connected Cache](#install-mcc) section.
+Once you create the Connected Cache node, it will display the installer instructions. For more information on the installer instructions, see the [Install Connected Cache](#install-mcc) section.
 
 :::image type="content" source="./images/mcc-isp-success-instructions.png" alt-text="Screenshot of the Cache node successfully created with Connected Cache installer instructions.":::
 
 ### IP address space approval
 
-There are three states for IP address space. MCC configuration supports BGP and has automatic routing capabilities.
+There are three states for IP address space. Connected Cache configuration supports BGP and has automatic routing capabilities.
 
 - **Valid**: The IP address space is approved.
 
@@ -255,23 +255,23 @@ There are three states for IP address space. MCC configuration supports BGP and
 
 :::image type="content" source="./images/mcc-isp-list-nodes.png" alt-text="Screenshot of the Cache Nodes list in the Azure portal.":::
 
-To modify the configuration for existing MCC nodes in the portal, select the cache node name in the cache nodes list. This action opens the **Cache Node Configuration** page. You can edit the **Server IP Address** or **Address Range/CIDR Blocks** field. You can also enable or disable the cache node.
+To modify the configuration for existing Connected Cache nodes in the portal, select the cache node name in the cache nodes list. This action opens the **Cache Node Configuration** page. You can edit the **Server IP Address** or **Address Range/CIDR Blocks** field. You can also enable or disable the cache node.
 
 :::image type="content" source="./images/mcc-isp-node-configuration.png" alt-text="Screenshot of the Cache Node Configuration page, highlighting editable fields.":::
 
 To delete a cache node, select it in the cache nodes list, and then select **Delete** in the toolbar. If you delete a cache node, there's no way to recover it or any of the information related to the cache node. -->
 
-<!-- ## Install MCC
+<!-- ## Install Connected Cache
 
-To install MCC on your physical server or VM, you use a Bash script installer, which runs the following tasks:
+To install Connected Cache on your physical server or VM, you use a Bash script installer, which runs the following tasks:
 
 - Installs the Moby engine and CLI.
 - Installs IoT Edge.
 - Installs SSH to support remote access to the server.
-- Enables the firewall and opens port 80 for inbound and outbound traffic. The MCC uses port 80.
+- Enables the firewall and opens port 80 for inbound and outbound traffic. The Connected Cache uses port 80.
 - Configures Connected Cache tuning settings.
 - Creates the necessary free Azure resource: IoT Hub/IoT Edge.
-- Deploys the MCC container to the server.
+- Deploys the Connected Cache container to the server.
 
 > [!IMPORTANT]
 > Make sure that the following ports are open so that Microsoft can verify proper functionality of the cache server:
@@ -283,7 +283,7 @@ To install MCC on your physical server or VM, you use a Bash script installer, w
 > - 5671: IoT Edge communication/container management
 > - 8883: IoT Edge communication/container management
 
-### Steps to install MCC
+### Steps to install Connected Cache
 
 Before you start, make sure that you have a data drive configured on your server. You'll need to specify the location for this cache drive during this process. The minimum size for the data drive is 100 GB. For instructions to mount a disk on a Linux VM, see [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk).
 
@@ -296,8 +296,8 @@ Before you start, make sure that you have a data drive configured on your server
     - Diagnostics folder: Used to create diagnostics support bundle.
     - **installmcc.sh**: Main installer file.
     - **installIotEdge.sh**: Installs the necessary prerequisites. For example, IoT Edge runtime and Docker. It also makes necessary host OS settings to optimize caching performance.
-    - **resourceDeploymentForConnectedCache.sh**: Creates Azure cloud resources required to support the MCC control plane.
+    - **resourceDeploymentForConnectedCache.sh**: Creates Azure cloud resources required to support the Connected Cache control plane.
-    - **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the MCC container. It also configures settings on the container like cache drives location and sizes.
+    - **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the Connected Cache container. It also configures settings on the container like cache drives location and sizes.
     - **mccupdate.json**
     - **packagever.txt**
     - **uninstallmcc.sh**: Main uninstaller file.
@@ -345,9 +345,9 @@ Before you start, make sure that you have a data drive configured on your server
 
 1. Specify whether you have an existing IoT Hub.
 
-    - If this process is for your *first MCC deployment*, enter `n`.
+    - If this process is for your *first Connected Cache deployment*, enter `n`.
 
-    - If you already have an MCC deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue.
+    - If you already have an Connected Cache deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue.
 
     :::image type="content" source="./images/mcc-isp-bash-iot-prompt.png" alt-text="Screenshot of the Bash script output with steps for existing IoT Hub." lightbox="./images/mcc-isp-bash-iot-prompt.png":::
 
@@ -355,16 +355,16 @@ Before you start, make sure that you have a data drive configured on your server
 
     1. Enter the number of BGP neighbors you want to configure.
     1. Enter the IP address for the neighbor.
-    1. Enter the ASN corresponding to that neighbor. This value should be the same ASN as the MCC -iBGP connection.
+    1. Enter the ASN corresponding to that neighbor. This value should be the same ASN as the Connected Cache -iBGP connection.
     1. Repeat these steps for each neighbor you need to configure.
 
     > [!NOTE]
     > With the BGP configuration, you're essentially setting up an iBGP neighbor in your public ASN. For example, when you initiate the BGP session from the router to the cache node, you would use your own ASN.
 
-1. BGP is now configured from the MCC side. From your end, establish a neighborship from your router to MCC's host machine. Use the IP address of the host machine that's running the MCC container.
+1. BGP is now configured from the Connected Cache side. From your end, establish a neighborship from your router to Connected Cache's host machine. Use the IP address of the host machine that's running the Connected Cache container.
 
     1. Make sure there aren't any firewall rules blocking this connection.
-    1. Verify that the BGP connection has been established and that you're advertising routes to the MCC.
+    1. Verify that the BGP connection has been established and that you're advertising routes to the Connected Cache.
     1. Wait five minutes to refresh the cache node page in the Azure portal to see the BGP routes.
 
 1. Confirm the update is complete by running the following command.
@@ -373,9 +373,9 @@ Before you start, make sure that you have a data drive configured on your server
     sudo iotedge list
     ```
 
-    Make sure MCC is running on the latest version. If you only see **edgeAgent** and **edgeHub**, wait five minutes and run this command again.
+    Make sure Connected Cache is running on the latest version. If you only see **edgeAgent** and **edgeHub**, wait five minutes and run this command again.
 
-1. Make sure MCC is reachable. Replace `<CacheServerIp>` with the IP address of your MCC or localhost.
+1. Make sure Connected Cache is reachable. Replace `<CacheServerIp>` with the IP address of your Connected Cache or localhost.
 
     ```bash
     wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
@@ -387,7 +387,7 @@ Before you start, make sure that you have a data drive configured on your server
 
     :::image type="content" source="./images/mcc-isp-use-bgp.png" alt-text="Screenshot of the Cache Node Configuration page with the Prefix Source set to Use BGP.":::
 
-1. If there are no errors, go to the next section to verify the MCC server.
+1. If there are no errors, go to the next section to verify the Connected Cache server.
 
     If there are errors:
 
@@ -395,7 +395,7 @@ Before you start, make sure that you have a data drive configured on your server
 
     - For more information, see [Troubleshoot your IoT Edge device](/azure/iot-edge/troubleshoot). -->
 
-## Verify properly functioning MCC server
+## Verify properly functioning Connected Cache server
 
 ### Verify client side
 
@@ -421,7 +421,7 @@ For example, this command provides the current status of the starting and stoppi
 
 It can take a few minutes for the container to deploy.
 
-To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
+To validate a properly functioning Connected Cache, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
 
 ```bash
 wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
@@ -511,11 +511,11 @@ To configure the device to work with your DNS, use the following steps:
 
 <!-- ### Diagnostics script
 
-If you're having issues with your MCC, the installer file includes a diagnostics script. The script collects all logs and zips them into a single file. 
+If you're having issues with your Connected Cache, the installer file includes a diagnostics script. The script collects all logs and zips them into a single file. 
 
 To run the script:
 
-1. Navigate to the following folder in the MCC installation files:
+1. Navigate to the following folder in the Connected Cache installation files:
 
     `mccinstaller > MccResourceInstall > Diagnostics`
 
@@ -526,15 +526,15 @@ To run the script:
     sudo ./collectMccDiagnostics.sh
     ```
 
-1. The script stores all the debug files into a folder and creates a tar file. After the script is finished running, it displays the path of the tar file that you can share with the MCC team. The file should be `/etc/mccdiagnostics/support_bundle_\$timestamp.tar.gz`
+1. The script stores all the debug files into a folder and creates a tar file. After the script is finished running, it displays the path of the tar file that you can share with the Connected Cache team. The file should be `/etc/mccdiagnostics/support_bundle_\$timestamp.tar.gz`
 
-1. [Email the MCC team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process. -->
+1. [Email the Connected Cache team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process. -->
 
-<!-- ## Updating your MCC
+<!-- ## Updating your Connected Cache
 
-Throughout the early preview phase, Microsoft will release security and feature updates for MCC. Follow these steps to update your MCC.
+Throughout the early preview phase, Microsoft will release security and feature updates for Connected Cache. Follow these steps to update your Connected Cache.
 
-Run the following commands, replacing the variables with the values provided in the email to update your MCC:
+Run the following commands, replacing the variables with the values provided in the email to update your Connected Cache:
 
 ```bash
 sudo chmod +x updatemcc.sh
@@ -548,20 +548,20 @@ For example:
 sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.981" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99aa"
 ``` -->
 
-<!-- ### Configure BGP on an Existing MCC
+<!-- ### Configure BGP on an Existing Connected Cache
 
-If you have an MCC that's already active and running, follow the steps below to configure BGP.
+If you have an Connected Cache that's already active and running, follow the steps below to configure BGP.
 
 1. Run the Update commands as described above.
 
 1. Sign in with your Azure credentials using the device code.
 
-1. To finish configuring your MCC with BGP routing, continue from Step 10 of [Steps to Install MCC](#steps-to-install-mcc). -->
+1. To finish configuring your Connected Cache with BGP routing, continue from Step 10 of [Steps to Install Connected Cache](#steps-to-install-mcc). -->
 
 
-## Uninstalling MCC
+## Uninstalling Connected Cache
 
-In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation.
+In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls Connected Cache and all the related components. Before you run this script, contact the Connected Cache team. Only run it if you're facing issues with Connected Cache installation.
 
 > [!WARNING]
 > Be cautious before running this script. It will also erase existing IoT workflows in this VM.
@@ -571,7 +571,7 @@ The **uninstallmcc.sh** script removes the following components:
 - IoT Edge
 - Edge Agent
 - Edge Hub
-- MCC
+- Connected Cache
 - Moby CLI
 - Moby engine
 
@@ -589,25 +589,25 @@ sudo ./uninstallmcc.sh
 <!--Using include file, get-azure-subscription.md, for shared content-->
 [!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)]
 
-### Performance of MCC in virtual environments
+### Performance of Connected Cache in virtual environments
 
 In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings:
 
 1. Enable **SR-IOV** in the following three locations:
 
-    - The BIOS of the MCC VM
+    - The BIOS of the Connected Cache VM
-    - The MCC VM's network card properties
+    - The Connected Cache VM's network card properties
-    - The hypervisor for the MCC VM
+    - The hypervisor for the Connected Cache VM
 
     Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment.
 
 2. Enable "high performance" in the BIOS instead of energy savings. Microsoft has found this setting nearly doubled egress in a Microsoft Hyper-V deployment.
 
-### Grant other users access to manage your MCC
+### Grant other users access to manage your Connected Cache
 
 More users can be given access to manage Microsoft Connected Cache, even if they don't have an Azure account. Once you've created the first cache node in the portal, you can add other users as **Owners** of the Microsoft Connected Cache resource group and the Microsoft Connected Cache resource.
 
-For more information on how to add other users as an owner, see [Grant a user access to Azure resources using the Azure portal](/azure/role-based-access-control/quickstart-assign-role-user-portal). Make sure to do this action for both the *MCC resource* and *MCC resource group*.
+For more information on how to add other users as an owner, see [Grant a user access to Azure resources using the Azure portal](/azure/role-based-access-control/quickstart-assign-role-user-portal). Make sure to do this action for both the *Connected Cache resource* and *Connected Cache resource group*.
 
 ### Setting up a VM on Windows Server
 
@@ -708,7 +708,7 @@ You can use hardware that will natively run Ubuntu 20.04 LTS, or you can run an
     >
     > :::image type="content" source="./images/mcc-isp-ubuntu-upgrade.png" alt-text="Screenshot of the Ubuntu install's Upgrade Available prompt with Don't Upgrade selected.":::
 
-Your Ubuntu VM is now ready to install MCC.
+Your Ubuntu VM is now ready to install Connected Cache.
 
 ### IoT Edge runtime
 

windows/deployment/do/waas-delivery-optimization-faq.yml

@@ -113,8 +113,8 @@ sections:
           For more information, see [Endpoints for Delivery Optimization and Microsoft Connected Cache](../do/delivery-optimization-endpoints.md) for a list of all content endpoints needed.
       - question: My firewall requires IP addresses and can't process FQDNs. How do I configure it to download content with Delivery Optimization?
         answer: | 
-          Microsoft content, such as Windows updates, are hosted and delivered globally via Content Delivery Networks (CDNs) and [Microsoft Connected Cache](waas-microsoft-connected-cache.md) (MCC) servers, which are hosted within Internet Service Provider (ISP) networks. 
+          Microsoft content, such as Windows updates, are hosted and delivered globally via Content Delivery Networks (CDNs) and [Microsoft Connected Cache](waas-microsoft-connected-cache.md) servers, which are hosted within Internet Service Provider (ISP) networks. 
-          The network of CDNs and MCCs allows Microsoft to reach the scale required to meet the demand of the Windows user base. Given this delivery infrastructure changes dynamically, providing an exhaustive list of IPs and keeping it up to date isn't feasible.  
+          The network of CDNs and Microsoft Connected Caches allows Microsoft to reach the scale required to meet the demand of the Windows user base. Given this delivery infrastructure changes dynamically, providing an exhaustive list of IPs and keeping it up to date isn't feasible.  
       - question: What is the recommended configuration for Delivery Optimization used with cloud proxies?
         answer: |
           The recommended configuration for Delivery Optimization peer-to-peer to work most efficiently along with cloud proxy solutions (for example, Zscaler) is to allow traffic to the Delivery Optimization services to go directly to the internet and not through the cloud proxy.
@@ -131,8 +131,8 @@ sections:
           Delivery Optimization uses the cache content on the device to determine what's available for peering. For the upload source device, there's a limited number (4) of slots for cached content that's available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots.
       - question: Where does Delivery Optimization get content from first?
         answer: |
-          When Delivery Optimization client is configured to use peers and Microsoft Connected Cache (MCC), the client connects to both MCC and peers in parallel. There is no prioritization between the two. Once downloading starts in parallel, Delivery Optimization 
+          When Delivery Optimization client is configured to use peers and Microsoft Connected Cache, the client connects to both Connected Cache and peers in parallel. There is no prioritization between the two. Once downloading starts in parallel, Delivery Optimization 
-          will taper off requests to the HTTP source (CDN or MCC) when the peer connections are able to reach the target download speed. For background downloads, Delivery Optimization will drop HTTP connections if peers are meeting the minimum QoS speed. To manage delaying the default behavior
+          will taper off requests to the HTTP source (CDN or Connected Cache) when the peer connections are able to reach the target download speed. For background downloads, Delivery Optimization will drop HTTP connections if peers are meeting the minimum QoS speed. To manage delaying the default behavior
           there are a collection of policies that can be used. For more information, see [Delivery Optimization delay policies](waas-delivery-optimization-reference.md#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources).
       - question: Does Delivery Optimization use multicast?
         answer: |

windows/deployment/do/waas-delivery-optimization-monitor.md

@@ -24,7 +24,7 @@ To monitor Delivery Optimization, you can use either the Windows Update for Busi
 
 ## Monitor with Windows Update for Business Delivery Optimization report
 
-Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache (MCC), HTTP source/CDN distribution over the past 28 days.
+Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache, HTTP source/CDN distribution over the past 28 days.
 
 :::image type="content" source="../update/media/wufb-do-overview.png" alt-text="This screenshot shows the Windows Update for Business report, Delivery Optimization status in Update Compliance." lightbox= "../update/media/wufb-do-overview.png":::
 
@@ -49,7 +49,7 @@ For details, see [Windows Update for Business Delivery Optimization Report](/win
 | BytesFromHTTP | Total number of bytes received over HTTP. This metric represents all HTTP sources, **which includes BytesFromCacheServer** |
 | Status | Current state of the operation. Possible values are: **Downloading** (download in progress); **Complete** (download completed, but isn't uploading yet); **Caching** (download completed successfully and is ready to upload or uploading); **Paused** (download/upload paused by caller) |
 | Priority | Priority of the download; values are **foreground** or **background** |
-| BytesFromCacheServer | Total number of bytes received from cache server (MCC) |
+| BytesFromCacheServer | Total number of bytes received from cache server (Connected Cache) |
 | BytesFromLanPeers | Total number of bytes received from peers found on the LAN |
 | BytesFromGroupPeers | Total number of bytes received from peers found in the group. (Note: Group mode is LAN + Group. If peers are found on the LAN, those bytes are registered in 'BytesFromLANPeers'.)  |
 | BytesFromInternetPeers | Total number of bytes received from internet peers |