From abaeedfaae4943653fc8be265a38f58332dea371 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Tue, 1 Mar 2022 12:19:16 -0800 Subject: [PATCH] mcc --- windows/deployment/do/mcc-enterprise.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-enterprise.md b/windows/deployment/do/mcc-enterprise.md index 8d3dad4442..df419a776b 100644 --- a/windows/deployment/do/mcc-enterprise.md +++ b/windows/deployment/do/mcc-enterprise.md @@ -42,7 +42,7 @@ For more details information on Azure IoT Edge, please see the [Azure IoT Edge d 1. The Azure Management Portal used to create the MCC nodes. 2. The MCC container deployed and provisioned to the server using the installer provided in the portal. -3. Set the client policy in your management solution to point to the IP Address/FQDN of the cache server +3. Set the client policy in your management solution to point to the IP address/FQDN of the cache server 4. Microsoft end-user devices make the range requests for content from the MCC node. 5. MCC node pulls content from the CDN, seeds its local cache stored on disk and delivers the content to the client. 6. Subsequent requests from end-user devices for content will now come from cache.