rename images and edits

windows/deployment/do/TOC.yml

@@ -61,7 +61,7 @@
           href: mcc-isp-support.md
         - name: Version history
           href: mcc-version-history.md
-        - name: MCC for ISPs (Private Preview)
+        - name: MCC for ISPs (Early Preview)
           href: mcc-isp.md
 - name: Content endpoints for Delivery Optimization and Microsoft Connected Cache
   href: delivery-optimization-endpoints.md 

windows/deployment/do/mcc-isp.md

@@ -31,15 +31,15 @@ Microsoft Connected Cache is a hybrid application, in that it's a mix of on-prem
 
 ## How MCC works
 
-:::image type="content" source="images/imcc01.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="images/imcc01.png":::
+:::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:
 
 1. The Azure Management Portal is used to create and manage MCC nodes.
 
-2. 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 MCC application.
 
-3. 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 MCC server.
 
     - The publicly accessible IPv4 address of the server is configured on the portal.
 
@@ -50,26 +50,26 @@ The following steps describe how MCC is provisioned and used:
         > [!NOTE]
         > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error.
 
-4. 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 MCC node.
 
-5. Microsoft clients make the range requests for content from the MCC node.
+1. Microsoft clients make the range requests for content from the MCC node.
 
-6. A MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
+1. A MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
 
-7. Subsequent requests from end-user devices for content will be served from cache.
+1. Subsequent requests from end-user devices for content will be served from cache.
 
