fix errors

windows/deployment/do/TOC.yml

@@ -28,7 +28,7 @@
     - name: Testing Delivery Optimization
       href: delivery-optimization-test.md
     - name: Delivery Optimization Troubleshooter
-      href: http://aka.ms/do-fix
+      href: https://aka.ms/do-fix
 - name: Microsoft Connected Cache
   items:
     - name: What is Microsoft Connected Cache?

windows/deployment/do/mcc-enterprise-appendix.md

@@ -41,7 +41,7 @@ Most customers choose to install their cache node on a Windows Server with a nes
 Microsoft Connected Cache for Enterprise and Education can be successfully installed on VMware. To do so, there are a couple of additional configurations to be made. Ensure the VM is turned off before making the following configuration changes:
 
 1. Ensure that you're using ESX. In the VM settings, turn on the option **Expose hardware assisted virtualization to the guest OS**.
-1. Using the Hyper-V Manager, create an external switch. For the external switch to have internet connection, ensure **"Allow promiscuous mode"** and **"Forged transmits"** are switched to **Yes**.
+2. Using the Hyper-V Manager, create an external switch. For the external switch to have internet connection, ensure **"Allow promiscuous mode"** and **"Forged transmits"** are switched to **Yes**.
 
 ### Installing on Hyper-V
 
@@ -57,16 +57,16 @@ To run this script:
 
     mccinstaller > Eflow > Diagnostics
 
-1. Run the following commands:
+2. Run the following commands:
 
    ```powershell
    Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
    .\collectMccDiagnostics.ps1
    ```
 
-1. The script stores all the debug files into a folder and then creates a tar file. After the script is finished running, it will output the path of the tar file, which you can share with us. The location should be **\<currentpath\>**\mccdiagnostics\support_bundle_\$timestamp.tar.gz
+3. The script stores all the debug files into a folder and then creates a tar file. After the script is finished running, it will output the path of the tar file, which you can share with us. The location should be **\<currentpath\>**\mccdiagnostics\support_bundle_\$timestamp.tar.gz
 
-1. [Email the MCC team](mailto:mccforenterprise@microsoft.com?subject=Debugging%20Help%20Needed%20for%20MCC%20for%20Enterprise) and attach this file asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during out debugging process.
+4. [Email the MCC team](mailto:mccforenterprise@microsoft.com?subject=Debugging%20Help%20Needed%20for%20MCC%20for%20Enterprise) and attach this file asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during out debugging process.
 
 ## IoT Edge runtime
 
@@ -99,15 +99,15 @@ You can either set your MCC IP address or FQDN using:
 
     From an elevated command prompt:
 
-```powershell
-    reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
+    ```powershell
+        reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
     ```
 
-1. MDM path (version 1809 and later):
+2. MDM path (version 1809 and later):
 
     `.Vendor/MSFT/Policy/Config/DeliveryOptimization/DOCacheHost`
 
-1. In Windows (release version 1809 and later), you can apply the policy via Group Policy Editor. The policy to apply is **DOCacheHost**. To configure the clients to pull content from the MCC using Group Policy, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Delivery Optimization**. Set the **Cache Server Hostname** to the IP address of your MCC, such as `10.137.187.38`.
+3. In Windows (release version 1809 and later), you can apply the policy via Group Policy Editor. The policy to apply is **DOCacheHost**. To configure the clients to pull content from the MCC using Group Policy, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Delivery Optimization**. Set the **Cache Server Hostname** to the IP address of your MCC, such as `10.137.187.38`.
 
    :::image type="content" source="./images/ent-mcc-group-policy-hostname.png" alt-text="Screenshot of the Group Policy editor showing the Cache Server Hostname Group Policy setting." lightbox="./images/ent-mcc-group-policy-hostname.png":::
 
@@ -119,7 +119,7 @@ To verify that the Delivery Optimization client can download content using MCC,
 
    :::image type="content" source="./images/ent-mcc-store-example-download.png" alt-text="Screenshot of the Microsoft Store with the game, Angry Birds 2, selected.":::
 
-1. Verify downloads came from MCC by one of two methods:
+2. Verify downloads came from MCC by one of two methods:
 
     - Using the PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see *BytesFromCacheServer*.
 

windows/deployment/do/whats-new-do.md

@@ -35,7 +35,7 @@ There are two different versions:
 
 ### General
 
-[Check out](http://aka.ms/do-fix) the new Delivery Optimization Troubleshooter. This tool provides a device health check to verify the device is set up properly to use Delivery Optimization. To scope the output more specifically, use one of the two switches:
+[Check out](https://aka.ms/do-fix) the new Delivery Optimization Troubleshooter. This tool provides a device health check to verify the device is set up properly to use Delivery Optimization. To scope the output more specifically, use one of the two switches:
 
 - -p2p: Provides output specific to P2P settings, efficiency, and errors.
 - -mcc: Provides output specific to MCC settings and verifies the client can access the cache server.