updated TOC after Meghan's feedback, added device provisioning doc

modified:   windows/deployment/do/TOC.yml
	modified:   windows/deployment/do/mcc-isp-device-provisioning.md

windows/deployment/do/TOC.yml

@@ -1,30 +1,30 @@
-- name: Delivery Optimization for Windows client
+- name: Delivery Optimization for Windows client and Microsoft Connected Cache
   href: index.yml
+- name: What's new
+  href: whats-new-do.md
   items: 
-    - name: Get started
+- name: Delivery Optimization
   items: 
   - name: What is Delivery Optimization
     href: waas-delivery-optimization.md
-        - name: What's new
-          href: whats-new-do.md
   - name: Delivery Optimization Frequently Asked Questions
     href: waas-delivery-optimization-faq.yml    
-          
+  - name: Configure Delivery Optimization for Windows clients
-
-     
-    - name: Configure Delivery Optimization
     items:
-        - name: Configure Windows Clients
+    - name: Windows client Delivery Optimization settings
-          items:
-            - name: Windows Delivery Optimization settings
       href: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
-            - name: Windows Delivery Optimization Frequently Asked Questions
+    - name: Configure Delivery Optimization settings using Microsoft Intune
-              href: ../do/waas-delivery-optimization-faq.yml
-        - name: Configure Microsoft Endpoint Manager
-          items:
-            - name: Delivery Optimization settings in Microsoft Intune
       href: /mem/intune/configuration/delivery-optimization-windows
-     
+  - name: Resources for Delivery Optimization
+    items:
+    - name: Set up Delivery Optimization for Windows
+      href: waas-delivery-optimization-setup.md
+    - name: Delivery Optimization reference
+      href: waas-delivery-optimization-reference.md
+    - name: Delivery Optimization client-service communication
+      href: delivery-optimization-workflow.md       
+    - name: Using a proxy with Delivery Optimization
+      href: delivery-optimization-proxy.md
 - name: Microsoft Connected Cache
   items:
     - name: MCC overview
@@ -75,20 +75,5 @@
           href: mcc-isp-support.md
         - name: MCC for ISPs (Private Preview)
           href: mcc-isp.md
-
-
-
-
-    - name: Resources
-      items:
-        - name: Set up Delivery Optimization for Windows
-          href: waas-delivery-optimization-setup.md
-        - name: Delivery Optimization reference
-          href: waas-delivery-optimization-reference.md
-        - name: Delivery Optimization client-service communication
-          href: delivery-optimization-workflow.md       
-        - name: Using a proxy with Delivery Optimization
-          href: delivery-optimization-proxy.md
 - name: Content endpoints for Delivery Optimization and Microsoft Connected Cache
   href: delivery-optimization-endpoints.md 
-

windows/deployment/do/mcc-isp-device-provisioning.md

@@ -1,16 +1,32 @@
 # Device Provisioning
 
-1. Overview of device provisioning
+Once the user executes the provisioning script, resources are created behind the scenes resulting in the successful cache node installation. 
+The device provisioning script takes the input of different IDs outlined below to create an IoT Central and an IoT Edge device. even though Microsoft Connected Cache scenario is not related to IoT, IoT Central and IoT Edge are installed for management and communication operation purposes. 
 
-2. Components that are installed during provisioning
+### Components installed during provisioning
 
-3. Talk about the unique IDs in the device provisioning script
+#### IoT Central
+
+IoT Central is the main hub that handles all messaging and requests from IoT Edge devices. To learn more about the interaction between IoT Edge and IoT Central, view [IoT Central](https://docs.microsoft.com/en-us/azure/iot-central/core/concepts-iot-edge) documentation.
+
+#### IoT Edge
+
+IoT Edge performs several functions important to manage MCC on your edge device:
+
+1. Installs and updates MCC on your edge device.
+1. Maintains Azure IoT Edge security standards on your edge device.
+1. Ensures that MCC is always running.
+1. Reports MCC health and usage to the cloud for remote monitoring.
+
+### Components of the device provisioning script
+
+There are five IDs that the device provisioning script takes as input in order to successfully provision and install your cache server. The provisioning script will automatically include these keys, with no input necessary from the user.
 
 | ID | Description |
 | -- | --- |
-| Customer ID | |
+| Customer ID | The Azure subscription ID that the cache node is created in. |
-| Cache node ID | |
+| Cache node ID | The unique alphanumeric ID of the cache node being provisioned. |
 | Customer key | |
-| Cache node name | |
+| Cache node name | The name of the cache node. |
-| Tenant ID | |
+| Tenant ID | The unique ID associated with the Azure account. |