Fixed things based on review

Author: w-azure

articles/iot-edge/how-to-provision-single-device-linux-symmetric.md

@@ -15,7 +15,7 @@ ms.author: patricka
 
 This article provides end-to-end instructions for registering and provisioning a Linux IoT Edge device, which includes installing IoT Edge.
 
-Each device that connects to an [IoT hub](/azure/iot-hub/) has a device ID that's used to track [cloud-to-device](/azure/iot-hub/iot-hub-devguide-c2d-guidance) or [device-to-cloud](/azure/iot-hub/iot-hub-devguide-d2c-guidance) communications. You configure a device with its connection information, which includes: 
+Each device that connects to an [IoT hub](../iot-hub/index.yml) has a device ID that's used to track [cloud-to-device](..iot-hub/iot-hub-devguide-c2d-guidance.md) or [device-to-cloud](../iot-hub/iot-hub-devguide-d2c-guidance.md) communications. You configure a device with its connection information, which includes: 
 
 * IoT hub hostname
 * Device ID
@@ -130,10 +130,26 @@ After entering the provisioning information in the configuration file, restart t
    ```bash
    sudo nano /etc/aziot/config.toml
    ```
-
+Verify successful configuration
 <!-- end iotedge-2020-11 -->
 ::: moniker-end
 
