Fixed ol/ul formatting

Author: kgremban

articles/iot-edge/how-to-authenticate-downstream-device.md

@@ -148,8 +148,8 @@ The easiest way to test this scenario is to use the same machine that you used t
 
 1. Follow the instructions in the [Register X.509 CA certificates to your IoT hub](../iot-hub/iot-hub-security-x509-get-started.md#register-x509-ca-certificates-to-your-iot-hub) section of *Set up X.509 security in your Azure IoT hub*. In that section, you perform the following steps: 
 
-   * Upload a root CA certificate. If you're using the certificates that you created in the transparent gateway article, upload **\<WRKDIR>/certs/azure-iot-test-only.root.ca.cert.pem** as the root certificate file. 
-   * Verify that you own that root CA certificate. You can verify possession with the cert tools in \<WRKDIR>. 
+   1. Upload a root CA certificate. If you're using the certificates that you created in the transparent gateway article, upload **\<WRKDIR>/certs/azure-iot-test-only.root.ca.cert.pem** as the root certificate file. 
+   2. Verify that you own that root CA certificate. You can verify possession with the cert tools in \<WRKDIR>. 
 
       ```powershell
       New-CACertsVerificationCert "<verification code from Azure portal>"
@@ -161,8 +161,8 @@ The easiest way to test this scenario is to use the same machine that you used t
 
 2. Follow the instructions in the [Create an X.509 device for your IoT hub](../iot-hub/iot-hub-security-x509-get-started.md#create-an-x509-device-for-your-iot-hub) section of *Set up X.509 security in your Azure IoT hub*. In that section, you perform the following steps: 
 
-   * Add a new device. Provide a lowercase name for **device ID**, and choose the authentication type **X.509 CA Signed**. 
-   * For downstream devices, you must **Set a parent device** and choose the IoT Edge gateway device that will provide the connection to IoT Hub. 
+   1. Add a new device. Provide a lowercase name for **device ID**, and choose the authentication type **X.509 CA Signed**. 
+   2. Set a parent device. For downstream devices, select **Set a parent device** and choose the IoT Edge gateway device that will provide the connection to IoT Hub. 
 
 3. Create a certificate chain for your downstream device. Use the same root CA certificate that you uploaded to IoT Hub to make this chain. Use the same lowercase device ID that you gave to your device identity in the portal.
 

articles/iot-edge/how-to-connect-downstream-device.md

@@ -35,11 +35,11 @@ A downstream device can be any application or platform that has an identity crea
 
 To connect a downstream device to an IoT Edge gateway, you need two things:
 
-1. A device or application that's configured with an IoT Hub device connection string appended with information to connect it to the gateway. 
+* A device or application that's configured with an IoT Hub device connection string appended with information to connect it to the gateway. 
 
     This step is explained in [Authenticate a downstream device to Azure IoT Hub](how-to-authenticate-downstream-device.md).
 
-2. The device or application has to trust the gateway's **root CA** certificate to validate the TLS connections to the gateway device. 
+* The device or application has to trust the gateway's **root CA** certificate to validate the TLS connections to the gateway device. 
 
     This step is explained in detail in the rest of this article. This step can be performed one of two ways: by installing the CA certificate in the operating system's certificate store, or (for certain languages) by referencing the certificate within applications using the Azure IoT SDKs.
 
@@ -97,9 +97,9 @@ This section describes how the Azure IoT SDKs connect to an IoT Edge device usin
 
 Have two things ready before using the application-level samples:
 
-1. Your downstream device's IoT Hub connection string modified to point to the gateway device, and any certificates required to authenticate your downstream device to IoT Hub. For more information, see [Authenticate a downstream device to Azure IoT Hub](how-to-authenticate-downstream-device.md).
+* Your downstream device's IoT Hub connection string modified to point to the gateway device, and any certificates required to authenticate your downstream device to IoT Hub. For more information, see [Authenticate a downstream device to Azure IoT Hub](how-to-authenticate-downstream-device.md).
 
-2. The full path to the root CA certificate that you copied and saved somewhere on your downstream device.
+* The full path to the root CA certificate that you copied and saved somewhere on your downstream device.
 
     For example, `<path>/azure-iot-test-only.root.ca.cert.pem`.