Merge pull request #299054 from DENKEN02MSFT/Top50_patricka_Row3

Top50 - row 3

Author: JillGrant615

articles/iot-edge/configure-device.md

@@ -156,7 +156,7 @@ symmetric_key = { uri = "file:///var/aziot/secrets/device-id.key" }
 symmetric_key = { uri = "pkcs11:slot-id=0;object=device%20id?pin-value=1234" }    
 ```
 
-For more information about DPS provisioning with symmetric key, see [Create and provision IoT Edge devices at scale on Linux using symmetric key](how-to-provision-devices-at-scale-linux-symmetric.md).
+For more information about DPS provisioning with symmetric key, see [Create and provision IoT Edge devices at scale on Linux using symmetric keys](how-to-provision-devices-at-scale-linux-symmetric.md).
 
 ### DPS provisioning with X.509 certificates
 

articles/iot-edge/how-to-provision-devices-at-scale-linux-symmetric.md

@@ -4,12 +4,12 @@ description: Use symmetric key attestation to test provisioning Linux devices at
 author: PatAltimore
 ms.author: patricka
 ms.date: 02/27/2024
-ms.topic: conceptual
+ms.topic: concept-article
 ms.service: azure-iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ---
-# Create and provision IoT Edge devices at scale on Linux using symmetric key
+# Create and provision IoT Edge devices at scale on Linux using symmetric keys
 
 [!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
 

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

@@ -7,7 +7,7 @@ ms.service: azure-iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: how-to
-ms.date: 03/04/2024
+ms.date: 04/29/2025
 ms.author: patricka
 ms.reviewer: mattmcinnes
 ---
@@ -39,9 +39,9 @@ This article covers using symmetric keys as your authentication method. If you w
 > [!NOTE]
 > If you have many devices to set up and don't want to manually provision each one, use one of the following articles to learn how IoT Edge works with the IoT Hub device provisioning service:
 >
-> * [Create and provision IoT Edge devices at scale using X.509 certificates](how-to-provision-devices-at-scale-linux-x509.md)
-> * [Create and provision IoT Edge devices at scale with a TPM](how-to-provision-devices-at-scale-linux-tpm.md)
-> * [Create and provision IoT Edge devices at scale using symmetric keys](how-to-provision-devices-at-scale-linux-symmetric.md)
+> * [Create and provision IoT Edge devices at scale on Linux using X.509 certificates](how-to-provision-devices-at-scale-linux-x509.md)
+> * [Create and provision IoT Edge devices at scale with a TPM on Linux](how-to-provision-devices-at-scale-linux-tpm.md)
+> * [Create and provision IoT Edge devices at scale on Linux using symmetric keys](how-to-provision-devices-at-scale-linux-symmetric.md)
 
 ## Prerequisites
 
@@ -56,7 +56,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 are 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, there are helpful Azure IoT extensions that make the device creation and management process easier.
 
 Install both the Azure IoT Edge and Azure IoT Hub extensions:
 
@@ -167,25 +167,25 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
    sudo iotedge check
    ```
 
-   You can expect a range of responses that may include **OK** (green), **Warning** (yellow), or **Error** (red). For troubleshooting common errors, see [Solutions to common issues for Azure IoT Edge](troubleshoot-common-errors.md).
+   You can expect a range of responses that might include **OK** (green), **Warning** (yellow), or **Error** (red). For troubleshooting common errors, see [Solutions to common issues for Azure IoT Edge](troubleshoot-common-errors.md).
 
    :::image type="content" source="media/how-to-provision-single-device-linux-symmetric/config-checks.png" alt-text="Screenshot of sample responses from the check command." lightbox="media/how-to-provision-single-device-linux-symmetric/config-checks.png":::
 
    >[!TIP]
    >Always use `sudo` to run the check tool, even after your permissions are updated. The tool needs elevated privileges to access the config file to verify configuration status.
 
    >[!NOTE]
-   >On a newly provisioned device, you may see an error related to IoT Edge Hub:
+   >On a newly provisioned device, you might 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. Be sure your IoT Edge modules were deployed in the previous steps. Deployment resolves this error.
+   >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't yet running. Be sure your IoT Edge modules were deployed in the previous steps. Deployment resolves this error.
    >
-   >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.
+   >Alternatively, you might see a status code as `417 -- The device's deployment configuration is not set`. Once your modules are deployed, this status changes.
    >
 
-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.
+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 other modules that you deploy to your device.
 
    Check that your device and modules are deployed and running, by viewing your device page in the Azure portal.
 
@@ -199,14 +199,14 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
 
 ## Offline or specific version installation (optional)
 