+## Deploy modules
+
+To deploy your IoT Edge modules, go to your IoT hub in the Azure portal, then:
+
+1. Select **Devices** from the IoT Hub menu.
+
+1. Select your device to open its page.
+
+1. Select the **Set Modules** tab.
+
+1. Since we want to deploy the IoT Edge default modules (edgeAgent and edgeHub), we don't need to add any modules to this pane, so select **Review + create** at the bottom.
+
+1. You see the JSON confirmation of your modules. Select **Create** to deploy the modules.<br>
+   
+For more information, see [Deploy a module](/quickstart-linux#deploy-a-module.md).
+
 ## Verify successful configuration
 
 Verify that the runtime was successfully installed and configured on your IoT Edge device.
@@ -143,25 +159,25 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
 
 1. Check to see that the IoT Edge system service is running.
 
-<!-- 1.1 -->
-::: moniker range="iotedge-2018-06"
+   <!-- 1.1 -->
+   ::: moniker range="iotedge-2018-06"
 
    ```bash
    sudo systemctl status iotedge
    ```
 
-::: moniker-end
+   ::: moniker-end
 
-<!-- iotedge-2020-11 -->
-::: moniker range=">=iotedge-2020-11"
+   <!-- iotedge-2020-11 -->
+   ::: moniker range=">=iotedge-2020-11"
 
    ```bash
    sudo iotedge system status
    ```
 
-   A successful status response is `Ok`.
+   A successful status response shows the `aziot` services as running or ready.
 
-::: moniker-end
+   ::: moniker-end
 
 1. To troubleshoot the service, retrieve the service logs.
 
@@ -198,20 +214,14 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
 
    >[!NOTE]
    >On a newly provisioned device, you may see an error related to IoT Edge Hub:
+   >
    >**× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error**
    >**Could not check current state of edgeHub container**
    >
-   >This error is expected on a newly provisioned device because the IoT Edge Hub module is not yet running. You need to deploy your device and then deploy the IoT Edge modules.
+   >This error is expected on a newly provisioned device because the IoT Edge Hub module is not yet running. Be sure your IoT Edge modules were deployed in the previous steps. Deployment resolves this error.
    >
-   >Use the `az deployment group create` command to deploy your device. For more information, see [Deploy the IoT Edge device](quickstart-linux.md#deploy-the-iot-edge-device).
+   >Alternatively, you may see a status code as `417 -- The device's deployment configuration is not set`. Once your modules are deployed, this status will change.
    >
-   >To deploy your IoT Edge modules, go to your IoT hub in the Azure portal, then:
-   >1. Select **Devices** from the IoT Hub menu.
-   >1. Select your device to open its page.
-   >1. Select the **Set Modules** tab.
-   >1. Since we want to deploy the IoT Edge default modules (edgeAgent and edgeHub), we don't need to add any modules to this pane, so select **Review + create** at the bottom.
-   >1. You see the JSON confirmation of your modules. Select **Create** to deploy the modules.
-   >For more information, see [Deploy a module](/quickstart-linux#deploy-a-module.md).
 
 1. When the service starts for the first time, you should only see the **edgeAgent** module running. The edgeAgent module runs by default and helps to install and start any additional modules that you deploy to your device.
 
@@ -225,17 +235,14 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
    sudo iotedge list
    ```
 
-   >[!NOTE]
-   >When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
-
 ## Offline or specific version installation (optional)
 
 The steps in this section are for scenarios not covered by the standard installation steps. This may include:
 
 * Installing IoT Edge while offline
 * Installing a release candidate version
 
-Use the steps in this section if you want to install a specific version of the Azure IoT Edge runtime that isn't available through your package manager. The Microsoft package list only contains a limited set of recent versions and their sub-versions, so these steps are for anyone who wants to install an older version or a release candidate version.
+Use the steps in this section if you want to install a [specific version of the Azure IoT Edge runtime](version-history.md) that isn't available through your package manager. The Microsoft package list only contains a limited set of recent versions and their sub-versions, so these steps are for anyone who wants to install an older version or a release candidate version.
 
 Using curl commands, you can target the component files directly from the IoT Edge GitHub repository.
 

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

@@ -64,7 +64,7 @@ Installing can be done with a few commands. Open a terminal and run the followin
 
 ---
 
-For more information about operating system versions, see [Azure IoT Edge supported platforms](/support?#linux-containers).
+For more information about operating system versions, see [Azure IoT Edge supported platforms](../support.md?#linux-containers).
 
 > [!NOTE]
 > Azure IoT Edge software packages are subject to the license terms located in each package (`usr/share/doc/{package-name}` or the `LICENSE` directory). Read the license terms prior to using a package. Your installation and use of a package constitutes your acceptance of these terms. If you don't agree with the license terms, don't use that package.
@@ -137,7 +137,7 @@ The following steps show you how to configure your container to use [`local` log
 
 The IoT Edge security daemon provides and maintains security standards on the IoT Edge device. The daemon starts on every boot and bootstraps the device by starting the rest of the IoT Edge runtime.
 
-The steps in this section represent the typical process to install the latest version on a device that has internet connection. If you need to install a specific version, like a pre-release version, or need to install while offline, follow the [Offline or specific version installation](/how-to-provision-single-device-linux-symmetric#offline-or-specific-version-installation-optional) steps later in this article.
+The steps in this section represent the typical process to install the latest version on a device that has internet connection. If you need to install a specific version, like a pre-release version, or need to install while offline, follow the **Offline or specific version installation** steps later in this article.
 
 Install IoT Edge version 1.1.* along with the **libiothsm-std** package:
 
@@ -175,10 +175,10 @@ The IoT Edge service provides and maintains security standards on the IoT Edge d
 > [!NOTE]
 > Beginning with version 1.2, the [IoT identity service](https://azure.github.io/iot-identity-service/) handles identity provisioning and management for IoT Edge and for other device components that need to communicate with IoT Hub.
 
-The steps in this section represent the typical process to install the latest IoT Edge version on a device that has internet connection. If you need to install a specific version, like a pre-release version, or need to install while offline, follow the [Offline or specific version installation](/how-to-provision-single-device-linux-symmetric#offline-or-specific-version-installation-optional) steps later in this article.
+The steps in this section represent the typical process to install the latest IoT Edge version on a device that has internet connection. If you need to install a specific version, like a pre-release version, or need to install while offline, follow the **Offline or specific version installation** steps later in this article.
 
 > [!TIP]
-> If you already have an IoT Edge device running an older version and want to upgrade to the latest release, use the steps in [Update the IoT Edge security daemon and runtime](/articles/iot-edge/how-to-update-iot-edge.md). Later versions are sufficiently different from previous versions of IoT Edge that specific steps are necessary to upgrade.
+> If you already have an IoT Edge device running an older version and want to upgrade to the latest release, use the steps in [Update the IoT Edge security daemon and runtime](../how-to-update-iot-edge.md). Later versions are sufficiently different from previous versions of IoT Edge that specific steps are necessary to upgrade.
 
 # [Ubuntu](#tab/ubuntu)
 
@@ -204,7 +204,7 @@ The defender-iot-micro-agent-edge package includes the Microsoft Defender for Io
 
 # [Red Hat Enterprise Linux](#tab/rhel)
 
-  Install the latest version of IoT Edge and the IoT identity service package (if you're not already [up-to-date](/version-history.md)):
+  Install the latest version of IoT Edge and the IoT identity service package (if you're not already [up-to-date](../version-history.md)):
 
    ```bash
    sudo yum install aziot-edge

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

@@ -89,7 +89,7 @@ Now that you have a device registered in IoT Hub, you can retrieve provisioning
 
 ## View registered devices and retrieve provisioning information
 
-Devices that use symmetric key authentication need their connection strings to complete installation and provisioning of the IoT Edge runtime. The connection string was generated for your IoT Edge device when you created it. For Visual Studio Code and Azure CLI, the connection string is in the JSON printout. If you used the Azure portal to create your device, you can find the connection string from the device itself. When you select your device in your IoT hub, it's listed as `Primary connection string` on the device page.
+Devices that use symmetric key authentication need their connection strings to complete installation and provisioning of the IoT Edge runtime. The connection string gets generated for your IoT Edge device when you create the device. For Visual Studio Code and Azure CLI, the connection string is in the JSON output. If you use the Azure portal to create your device, you can find the connection string from the device itself. When you select your device in your IoT hub, it's listed as `Primary connection string` on the device page.
 
 # [Portal](#tab/azure-portal)
 
@@ -125,19 +125,19 @@ To see all devices in your IoT hub, use the [az iot hub device-identity list](/c
    az iot hub device-identity list --hub-name hub_name_here
    ```
 
-Any device that is registered as an IoT Edge device will have the property **capabilities.iotEdge** set to **true**. You will see a lot of other metadata as a JSON printout, including your device IDs.
+Any device that is registered as an IoT Edge device will have the property **capabilities.iotEdge** set to **true**. You see a lot of other metadata as JSON output as well, including your device IDs.
 
 When you're ready to set up your device, you need its connection string that links your physical device with its identity in the IoT hub. Use the following [az iot hub device-identity connection-string show](/cli/azure/iot/hub/device-identity/connection-string) command to return the connection string for a single device. Replace `[device_id]` and `[hub_name]` with your own values. The value for the `device-identity` parameter is case-sensitive.
 
    ```azurecli
    az iot hub device-identity connection-string show --device-id [device_id] --hub-name [hub_name]
    ```
 
-You should see a JSON printout in the console, similar to the following:
+You should see JSON output in the console, similar to the following:
 
 ```json
 {
-  "connectionString": "HostName=my-iot-hub.azure-devices.net;DeviceId=my-edge-device-1;SharedAccessKey=saQ02bt6BBUlRcdsqWuxPMAx4ysQwWEb5+1eidwzHPY="
+  "connectionString": "HostName=my-iot-hub.azure-devices.net;DeviceId=my-edge-device-1;SharedAccessKey=saQ52bt6BBUlRfusqWuxPMAx4ysQwWEb5+1eidwzHPY="
 }
 ```