diff --git a/windows/client-management/mdm/policy-csp-deliveryoptimization.md b/windows/client-management/mdm/policy-csp-deliveryoptimization.md index 2d2289e957..c058b8bccf 100644 --- a/windows/client-management/mdm/policy-csp-deliveryoptimization.md +++ b/windows/client-management/mdm/policy-csp-deliveryoptimization.md @@ -164,7 +164,7 @@ One or more values can be added as either fully qualified domain names (FQDN) or > [!NOTE] -> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to an Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client. +> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to a Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client. diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index a028e5929c..097f3c1c5c 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -33,7 +33,7 @@ items: - name: What is Microsoft Connected Cache? href: waas-microsoft-connected-cache.md - - name: Connected Cache for Enterprise and Education + - name: Microsoft Connected Cache for Enterprise and Education items: - name: Connected Cache for Enterprise and Education Overview href: mcc-ent-edu-overview.md @@ -45,7 +45,7 @@ href: mcc-enterprise-update-uninstall.md - name: Appendix href: mcc-enterprise-appendix.md - - name: Connected Cache for ISPs + - name: Microsoft Connected Cache for ISPs items: - name: Connected Cache for ISPs Overview href: mcc-isp-overview.md diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md index aab4bc87d2..0a0239d690 100644 --- a/windows/deployment/do/mcc-enterprise-appendix.md +++ b/windows/deployment/do/mcc-enterprise-appendix.md @@ -82,7 +82,7 @@ communication operations. The runtime performs several functions: For more information on Azure IoT Edge, see the [Azure IoT Edge documentation](/azure/iot-edge/about-iot-edge). -## Routing local Windows clients to an Connected Cache +## Routing local Windows clients to a Connected Cache ### Get the IP address of your Connected Cache using ifconfig diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index 4344f22ca4..0d3426ca7a 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -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 Connected Cache resource. +- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create a 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 Connected Cache node in Azure +### Create a Connected Cache node in Azure 1. After you successfully create the resource, select **Go to resource**. @@ -347,7 +347,7 @@ Before you start, make sure that you have a data drive configured on your server - If this process is for your *first Connected Cache deployment*, enter `n`. - - 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. + - If you already have a 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"::: @@ -550,7 +550,7 @@ sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-u