Merge pull request #222944 from w-azure/winona-linkfix

Fixed some links

Author: prmerger-automator[bot]

articles/iot-edge/includes/iot-edge-generate-device-identity-certs.md

@@ -15,7 +15,7 @@ When you provision an IoT Edge device with X.509 certificates, you use what is c
 
 For X.509 certificate authentication, each device's authentication information is provided in the form of *thumbprints* taken from your device identity certificates. These thumbprints are given to IoT Hub at the time of device registration so that the service can recognize the device when it connects.
 
-For more information about how the CA certificates are used in IoT Edge devices, see [Understand how Azure IoT Edge uses certificates](/articles/iot-edge/iot-edge-certs.md).
+For more information about how the CA certificates are used in IoT Edge devices, see [Understand how Azure IoT Edge uses certificates](../iot-edge-certs.md).
 
 You need the following files for manual provisioning with X.509:
 
@@ -27,7 +27,7 @@ You need the following files for manual provisioning with X.509:
 
   Thumbprint values are 40-hex characters for SHA-1 hashes or 64-hex characters for SHA-256 hashes. Both thumbprints are provided to IoT Hub at the time of device registration.
 
-If you don't have certificates available, you can [Create demo certificates to test IoT Edge device features](/articles/iot-edge/how-to-create-test-certificates.md). Follow the instructions in that article to set up certificate creation scripts, create a root CA certificate, and then create two IoT Edge device identity certificates.
+If you don't have certificates available, you can [Create demo certificates to test IoT Edge device features](../how-to-create-test-certificates.md). Follow the instructions in that article to set up certificate creation scripts, create a root CA certificate, and then create two IoT Edge device identity certificates.
 
 One way to retrieve the thumbprint from a certificate is with the following openssl command:
 

articles/iot-edge/includes/iot-edge-install-linux.md

@@ -98,7 +98,7 @@ Install the Moby engine and CLI.
    ```
 ---
 
-Once the Moby engine is successfully installed, configure it to use [`local` logging driver](https://docs.docker.com/config/containers/logging/local/) as the logging mechanism. To learn more about logging configuration, see [Production Deployment Checklist](/articles/iot-edge/production-checklist.md#set-up-default-logging-driver).
+Once the Moby engine is successfully installed, configure it to use [`local` logging driver](https://docs.docker.com/config/containers/logging/local/) as the logging mechanism. To learn more about logging configuration, see [Production Deployment Checklist](../production-checklist.md#set-up-default-logging-driver).
 
 * Create or open the Docker daemon's config file at `/etc/docker/daemon.json`.
 * Set the default logging driver to the `local` logging driver as shown in the example below.   

articles/iot-edge/includes/iot-edge-prerequisites-device-requirements-linux.md

@@ -13,4 +13,4 @@ An X64, ARM32, or ARM64 Linux device.
 
 Microsoft publishes installation packages for a variety of operating systems.
 
-For the latest information about which operating systems are currently supported for production scenarios, see [Azure IoT Edge supported systems](/articles/iot-edge/support.md#operating-systems).
+For the latest information about which operating systems are currently supported for production scenarios, see [Azure IoT Edge supported systems](../support.md#operating-systems).

articles/iot-edge/includes/iot-edge-prerequisites-linux-on-windows.md

@@ -22,17 +22,17 @@ A Windows device with the following minimum requirements:
 
 * Virtualization support
   * On Windows 10, enable Hyper-V. For more information, see [Install Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v).
-  * On Windows Server, install the Hyper-V role and create a default network switch. For more information, see [Nested virtualization for Azure IoT Edge for Linux on Windows](/articles/iot-edge/nested-virtualization.md).
-  * On a virtual machine, configure nested virtualization. For more information, see [nested virtualization](/articles/iot-edge/nested-virtualization.md).
+  * On Windows Server, install the Hyper-V role and create a default network switch. For more information, see [Nested virtualization for Azure IoT Edge for Linux on Windows](../nested-virtualization.md).
+  * On a virtual machine, configure nested virtualization. For more information, see [nested virtualization](../nested-virtualization.md).
 
 * Networking support
-  * Windows Server does not come with a default switch. Before you can deploy EFLOW to a Windows Server device, you need to create a virtual switch.  For more information, see [Create virtual switch for Linux on Windows](/articles/iot-edge/how-to-create-virtual-switch.md).
+  * Windows Server does not come with a default switch. Before you can deploy EFLOW to a Windows Server device, you need to create a virtual switch.  For more information, see [Create virtual switch for Linux on Windows](../how-to-create-virtual-switch.md).
   * Windows Desktop versions come with a default switch that can be used for EFLOW installation. If needed, you can create your own custom virtual switch.
 
 > [!TIP]
 > If you want to use **GPU-accelerated Linux modules** in your Azure IoT Edge for Linux on Windows deployment, there are several configuration options to consider.
 >
-> You will need to install the correct drivers depending on your GPU architecture, and you may need access to a Windows Insider Program build. To determine your configuration needs and satisfy these prerequisites, see [GPU acceleration for Azure IoT Edge for Linux on Windows](/articles/iot-edge/gpu-acceleration.md).
+> You will need to install the correct drivers depending on your GPU architecture, and you may need access to a Windows Insider Program build. To determine your configuration needs and satisfy these prerequisites, see [GPU acceleration for Azure IoT Edge for Linux on Windows](../gpu-acceleration.md).
 >
 > Make sure you take the time to satisfy the prerequisites for GPU acceleration now. You will need to restart the installation process if you decide you want GPU acceleration during installation.
 
@@ -59,7 +59,7 @@ If you want to use PowerShell, use the following steps to prepare your target de
    Set-ExecutionPolicy -ExecutionPolicy AllSigned -Force
    ```
 
