Removed lightbox; some formatting

Author: kgremban

articles/iot-hub-device-update/connected-cache-disconnected-device-update.md

@@ -25,7 +25,7 @@ Microsoft Connected Cache is an intelligent, transparent cache for content publi
 >[!Note]
 >This flow assumes that the IoT Edge gateway has internet connectivity. For the downstream IoT Edge gateway (nested edge) scenario, the content delivery network (CDN) can be considered the MCC hosted on the parent IoT Edge gateway.
 
-:::image type="content" source="media/connected-cache-overview/disconnected-device-update.png" alt-text="Diagram that demonstrates how the Microsoft Connected Cache module enables disconnected device update." lightbox="media/connected-cache-overview/disconnected-device-update.png":::
+:::image type="content" source="media/connected-cache-overview/disconnected-device-update.png" alt-text="Diagram that demonstrates how the Microsoft Connected Cache module enables disconnected device update.":::
 
 1. Microsoft Connected Cache is deployed as an IoT Edge module to the on-premises gateway server.
 2. Device Update for IoT Hub clients are configured to download content from Microsoft Connected Cache by using either the GatewayHostName attribute of the device connection string for IoT leaf devices **or** the parent_hostname set in the config.toml for IoT Edge child devices.

articles/iot-hub-device-update/connected-cache-nested-level.md

@@ -18,7 +18,7 @@ The Microsoft Connected Cache module supports nested, or hierarchical gateways,
 
 The following diagram describes the scenario where one Azure IoT Edge gateway has direct access to CDN resources and is acting as the parent to another Azure IoT Edge gateway. The child IoT Edge gateway is acting as the parent to an IoT leaf device such as a Raspberry Pi. Both the IoT Edge child gateway and the IoT device are internet isolated. This example demonstrates the configuration for two levels of Azure IoT Edge gateways, but there's no limit to the depth of upstream hosts that Microsoft Connected Cache will support.
 
-:::image type="content" source="media/connected-cache-overview/nested-level-proxy.png" alt-text="Diagram showing Microsoft Connected Cache modules deployed to two nested IoT Edge gateways." lightbox="media/connected-cache-overview/nested-level-proxy.png":::
+:::image type="content" source="media/connected-cache-overview/nested-level-proxy.png" alt-text="Diagram showing Microsoft Connected Cache modules deployed to two nested IoT Edge gateways.":::
 
 Refer to the documentation [Connect downstream IoT Edge devices](../iot-edge/how-to-connect-downstream-iot-edge-device.md) for more details on configuring layered deployments of Azure IoT Edge gateways. Additionally note that when deploying Azure IoT Edge, Microsoft Connected Cache, and custom modules, all modules must reside in the same container registry.
 
@@ -128,7 +128,7 @@ The key to configuring Microsoft Connected Cache deployments within an ISA 95 co
 
 3. The OT proxy must add the L4 MCC FQDN/IP address to the allowlist.
 
-To validate that Microsoft Connected Cache is functioning properly, execute the following command in the terminal of the IoT Edge device hosting the module, or any device on the network. Replace \<Azure IoT Edge Gateway IP\> with the IP address or hostname of your IoT Edge gateway. (see environment variable details for information on visibility of this report).
+To validate that Microsoft Connected Cache is functioning properly, execute the following command in the terminal of the IoT Edge device hosting the module, or any device on the network. Replace \<Azure IoT Edge Gateway IP\> with the IP address or hostname of your IoT Edge gateway. For information on the visibility of this report, see [Microsoft Connected Cache summary report](./connected-cache-disconnected-device-update.md#microsoft-connected-cache-summary-report).
 
 ```bash
 wget http://<L3 IoT Edge Gateway IP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com

articles/iot-hub-device-update/connected-cache-single-level.md

@@ -20,9 +20,11 @@ If you have multiple IoT Edge gateways chained together, refer to the instructio
 
 ## Deploy to a gateway with no proxy
 
-The following diagram describes the scenario where an Azure IoT Edge gateway has direct access to CDN resources, and has the Microsoft Connected Cache module deployed on it. Behind the gateway, there's an IoT leaf device such as a Raspberry PI that is an internet isolated child device of the IoT Edge gateway.
+The following diagram describes the scenario where an Azure IoT Edge gateway has direct access to content deliver network (CDN) resources, and has the Microsoft Connected Cache module deployed on it. Behind the gateway, there's an IoT leaf device such as a Raspberry PI that is an internet isolated child device of the IoT Edge gateway.
 
-:::image type="content" source="media/connected-cache-overview/disconnected-device-update.png" alt-text="Diagram that shows the Microsoft Connected Cache module on a gateway." lightbox="media/connected-cache-overview/disconnected-device-update.png":::
+:::image type="content" source="media/connected-cache-overview/disconnected-device-update.png" alt-text="Diagram that shows the Microsoft Connected Cache module on a gateway.":::
+
+The following steps are an example of configuring the MCC environment variables to connect directly to the CDN with no proxy:
 
 1. Add the Microsoft Connected Cache module to your Azure IoT Edge gateway device deployment in Azure IoT Hub (see [Support for Disconnected Devices](connected-cache-disconnected-device-update.md) for details on how to get the module).
 2. Add the environment variables for the deployment. The following table is an example of the environment variables:
@@ -58,17 +60,19 @@ The following diagram describes the scenario where an Azure IoT Edge gateway has
    }
    ```
 
-For a validation of properly functioning Microsoft Connected Cache, execute the following command in the terminal of the IoT Edge device hosting the module or any device on the network. Replace \<Azure IoT Edge Gateway IP\> with the IP address or hostname of your IoT Edge gateway. (see environment variable details for information on visibility of this report).
+For a validation of properly functioning Microsoft Connected Cache, execute the following command in the terminal of the IoT Edge device hosting the module or any device on the network. Replace \<Azure IoT Edge Gateway IP\> with the IP address or hostname of your IoT Edge gateway. For information on the visibility of this report, see [Microsoft Connected Cache summary report](./connected-cache-disconnected-device-update.md#microsoft-connected-cache-summary-report).
 
 ```bash
-    wget http://<IoT Edge Gateway IP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
+wget http://<IoT Edge Gateway IP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
 ```
 
 ## Deploy to a gateway with outbound unauthenticated proxy
 
-In this scenario there's an Azure IoT Edge Gateway that has access to CDN resources through an outbound unauthenticated proxy. Microsoft Connected Cache is being configured to cache content from a custom repository and the summary report has been made visible to anyone on the network. This section provides an example of the MCC environment variables to support an outbound unauthenticated proxy.
+In this scenario, an Azure IoT Edge Gateway has access to content delivery network (CDN) resources through an outbound unauthenticated proxy. Microsoft Connected Cache is configured to cache content from a custom repository and the summary report is visible to anyone on the network.
+
+:::image type="content" source="media/connected-cache-overview/single-level-proxy.png" alt-text="Diagram that shows the Microsoft Connected Cache module on a gateway behind a proxy.":::
 
-:::image type="content" source="media/connected-cache-overview/single-level-proxy.png" alt-text="Diagram that shows the Microsoft Connected Cache module on a gateway behind a proxy." lightbox="media/connected-cache-overview/single-level-proxy.png":::
+The following steps are an example of configuring the MCC environment variables to support an outbound unauthenticated proxy:
 
 1. Add the Microsoft Connected Cache module to your Azure IoT Edge gateway device deployment in Azure IoT Hub.
 2. Add the environment variables for the deployment. Below is an example of the environment variables.