-8. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
+1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers.
 
 ## ISP requirements for MCC
 
 ### 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 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.
 
 > [!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 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.
 
 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.
 
@@ -89,7 +89,7 @@ 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 MCC instance are supported using a *link aggregated* configuration.
 - 10 Gbps NIC is the minimum speed recommended, but any NIC is supported.
 
 ### Sizing recommendations
@@ -100,7 +100,7 @@ The MCC module is optimized for Ubuntu 20.04 LTS. Install Ubuntu 20.04 LTS on a
 | -- | --- | --- |
 | OS |  Ubuntu 20.04 LTS VM or physical server | Ubuntu 20.04 LTS VM or physical server (preferred) |
 | NIC | 10 Gbps| at least 10 Gbps |
-| Disk | SSD <br>1 drive <br>2 TB each  |SSD <br>2-4 drives <br>at least 2 TB each  |
+| Disk | SSD </br>1 drive </br>2 TB each  |SSD </br>2-4 drives </br>at least 2 TB each  |
 | Memory | 8 GB | 32 GB or greater |
 | Cores | 4 | 8 or more  |
 
@@ -111,7 +111,7 @@ To deploy MCC:
 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)
 3. [Create a Cache Node](#create-a-mcc-node-in-azure)
-4. [Configure Cache Node Routing](#edit-cache-node-information) 
+4. [Configure Cache Node Routing](#edit-cache-node-information)
 5. [Install MCC on a physical server or VM](#install-mcc)
 6. [Verify properly functioning MCC server](#verify-properly-functioning-mcc-server)
 7. [Review common issues if needed](#common-issues)
@@ -135,20 +135,20 @@ Operators who have been given access to the program will be sent a link to the A
 
 1. Choose **Create a resource**.
 
-    :::image type="content" source="images/imcc02.png" alt-text="Select the option to 'Create a resource' in the Azure portal.":::
+    :::image type="content" source="./images/mcc-isp-create-resource.png" alt-text="Screenshot of the option to 'Create a resource' in the Azure portal.":::
 
 1. Type **Microsoft Connected Cache** into the search box and press **Enter** to show the search results.
 
 1. Select **Microsoft Connected Cache**.
 
-    :::image type="content" source="images/imcc03.png" alt-text="Search the Azure Marketplace for 'Microsoft Connected Cache'.":::
+    :::image type="content" source="./images/mcc-isp-search-marketplace.png" alt-text="Screenshot of searching the Azure Marketplace for 'Microsoft Connected Cache'.":::
 
     > [!IMPORTANT]
-    > Don't select _Connected Cache Resources_, which is different from **Microsoft Connected Cache**.
+    > 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.
 
-    :::image type="content" source="images/imcc04.png" alt-text="Select the option to Create the Microsoft Connected Cache service.":::
+    :::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:
 
@@ -163,11 +163,11 @@ Operators who have been given access to the program will be sent a link to the A
 
     - Specify a **Connected Cache Resource Name**.
 
-    :::image type="content" source="images/imcc05.png" alt-text="Enter the required information to create a Connected Cache in Azure.":::
+      :::image type="content" source="./images/mcc-isp-location-west.png" alt-text="Screenshot of entering the required information, including the West US location, to create a Connected Cache in Azure.":::
 
 1. Select **Review + Create**. Once validation is complete, select **Create** to start the resource creation.
 
-    :::image type="content" source="images/imcc06.png" alt-text="'Your deployment is complete' message displaying deployment details.":::
+    :::image type="content" source="./images/mcc-isp-deployment-complete.png" alt-text="'Screenshot of the 'Your deployment is complete' message displaying deployment details.":::
 
 #### Common Resource Creation Errors
 
@@ -175,13 +175,13 @@ Operators who have been given access to the program will be sent a link to the A
 
 If you get the error message "Validation failed" in the Azure portal, it's likely because you selected the **Location** as **US West 2** or another unsupported location. To resolve this error, go to the previous step and choose **(US) West US** for the **Location**.
 
-:::image type="content" source="images/imcc07.png" alt-text="'Validation failed' error message for Connected Cache in an unsupported location.":::
+:::image type="content" source="./images/mcc-isp-unsupported-location.png" alt-text="'Screenshot of the Validation failed' error message for Connected Cache in an unsupported location.":::
 
 ##### Error: Could not create Marketplace item
 
 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 a MCC resource.
+- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create a MCC resource.
 
 - Make sure that you're using the same subscription that you provided to Microsoft and you have privileges to create an Azure resource.
 
@@ -193,11 +193,11 @@ If you get the error message "Could not create marketplace item" in the Azure po
 
 1. Under the **Cache Node Management** section in the left panel, select **Cache Nodes**.
 
-    :::image type="content" source="images/imcc08.png" alt-text="The 'Cache Nodes' option in the Cache Node Management menu section.":::
+    :::image type="content" source="./images/mcc-isp-cache-nodes-option.png" alt-text="Screenshot of the 'Cache Nodes' option in the Cache Node Management menu section.":::
 
 1. On the **Cache Nodes** section, select **Create Cache Node**.
 
-    :::image type="content" source="images/imcc09.png" alt-text="Select the 'Create Cache Node' option.":::
+    :::image type="content" source="./images/mcc-isp-create-cache-node-option.png" alt-text="Screenshot of the selecting the 'Create Cache Node' option.":::
 
 1. This action opens the **Create Cache Node** page. The only required fields are **Cache Node Name** and **Max Allowable Egress (Mbps)**.
 
@@ -207,26 +207,25 @@ If you get the error message "Could not create marketplace item" in the Azure po
     | **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._ |
     | **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. |
     | **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` |
-    | **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. |
+    | **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/imcc10.png" alt-text="Available fields on the Create Cache Node page.":::
+    :::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.":::
 
     > [!TIP]
     > The information icon next to each field provides a description.
     >
-    > :::image type="content" source="images/imcc11.png" alt-text="Create Cache Node page showing the description for the Server IP Address field.":::
+    > :::image type="content" source="./images/mcc-isp-node-server-ip.png" alt-text="Screenshot of the Create Cache Node page showing the description for the Server IP Address field.":::
 
-    > [!NOTE]
-    > After you create the cache node, if you return to this page, it populates the values for the two read-only fields:
-    >
-    > | 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. |
+   After you create the cache node, if you return to this page, it populates the values for the two read-only fields:
+
+     | 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. |
 
 1. Enter the information to create the cache node, and then select **Create**.
 
-    :::image type="content" source="images/imcc12.png" alt-text="Select 'Create' on the Create Cache Node page.":::
+    :::image type="content" source="./images/mcc-isp-create-new-node.png" alt-text="Screenshot of selecting 'Create' on the Create Cache Node page.":::
 
 If there are errors, the page gives you guidance on how to correct the errors. For example:
 
@@ -236,11 +235,11 @@ If there are errors, the page gives you guidance on how to correct the errors. F
 
 See the following example with all information entered:
 
-:::image type="content" source="images/imcc13.png" alt-text="Create Cache Node page 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.
 
-:::image type="content" source="images/imcc14.png" alt-text="Cache node successfully created with Connected Cache installer instructions.":::
+:::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
 
@@ -258,15 +257,15 @@ There are three states for IP address space. MCC configuration supports BGP and
 
   If your IP address space has this status, contact Microsoft for more information.
 
-:::image type="content" source="images/imcc15.png" alt-text="A list of cache node names with example IP address space statuses.":::
+:::image type="content" source="./images/mcc-isp-node-names.png" alt-text="Screenshot of a list of cache node names with example IP address space statuses.":::
 
 ## Edit cache node information
 
-:::image type="content" source="images/imcc16.png" alt-text="Cache Nodes list in the Azure portal.":::
+:::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.
 
-:::image type="content" source="images/imcc17.png" alt-text="Cache Node Configuration page, highlighting editable fields.":::
+:::image type="content" source="./images/mcc-isp-node-configuration" 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.
 
@@ -298,7 +297,7 @@ Before you start, make sure that you have a data drive configured on your server
 
 1. From either **Create Cache Node** or **Cache Node Configuration** pages, select **Download Installer** to download the installer file.
 
-    :::image type="content" source="images/imcc18.png" alt-text="The Create Cache Node page highlighting the Download Installer action.":::
+    :::image type="content" source="./images/mcc-isp-installer-download.png" alt-text="Screenshot of the Create Cache Node page highlighting the Download Installer action.":::
 
     Unzip the **mccinstaller.zip** file, which includes the following installation files and folders:
 
@@ -322,19 +321,19 @@ Before you start, make sure that you have a data drive configured on your server
 
 1. In the Azure portal, in the Connected Cache installer instructions, copy the cache node installer Bash script command. Run the Bash script from the terminal.
 
-    :::image type="content" source="images/imcc19.png" alt-text="Copy the cache node installer Bash script in the Connected Cache installer instructions.":::
+    :::image type="content" source="./images/mcc-isp-copy-install-script.png" alt-text="Screenshot of the Copy option for the cache node installer Bash script in the Connected Cache installer instructions.":::
 
 1. Sign in to the Azure portal with a device code.
 
-    :::image type="content" source="images/imcc20.png" alt-text="Bash script prompt to sign in to the Azure portal with a device code.":::
+    :::image type="content" source="./images/mcc-isp-bash-device-code.png" alt-text="Screenshot of the Bash script prompt to sign in to the Azure portal with a device code." lightbox="./images/mcc-isp-bash-device-code.png":::
 
 1. Specify the number of drives to configure. Use an integer value less than 10.
 
-    :::image type="content" source="images/imcc22.png" alt-text="Bash script prompt to enter the number of cache drives to configure.":::
+    :::image type="content" source="./images/mcc-isp-bash-drive-number.png" alt-text="Screenshot of the Bash script prompt to enter the number of cache drives to configure." lightbox="./images/mcc-isp-bash-drive-number.png":::
 
 1. Specify the location of the cache drives. For example, `/datadrive/`
 
-    :::image type="content" source="images/imcc23.png" alt-text="Bash script prompt to enter the location for cache drive.":::
+    :::image type="content" source="./images/mcc-isp-bash-datadrive.png" alt-text="Screenshot of the Bash script prompt to enter the location for cache drive." lightbox="./images/mcc-isp-bash-datadrive.png':::
 
     > [!IMPORTANT]
     > The script changes the permission and ownership on the cache drive to **everyone** with the command `chmod 777`.
@@ -350,15 +349,15 @@ Before you start, make sure that you have a data drive configured on your server
 
 1. Specify an integer value as the size in GB for each cache drive. The minimum is `100` GB.
 
-    :::image type="content" source="images/imcc24.png" alt-text="Bash script prompt to enter the amount of space to allocate to the cache drive.":::
+    :::image type="content" source="./images/mcc-isp-bash-allocate-space.png" alt-text="Screenshot of the Bash script prompt to enter the amount of space to allocate to the cache drive." lightbox="./images/mcc-isp-bash-allocate-space.png":::
 
 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 MCC deployment*, enter `n`.
 
     - If you already have a 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.
 
-    :::image type="content" source="images/imcc25.png" alt-text="Bash script output with steps for existing IoT Hub.":::
+    :::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":::
 
 1. If you want to configure BGP, enter `y`. If you want to use manual entered prefixes for routing, enter `n` and skip to Step 16. You can always configure BGP at a later time using the Update Script.
 
@@ -394,7 +393,7 @@ Before you start, make sure that you have a data drive configured on your server
 
 1. To start routing using BGP, change the **Prefix Source** from **Manually Entered** to **Use BGP**.
 
-    :::image type="content" source="images/imcc55.PNG" alt-text="Cache node configuration with the Prefix Source set to Use BGP.":::
+    :::image type="content" source="./images/imcc55.PNG" alt-text="Cache node configuration with the Prefix Source set to Use BGP.":::
 
 
 1. If there are no errors, go to the next section to verify the MCC server.
@@ -623,7 +622,7 @@ You can use hardware that will natively run Ubuntu 20.04 LTS, or you can run an
 
 1. Start the **New Virtual Machine Wizard** in Hyper-V.
 
-    :::image type="content" source="images/imcc31.png" alt-text="The Before You Begin page of the Hyper-V New Virtual Machine Wizard.":::
+    :::image type="content" source="images/imcc31.png" alt-text="Screenshot of the Before You Begin page of the Hyper-V New Virtual Machine Wizard.":::
 
 1. Specify a name and choose a location.
 

windows/deployment/do/mcc-version-history.md

@@ -14,12 +14,12 @@ ms.topic: article
 ---
 
 # Version History
-Microsoft periodically releases software updates for your cache nodes to improve performance, caching efficiency, and other bug fixes. These updates will be performed automatically at low-traffic hours, requiring no 
+Microsoft periodically releases software updates for your cache nodes to improve performance, caching efficiency, and other bug fixes. These updates will be performed automatically at low-traffic hours.
 
 ## Current Version
 #### Version 1332
 Released September 15, 2022
 
 Version notes:
-- Fix for caching TLU (Time Limited URLs) – There was a problem and some files that were accessed via TLUs were returning 403s
+- Fix for caching TLU (Time Limited URLs) - There was a problem and some files that were accessed via TLUs were returning 403 errors
 - Core Caching Engine optimizations that will dynamically configure caching settings based on the available system resources.