-For more information on the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](/articles/iot-edge/reference-iot-edge-for-linux-on-windows-functions.md).
+For more information on the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](../reference-iot-edge-for-linux-on-windows-functions.md).
 
 # [Windows Admin Center](#tab/windowsadmincenter)
 
@@ -73,7 +73,7 @@ If you want to use Windows Admin Center, use the following steps to download and
 
    1. Install the Azure IoT Edge extension. Select the gear icon in the top right of the Windows Admin Center dashboard.
 
-      ![Select the gear icon in the top right of the dashboard to access the settings, PNG.](/articles/iot-edge/media/how-to-provision-devices-at-scale-linux-on-windows-x509/select-gear-icon.png)
+      ![Select the gear icon in the top right of the dashboard to access the settings, PNG.](../media/how-to-provision-devices-at-scale-linux-on-windows-x509/select-gear-icon.png)
 
    1. On the **Settings** menu, under **Gateway**, select **Extensions**.
 
@@ -102,7 +102,7 @@ Prepare your target device for the installation of Azure IoT Edge for Linux on W
    Set-ExecutionPolicy -ExecutionPolicy AllSigned -Force
    ```
 
-For more information on the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](/articles/iot-edge/reference-iot-edge-for-linux-on-windows-functions.md).
+For more information on the Azure IoT Edge for Linux on Windows PowerShell module, see the [PowerShell functions reference](../reference-iot-edge-for-linux-on-windows-functions.md).
 
 :::moniker-end
 <!-- end iotedge-2020-11 -->

articles/iot-edge/includes/iot-edge-prerequisites-register-device.md

@@ -13,18 +13,18 @@ You can use the **Azure portal**, **Visual Studio Code**, or **Azure CLI** for t
 
 # [Portal](#tab/azure-portal)
 
-A free or standard [IoT hub](/articles/iot-hub/iot-hub-create-through-portal.md) in your Azure subscription.
+A free or standard [IoT hub](../../iot-hub/iot-hub-create-through-portal.md) in your Azure subscription.
 
 # [Visual Studio Code](#tab/visual-studio-code)
 
-* A free or standard [IoT hub](/articles/iot-hub/iot-hub-create-through-portal.md) in your Azure subscription
+* A free or standard [IoT hub](../../iot-hub/iot-hub-create-through-portal.md) in your Azure subscription
 * [Visual Studio Code](https://code.visualstudio.com/)
 * [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) for Visual Studio Code
 * [Azure IoT Edge](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge) for Visual Studio Code
 
 # [Azure CLI](#tab/azure-cli)
 
-* A free or standard [IoT hub](/articles/iot-hub/iot-hub-create-using-cli.md) in your Azure subscription
+* A free or standard [IoT hub](../../iot-hub/iot-hub-create-using-cli.md) in your Azure subscription
 * [Azure CLI](/cli/azure/install-azure-cli) in your environment
 
   At a minimum, your Azure CLI version must be 2.0.70 or newer. Use `az --version` to validate. This version supports az extension commands and introduces the Knack command framework.