Documentor passes

Author: sethmanheim

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

@@ -19,7 +19,7 @@ ms.custom:
 
 This article provides end-to-end instructions for registering and provisioning a Linux IoT Edge device that includes installing IoT Edge.
 
-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:
+Each device that connects to an [IoT hub](../iot-hub/index.yml) has a device ID that tracks [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
@@ -29,7 +29,7 @@ The steps in this article walk through a process called *manual provisioning*, w
 
 * **Symmetric keys**: When you create a new device identity in IoT Hub, the service creates two keys. You place one of the keys on the device, and it presents the key to IoT Hub when authenticating.
 
-  This authentication method is faster to get started, but not as secure.
+  This authentication method is faster to get started, but isn't as secure.
 
 * **X.509 self-signed**: You create two X.509 identity certificates and place them on the device. When you create a new device identity in IoT Hub, you provide thumbprints from both certificates. When the device authenticates to IoT Hub, it presents one certificate and IoT Hub verifies that the certificate matches its thumbprint.
 
@@ -46,7 +46,7 @@ This article covers using symmetric keys as your authentication method. If you w
 
 ## Prerequisites
 
-This article shows how to register your IoT Edge device and install IoT Edge (also called IoT Edge runtime) on your device. Make sure you have the device management tool of your choice; for example Azure CLI, and review device requirements before you register and install your device.
+This article shows how to register your IoT Edge device and install IoT Edge (also called IoT Edge runtime) on your device. Make sure you have the device management tool of your choice, such as Azure CLI, and review device requirements before you register and install your device.
 
 <!-- Device registration prerequisites H3 and content -->
 [!INCLUDE [iot-edge-prerequisites-register-device.md](includes/iot-edge-prerequisites-register-device.md)]
@@ -57,7 +57,7 @@ This article shows how to register your IoT Edge device and install IoT Edge (al
 <!-- Azure IoT extensions for Visual Studio Code-->
 ### Visual Studio Code extensions
 
-If you're using Visual Studio Code, there are helpful Azure IoT extensions that make the device creation and management process easier.
+If you're using Visual Studio Code, helpful Azure IoT extensions make the device creation and management process easier.
 
 Install both the Azure IoT Edge and Azure IoT Hub extensions:
 
@@ -74,11 +74,11 @@ Install both the Azure IoT Edge and Azure IoT Hub extensions:
 
 ## Provision the device with its cloud identity
 
-Now that the container engine and the IoT Edge runtime are installed on your device, you're ready to set up the device with its cloud identity and authentication information.
+After you install the container engine and the IoT Edge runtime on your device, set up the device with its cloud identity and authentication information.
 
 # [Ubuntu / Debian / RHEL](#tab/ubuntu+debian+rhel)
 
-You can configure your IoT Edge device with symmetric key authentication using the following command:
+You can configure your IoT Edge device with symmetric key authentication by using the following command:
 
 ```bash
 sudo iotedge config mp --connection-string 'PASTE_DEVICE_CONNECTION_STRING_HERE'

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

@@ -17,12 +17,12 @@ Run the following commands to add the package repository and then add the Micros
 > [!IMPORTANT]
 > On June 30, 2022, Raspberry Pi OS Stretch was retired from the Tier 1 OS support list. To avoid potential security vulnerabilities, update your host OS to Bullseye.
 >
-> For [tier 2 supported platform operating systems](../support.md#tier-2), installation packages are made available at [Azure IoT Edge releases](https://github.com/Azure/azure-iotedge/releases). See the installation steps in [Offline or specific version installation (optional)](../how-to-provision-single-device-linux-symmetric.md#offline-or-specific-version-installation-optional).
+> For [tier 2 supported platform operating systems](../support.md#tier-2), installation packages are available at [Azure IoT Edge releases](https://github.com/Azure/azure-iotedge/releases). See the installation steps in [Offline or specific version installation (optional)](../how-to-provision-single-device-linux-symmetric.md#offline-or-specific-version-installation-optional).
 
 
 # [Ubuntu](#tab/ubuntu)
 
-Installing can be done with a few commands. Open a terminal and run the following commands:
+You can install IoT Edge by using a few commands. Open a terminal and run the following commands:
 
 * **24.04**:
 
@@ -50,7 +50,7 @@ Installing can be done with a few commands. Open a terminal and run the followin
 
 # [Debian](#tab/debian)
 
-Installing with APT can be done with a few commands. Open a terminal and run the following commands:
+You can install it by using APT and running a few commands. Open a terminal and run the following commands:
 
 * **12 - Bookworm (arm32v7)**:
 
@@ -67,11 +67,11 @@ Installing with APT can be done with a few commands. Open a terminal and run the
     ```
 
 > [!TIP]
-> If you gave the "root" account a password during the OS install, you don't need `sudo`, and can run the previous command by starting with `apt`.
+> If you set a password for the "root" account during the OS installation, you don't need `sudo`. You can run the previous command by starting with `apt`.
 
 # [Red Hat Enterprise Linux](#tab/rhel)
 
-Installing can be done with a few commands. Open a terminal and run the following commands:
+You can install IoT Edge by using a few commands. Open a terminal and run the following commands:
 
 * **9.x (amd64)**:
 
@@ -91,7 +91,7 @@ Installing can be done with a few commands. Open a terminal and run the followin
 
 # [Ubuntu Core snaps](#tab/snaps)
 
-You install IoT Edge runtime from the snap store in a later step. Continue to the next section.
+You install the IoT Edge runtime from the snap store in a later step. Continue to the next section.
 
 ---
 
@@ -102,7 +102,7 @@ For more information about operating system versions, see [Azure IoT Edge suppor
 
 ### Install a container engine
 
-Azure IoT Edge relies on an [OCI](https://opencontainers.org/)-compatible container runtime. For production scenarios, we recommend that you use the Moby engine. The Moby engine is the container engine officially supported with IoT Edge. Docker CE/EE container images are compatible with the Moby runtime. If you're using Ubuntu Core snaps, the Docker snap is serviced by Canonical and supported for production scenarios.
+Azure IoT Edge relies on an [OCI](https://opencontainers.org/)-compatible container runtime. For production scenarios, use the Moby engine. The Moby engine is the container engine officially supported with IoT Edge. Docker CE and Docker EE container images work with the Moby runtime. If you're using Ubuntu Core snaps, Canonical services the Docker snap and supports it for production scenarios.
 
 # [Ubuntu](#tab/ubuntu)
 
@@ -139,11 +139,11 @@ Install the Moby engine and CLI.
 >   ./check-config.sh
 >   ```
 >
-> In the output of the script, check that all items under `Generally Necessary` and `Network Drivers` are enabled. If you're missing features, enable them by rebuilding your kernel from source and selecting the associated modules for inclusion in the appropriate kernel .config. Similarly, if you're using a kernel configuration generator like `defconfig` or `menuconfig`, find and enable the respective features and rebuild your kernel accordingly. After you deploy your newly modified kernel, run the check-config script again to verify that all the required features were successfully enabled.
+> In the output of the script, check that all items under `Generally Necessary` and `Network Drivers` are enabled. If you're missing features, enable them by rebuilding your kernel from source and selecting the associated modules for inclusion in the appropriate kernel .config. Similarly, if you're using a kernel configuration generator like `defconfig` or `menuconfig`, find and enable the respective features and rebuild your kernel accordingly. After you deploy your newly modified kernel, run the check-config script again to verify that all the required features are successfully enabled.
 
 # [Ubuntu Core snaps](#tab/snaps)
 
-IoT Edge has dependencies on Docker and IoT Identity Service. Install the dependencies using the following commands:
+IoT Edge has dependencies on Docker and IoT Identity Service. Install the dependencies by using the following commands:
 
 ```bash
 sudo snap install docker
@@ -182,7 +182,7 @@ The following steps show you how to configure your container to use the [`local`
 
 # [Ubuntu Core snaps](#tab/snaps)
 
-Currently, the `local` logging driver setting isn't supported for the Docker snap.
+Currently, the Docker snap doesn't support the `local` logging driver setting.
 
 ---
 
@@ -241,7 +241,7 @@ sudo snap install azure-iot-edge
 
 ### Connect snaps
 
-By default, snaps are dependency-free, untrusted, and strictly confined. Hence, snaps must be connected to other snaps and system resources after installation. Use the following commands to connect the IoT Identity Service and IoT Edge snaps to each other and to system resources. To get started, snaps need to be manually connected. For production deployments, they can be configured to automatically connect to reduce the provisioning workload.
+By default, snaps are dependency-free, untrusted, and strictly confined. Hence, you must connect snaps to other snaps and system resources after installation. Use the following commands to connect the IoT Identity Service and IoT Edge snaps to each other and to system resources. To get started, manually connect the snaps. For production deployments, you can configure them to automatically connect to reduce the provisioning workload.
 
 ```bash
 #------------------------

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

@@ -10,7 +10,7 @@ services: iot-edge
 
 ### Device requirements
 
-An X64, ARM32, or ARM64 Linux device.
+An x64, ARM32, or ARM64 Linux device.
 
 Microsoft publishes installation packages for various operating systems.
 

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

@@ -14,16 +14,16 @@ You can use the Azure portal, Visual Studio Code, or Azure CLI to register your
 
 # [Portal](#tab/azure-portal)
 
-In your IoT hub in the Azure portal, IoT Edge devices are created and managed separately from IoT devices that aren't edge enabled.
+In your IoT hub in the Azure portal, you create and manage IoT Edge devices separately from IoT devices that aren't edge enabled.
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT hub.
+1. Sign in to the [Azure portal](https://portal.azure.com) and go to your IoT hub.
 
-1. In the left pane, select **Devices** from the menu, then select **Add Device**.
+1. In the left pane, select **Devices** from the menu, and then select **Add Device**.
 
-1. On the **Create a device** page, provide the following information:
+1. On **Create a device**, provide the following information:
 
-   * Create a descriptive Device ID, for example `my-edge-device-1` (all lowercase). Copy this Device ID, as you use it later.
-   * Check the **IoT Edge Device** checkbox.
+   * Create a descriptive Device ID, such as `my-edge-device-1` (all lowercase). Copy this Device ID, as you use it later.
+   * Select the **IoT Edge Device** checkbox.
    * Select **Symmetric key** as the authentication type.
    * Use the default settings to autogenerate authentication keys, which connect the new device to your hub.
 
@@ -35,9 +35,9 @@ You should see your new device listed in your IoT hub.
 
 ### Sign in to Azure
 
-You can use the Azure IoT extensions for Visual Studio Code to perform operations with your IoT hub. Make sure you install the Azure IoT extension prerequisites. 
+Use the Azure IoT extensions for Visual Studio Code to perform operations with your IoT hub. Make sure you install the Azure IoT extension prerequisites. 
 
-Once Azure IoT Edge and Azure IoT Hub extensions are installed, you notice an Azure icon gets added to the left icon menu. You can sign in to your Azure account through Visual Studio Code by selecting the Azure icon and then select **Sign in to Azure**. 
+After you install the Azure IoT Edge and Azure IoT Hub extensions, you see an Azure icon in the left icon menu. Sign in to your Azure account through Visual Studio Code by selecting the Azure icon and then selecting **Sign in to Azure**. 
 
 ### Register a new device with Visual Studio Code
 
@@ -46,7 +46,7 @@ Registering a new device is similar to creating an IoT Edge device in the Azure
 1. In the Visual Studio Code Explorer menu, expand the **Azure IoT Hub** section.
 1. Select the **...** ellipsis in the **Azure IoT Hub** section header. If you don't see the ellipsis, select or hover over the header.
 1. Select **Create IoT Edge Device**.
-1. In the text box that opens, give your device an ID; for example, `my-edge-device-1` (all lowercase), then press **Enter**.
+1. In the text box that opens, give your device an ID, such as `my-edge-device-1` (all lowercase), and press **Enter**.
 
 In the output console of Visual Studio Code, you see the result of the command: a JSON printout. The device information includes the **deviceId** that you provided and generates a **connectionString** value that you can use to connect your physical device to your IoT hub. The output console also shows your keys and other device identifying information.
 
@@ -57,7 +57,7 @@ You can now see your device listed under the **Azure IoT Hub > Devices** section
 
 # [Azure CLI](#tab/azure-cli)
 
-Use the [`az iot hub device-identity create`](/cli/azure/iot/hub/device-identity) command to create a new device identity in your IoT hub. Replace `device_id_here` with your own new and unique device ID; for example, `my-edge-device-1` (all lowercase). Replace `hub_name_here` with your existing IoT hub.
+Use the [`az iot hub device-identity create`](/cli/azure/iot/hub/device-identity) command to create a new device identity in your IoT hub. Replace `device_id_here` with your own new and unique device ID, such as `my-edge-device-1` (all lowercase). Replace `hub_name_here` with your existing IoT hub.
 
 This command includes three parameters:
 
@@ -86,11 +86,11 @@ The edge-enabled devices that connect to your IoT hub are listed on the **Device
 When you're ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub. Devices that authenticate with symmetric keys have their connection strings available to copy in the portal. To find your connection string in the portal, perform the following steps:
 
 1. From the **Devices** page, select the IoT Edge device ID from the list.
-2. Copy the value of either **Primary Connection String** or **Secondary Connection String**. Either key works.
+1. Copy the value of either **Primary Connection String** or **Secondary Connection String**. Either key works.
 
 # [Visual Studio Code](#tab/visual-studio-code)
 
-All the devices that connect to your IoT hub are listed in the **Azure IoT Hub** section of the Visual Studio Code Explorer. IoT Edge devices are distinguishable from non-edge devices because they have a different icon, and you can see that the **$edgeAgent** and **$edgeHub** modules are deployed to each IoT Edge device.
+The **Azure IoT Hub** section of the Visual Studio Code Explorer lists all the devices that connect to your IoT hub. IoT Edge devices have a different icon, so you can easily distinguish them from non-edge devices. You can see that the **$edgeAgent** and **$edgeHub** modules are deployed to each IoT Edge device.
 
 When you're ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub. Here's how to get your connection string from Visual Studio Code:
 
@@ -107,7 +107,7 @@ To see all devices in your IoT hub, use the [`az iot hub device-identity list`](
 az iot hub device-identity list --hub-name hub_name_here
 ```
 
-Any device that is registered as an IoT Edge device has the property **capabilities.iotEdge** set to **true**. You can see a lot of other metadata as JSON output as well, including your device IDs.
+Any device that you register as an IoT Edge device has the property **capabilities.iotEdge** set to **true**. You can 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.
 
@@ -126,6 +126,6 @@ You should see JSON output in the console, similar to the following example:
 >[!TIP]
 >The `connection-string show` command was introduced in version 0.9.8 of the Azure IoT extension, replacing the deprecated `show-connection-string` command. If you get an error running this command, make sure your extension version is updated to 0.9.8 or later. For more information and the latest updates, see [Microsoft Azure IoT extension for Azure CLI](https://github.com/Azure/azure-iot-cli-extension).
 
-When copying the connection string to use on a device, don't include the quotation marks around the connection string.
+When you copy the connection string to use on a device, don't include the quotation marks around the connection string.
 
 ---

articles/iot-edge/iot-edge-as-gateway.md

@@ -35,7 +35,7 @@ All gateway patterns provide the following benefits:
 
 ## Transparent gateways
 
-In the transparent gateway pattern, devices that theoretically can connect to IoT Hub can connect to a gateway device instead. These devices, called *downstream devices* or *child devices*, have their own IoT Hub identities and connect by using either MQTT or AMQP protocols. The gateway simply passes communications between the devices and IoT Hub. Both the devices and the users interacting with them through IoT Hub are unaware that a gateway is mediating their communications. This lack of awareness means the gateway is considered *transparent*.
+In the transparent gateway pattern, devices that can connect to IoT Hub can connect to a gateway device instead. These devices, called *downstream devices* or *child devices*, have their own IoT Hub identities and connect by using either MQTT or AMQP protocols. The gateway simply passes communications between the devices and IoT Hub. Both the devices and the users interacting with them through IoT Hub are unaware that a gateway is mediating their communications. This lack of awareness means the gateway is considered *transparent*.
 
 For more information about how the IoT Edge hub manages communication between downstream devices and the cloud, see the [Azure IoT Edge runtime and architecture overview](iot-edge-runtime.md).