Minor edit

w-azure · w-azure · commit eef38eb98461 · 2022-11-30T16:04:44.000-08:00
diff --git a/articles/iot-edge/how-to-authenticate-downstream-device.md b/articles/iot-edge/how-to-authenticate-downstream-device.md
@@ -17,7 +17,7 @@ services: iot-edge
 In a transparent gateway scenario, downstream devices (sometimes called child devices) need identities in IoT Hub like any other device. This article walks through the options for authenticating a downstream device to IoT Hub, and then demonstrates how to declare the gateway connection. 
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 There are three general steps to set up a successful transparent gateway connection. This article covers the second step:
 
diff --git a/articles/iot-edge/how-to-configure-api-proxy-module.md b/articles/iot-edge/how-to-configure-api-proxy-module.md
@@ -25,7 +25,7 @@ For example, to allow downstream IoT Edge devices to pull Docker images requires
 Without the API proxy, each service module would have to bind to a separate port on the host device, requiring a tedious and error-prone configuration change on each child device that connects to the parent IoT Edge device.
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 ## Deploy the proxy module
 
diff --git a/articles/iot-edge/how-to-connect-downstream-device.md b/articles/iot-edge/how-to-connect-downstream-device.md
@@ -20,8 +20,10 @@ This article provides instructions for establishing a trusted connection between
 There are three general steps to set up a successful transparent gateway connection. This article covers the third step:
 
 1. Configure the gateway device as a server so that downstream devices can connect to it securely. Set up the gateway to receive messages from downstream devices and route them to the proper destination. For those steps, see [Configure an IoT Edge device to act as a transparent gateway](how-to-create-transparent-gateway.md).
-2. Create a device identity for the downstream device so that it can authenticate with IoT Hub. Configure the downstream device to send messages through the gateway device. For those steps, see [Authenticate a downstream device to Azure IoT Hub](how-to-authenticate-downstream-device.md).
-3. **Connect the downstream device to the gateway device and start sending messages.**
+
+1. Create a device identity for the downstream device so that it can authenticate with IoT Hub. Configure the downstream device to send messages through the gateway device. For those steps, see [Authenticate a downstream device to Azure IoT Hub](how-to-authenticate-downstream-device.md).
+
+1. **Connect the downstream device to the gateway device and start sending messages.**
 
 This article discusses basic concepts for downstream device connections and guides you in setting up your downstream devices by:
 
@@ -32,7 +34,7 @@ This article discusses basic concepts for downstream device connections and guid
 In this article, the terms *gateway* and *IoT Edge gateway* refer to an IoT Edge device configured as a transparent gateway.
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 ## Prerequisites
 
diff --git a/articles/iot-edge/how-to-connect-downstream-iot-edge-device.md b/articles/iot-edge/how-to-connect-downstream-iot-edge-device.md
@@ -18,7 +18,7 @@ monikerRange: ">=iotedge-2020-11"
 
 This article provides instructions for establishing a trusted connection between an IoT Edge gateway and a downstream IoT Edge device. This setup is also known as "nested edge".
 
-In a gateway scenario, an IoT Edge device can be both a gateway and a downstream (child) device. Multiple IoT Edge gateways can be layered to create a hierarchy of devices. The downstream devices can authenticate and send or receive messages through their gateway (parent) device.
+In a gateway scenario, an IoT Edge device can be both a gateway and a downstream device. Multiple IoT Edge gateways can be layered to create a hierarchy of devices. The downstream devices can authenticate and send or receive messages through their gateway device.
 
 There are two different configurations for IoT Edge devices in a gateway hierarchy, and this article address both. The first is the **top layer** IoT Edge device. When multiple IoT Edge devices are connecting through each other, any device that doesn't have a parent device but connects directly to IoT Hub is considered to be in the top layer. This device is responsible for handling requests from all the devices below it. The other configuration applies to any IoT Edge device in a **lower layer** of the hierarchy. These devices may be a gateway for other downstream IoT and IoT Edge devices, but also need to route any communications through their own parent devices.
 
diff --git a/articles/iot-edge/iot-edge-as-gateway.md b/articles/iot-edge/iot-edge-as-gateway.md
@@ -64,7 +64,7 @@ Beginning with version 1.2 of IoT Edge, transparent gateways can handle connecti
 You declare transparent gateway relationships in IoT Hub by setting the IoT Edge gateway as the *parent* of a downstream device *child* that connects to it.
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 The parent/child relationship is established at three points in the gateway configuration:
 
diff --git a/articles/iot-edge/offline-capabilities.md b/articles/iot-edge/offline-capabilities.md
@@ -60,7 +60,7 @@ A device's *EdgeAgent* updates its reported properties whenever there is a chang
 By default, a parent device can have up to 100 children. You can change this limit by setting the **MaxConnectedClients** environment variable in the edgeHub module. A child device only has one parent.
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 <!-- 1.1 -->
 :::moniker range="iotedge-2018-06"
diff --git a/articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md b/articles/iot-edge/tutorial-nested-iot-edge-for-linux-on-windows.md
@@ -48,7 +48,7 @@ This tutorial uses a two device hierarchy for simplicity, pictured below. One de
 ![Diagram that shows the structure of the tutorial hierarchy, containing two devices: the top layer device and the lower layer device.](./media/tutorial-nested-iot-edge/tutorial-hierarchy-diagram.png)
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 ## Prerequisites
 
diff --git a/articles/iot-edge/tutorial-nested-iot-edge.md b/articles/iot-edge/tutorial-nested-iot-edge.md
@@ -49,7 +49,7 @@ This tutorial uses a two device hierarchy for simplicity, pictured below. One de
 ![Structure of the tutorial hierarchy, containing two devices: the top layer device and the lower layer device](./media/tutorial-nested-iot-edge/tutorial-hierarchy-diagram.png)
 
 >[!NOTE]
->A downstream device is a lockdown device that emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
+>A downstream device emits data directly to the Internet or to gateway devices (IoT Edge-enabled or not). A child device can be a downstream device or a gateway device in a nested topology.
 
 ## Prerequisites
 
