fix errors

.openpublishing.redirection.json

@@ -19927,12 +19927,7 @@
      },
      {
       "source_path": "windows/deployment/do/mcc-enterprise.md",
-      "redirect_url": "/windows/deployment/do/mcc-enterprise-overview",
-      "redirect_document_id": false
-    },
-    {
-      "source_path": "windows/deployment/do/mcc-enterprise-overview.md",
-      "redirect_url": "/windows/deployment/do/mcc-enterprise-prerequisites",
+      "redirect_url": "/windows/deployment/do/waas-microsoft-connected-cache",
       "redirect_document_id": false
     },
     {

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

@@ -106,15 +106,15 @@ There are five IDs that the device provisioning script takes as input in order t
 
 1. After completing cache node provisioning, navigate to the **Server provisioning** tab. Select **Download provisioning package** to download the installation package to your server.  
 
-2. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script: 
+1. Open a terminal window in the directory where you would like to deploy your cache node and run the following command to change the access permission to the Bash script: 
 
     ```bash
     sudo chmod +x provisionmcc.sh
     ```
 
-3. Copy and paste the script command line shown in the Azure portal.
+1. Copy and paste the script command line shown in the Azure portal.
 
-5. Run the script in your server terminal for your cache node by . The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
+1. Run the script in your server terminal for your cache node by . The script may take a few minutes to run. If there were no errors, you have set up your cache node successfully. To verify the server is set up correctly, follow the [verification steps](mcc-isp-verify-cache-node.md).
 
     > [!NOTE]
     > The same script can be used to provision multiple cache nodes, but the command line is unique per cache node. Additionally, if you need to reprovision your server or provision a new server or VM for the cache node, you must copy the command line from the Azure portal again as the "registrationkey" value is unique for each successful execution of the provisioning script.

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

@@ -73,7 +73,7 @@ For more information about how to build your custom charts and graphs, see [Azur
 
 To view the metrics associated with your cache nodes, navigate to the **Overview** > **Monitoring** tab within the Azure portal.
 
-:::image type="content" source="./images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab".:::
+:::image type="content" source="./images/mcc-isp-metrics.png" alt-text="Screenshot of the Azure portal displaying the metrics view in the Overview tab.":::
 
 You can choose to monitor the health and performance of all cache nodes or one at a time by using the dropdown menu. The **Egress bits per second** graph shows your inbound and outbound traffic of your cache nodes over time. You can change the time range (1 hour, 12 hours, 1 day, 7 days, 14 days, and 30 days) by selecting the time range of choice on the top bar.
 

windows/deployment/do/mcc-isp.md

@@ -110,7 +110,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)
+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)
 6. [Verify properly functioning MCC server](#verify-properly-functioning-mcc-server)