mcc-branding

This commit is contained in:
Meghan Stewart
2024-10-24 14:28:14 -07:00
parent daf5d8ff53
commit 5eb58e383d
2 changed files with 2 additions and 2 deletions

View File

@ -26,7 +26,7 @@ To deploy Connected Cache to your server:
1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id)
1. [Create the Connected Cache Resource in Azure](#create-the-connected-cache-resource-in-azure)
1. [Create a Connected Cache Node](#create-an-connected-cache-node-in-azure)
1. [Create a Connected Cache Node](#create-a-connected-cache-node-in-azure)
1. [Edit Cache Node Information](#edit-cache-node-information)
1. [Install Connected Cache on a physical server or VM](#install-connected-cache-on-windows)
1. [Verify Connected Cache functionality](#verify-connected-cache-server-functionality)

View File

@ -70,7 +70,7 @@ The following steps describe how Connected Cache is provisioned and used:
1. Microsoft clients make the range requests for content from the Connected Cache node.
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. 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.