-The steps in this section are for scenarios not covered by the standard installation steps. This may include:
+The steps in this section are for scenarios not covered by the standard installation steps. These scenarios might 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](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.
+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 subversions, so these steps are for anyone who wants to install an older version or a release candidate version.
 
-If you are using Ubuntu snaps, you can download a snap and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
+If you're using Ubuntu snaps, you can download a snap and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
 
 Using curl commands, you can target the component files directly from the IoT Edge GitHub repository.
 
@@ -231,7 +231,7 @@ Using curl commands, you can target the component files directly from the IoT Ed
       ```
 
       # [Ubuntu Core snaps](#tab/snaps)
-      If you are using Ubuntu snaps, you can download a snap package and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
+      If you're using Ubuntu snaps, you can download a snap package and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
 
       ---
 
@@ -250,7 +250,7 @@ Using curl commands, you can target the component files directly from the IoT Ed
       ```
 
       # [Ubuntu Core snaps](#tab/snaps)
-      If you are using Ubuntu snaps, you can download a snap package and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
+      If you're using Ubuntu snaps, you can download a snap package and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
 
       ---
 

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

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 12/04/2024
+ms.date: 04/29/2025
 author: PatAltimore
 ms.author: patricka
 ms.service: azure-iot-edge
@@ -15,16 +15,14 @@ In this section, you prepare your Linux virtual machine or physical device for I
 Run the following commands to add the package repository and then add the Microsoft package signing key to your list of trusted keys.
 
 > [!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.
+> 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](../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 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).
 
 
 # [Ubuntu](#tab/ubuntu)
 
-Installing can be done with a few commands.  Open a terminal and run the following commands:
-
-
+Installing can be done with a few commands. Open a terminal and run the following commands:
 
 * **24.04**:
 
@@ -34,8 +32,6 @@ Installing can be done with a few commands.  Open a terminal and run the followi
    rm packages-microsoft-prod.deb
    ```
 
-
-
 * **22.04**:
 
    ```bash
@@ -54,9 +50,7 @@ Installing can be done with a few commands.  Open a terminal and run the followi
 
 # [Debian](#tab/debian)
 
-Installing with APT can be done with a few commands.  Open a terminal and run the following commands:
-
-
+Installing with APT can be done with a few commands. Open a terminal and run the following commands:
 
 * **12 - Bookworm (arm32v7)**:
 
@@ -65,8 +59,6 @@ Installing with APT can be done with a few commands.  Open a terminal and run th
     sudo apt install ./packages-microsoft-prod.deb
     ```
 
-
-
 * **11 - Bullseye (arm32v7)**:
 
     ```bash
@@ -75,7 +67,7 @@ Installing with APT can be done with a few commands.  Open a terminal and run th
     ```
 
 > [!TIP]
-> If you gave the "root" account a password during the OS install, you will not need 'sudo' and can run the above command by starting with 'apt'.
+> 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'.
 
 # [Red Hat Enterprise Linux](#tab/rhel)
 
@@ -106,11 +98,11 @@ You install IoT Edge runtime from the snap store in a later step. Continue to th
 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.
+> 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 before 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.
 
 ### 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 are 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, 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.
 
 # [Ubuntu](#tab/ubuntu)
 
@@ -147,7 +139,7 @@ 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've deployed 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 were successfully enabled.
 
 # [Ubuntu Core snaps](#tab/snaps)
 
@@ -162,7 +154,7 @@ The Docker snap is serviced by Canonical and supported for production scenarios.
 
 ---
 
-By default, the container engine doesn't set container log size limits. Over time, this can lead to the device filling up with logs and running out of disk space. However, you can configure your log to show locally, though it's optional. To learn more about logging configuration, see [Production Deployment Checklist](../production-checklist.md#set-up-default-logging-driver).
+By default, the container engine doesn't set container log size limits. Over time, this situation can lead to the device filling up with logs and running out of disk space. However, you can configure your log to show locally, though it's optional. To learn more about logging configuration, see [Prepare to deploy your IoT Edge solution in production](../production-checklist.md#set-up-default-logging-driver).
 
 The following steps show you how to configure your container to use [`local` logging driver](https://docs.docker.com/config/containers/logging/local/) as the logging mechanism. 
 
@@ -190,7 +182,7 @@ The following steps show you how to configure your container to use [`local` log
 
 # [Ubuntu Core snaps](#tab/snaps)
 
-Currently, the local logging driver setting is not supported for the Docker snap.
+Currently, the `local` logging driver setting isn't supported for the Docker snap.
 
 ---
 
@@ -199,12 +191,12 @@ Currently, the local logging driver setting is not supported for the Docker snap
 The IoT Edge service provides and maintains security standards on the IoT Edge device. The service starts on every boot and bootstraps the device by starting the rest of the IoT Edge runtime.
 
 > [!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.
+> Beginning with version 1.2, the [Azure 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** 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 prerelease 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](../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 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.
 
 # [Ubuntu](#tab/ubuntu)
 

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

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 06/10/2024
+ms.date: 04/29/2025
 author: PatAltimore
 ms.author: patricka
 ms.service: azure-iot-edge
@@ -12,6 +12,6 @@ services: iot-edge
 
 An X64, ARM32, or ARM64 Linux device.
 
-Microsoft publishes installation packages for a variety of operating systems.
+Microsoft publishes installation packages for various 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).
+For the latest information about which operating systems are currently supported for production scenarios, see [Azure IoT Edge supported platforms](../support.md#operating-systems).

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

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 06/10/2024
+ms.date: 04/29/2025
 author: PatAltimore
 ms.author: patricka
 ms.service: azure-iot-edge
@@ -9,7 +9,7 @@ services: iot-edge
 
 ### Device management tools
 
-You can use the **Azure portal**, **Visual Studio Code**, or **Azure CLI** for the steps to register your device. Each utility has its own prerequisites or may need to be installed:
+You can use the **Azure portal**, **Visual Studio Code**, or **Azure CLI** for the steps to register your device. Each utility has its own prerequisites or might need to be installed:
 
 # [Portal](#tab/azure-portal)