formatting

windows/deployment/do/mcc-enterprise.md

@@ -25,23 +25,25 @@ ms.topic: article
 > [!IMPORTANT]
 > Microsoft Connected Cache is currently a private preview feature. During this phase we invite customers to take part in early access for testing purposes. This phase does not include formal support, and should not be used for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many physical servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the [client policy](/mem/intune/configuration/delivery-optimization-settings.md#local-server-caching) using your management tool, such as Intune.
+Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many physical servers or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying a [client policy](/mem/intune/configuration/delivery-optimization-settings.md#local-server-caching) using your management tool, such as Intune.
 
-MCC is a hybrid (mix of on-prem and cloud resources) SaaS solution built as an Azure IoT Edge module. It is a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it is a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.
+MCC is a hybrid (a mix of on-prem and cloud resources) SaaS solution built as an Azure IoT Edge module; it is a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it is a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It’s built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC will be a Linux IoT Edge module running on the Windows Host OS.
 
-Even though your MCC scenario is not related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage MCC on your edge device: 
+Even though your MCC scenario is not related to IoT, Azure IoT Edge is used as a more generic Linux container, deployment, and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs the following important functionsto manage MCC on your edge device: 
 
 1. Installs and updates MCC on your edge device. 
 2. Maintains Azure IoT Edge security standards on your edge device. 
 3. Ensures that MCC is always running. 
 4. Reports MCC health and usage to the cloud for remote monitoring.
 
-To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. See figure 1 below for a summary of the architecture of MCC, built using IoT Edge.
+To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. See [figure 1](#fig1) below for a summary of the architecture of MCC, built using IoT Edge.
 
 For more information about Azure IoT Edge, see [What is Azure IoT Edge](/azure/iot-edge/about-iot-edge).
 
 ## How MCC works
 
+The following steps describe how MCC is provisioned and used.
+
 1. The Azure Management Portal is used to create MCC nodes.
 2. The MCC container is deployed and provisioned to a server using the installer provided in the portal.
 3. Client policy is configured in your management solution to point to the IP address or FQDN of the cache server.
@@ -49,11 +51,11 @@ For more information about Azure IoT Edge, see [What is Azure IoT Edge](/azure/i
 5. An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.
 6. Subsequent requests from end-user devices for content come from the cache.
 
-If the MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
+If an MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
 
 ![eMCC emg01](images/emcc01.png)
 
-Figure 1: Each number in the diagram corresponds to the steps described above.
+<a id="fig1">Figure 1</a>: MCC processes. Each number in the diagram corresponds to the steps described above.
 
 ## Enterprise requirements for MCC
 
@@ -77,10 +79,10 @@ NIC requirements:
  - 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
  - For best performance, NIC and BIOS should support SR-IOV
 
-Networking support:
+  VM networking:
  -  An external virtual switch to support outbound and inbound network communication (created during the installation process)
 
-Hardware and software specifications:
+### Requirements summary:
 
 |   | Branch Office / Small Enterprise | Large Enterprise |
 | -- | --- | --- |