Merge pull request #312078 from sethmanheim/iotfrsh2-19

Freshness updates for iot ops

Author: denrea

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

@@ -7,7 +7,7 @@ ms.author: sethm
 ms.service: azure-iot-edge
 services: iot-edge
 ms.topic: how-to
-ms.date: 04/29/2025
+ms.date: 02/20/2026
 ms.custom:
   - linux-related-content
   - sfi-ropc-nochange
@@ -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 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,12 +57,11 @@ 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:
 
 * [Azure IoT Edge](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-edge). The *Azure IoT Edge tools for Visual Studio Code* extension is in [maintenance mode](https://github.com/microsoft/vscode-azure-iot-edge/issues/639).
-
 * [Azure IoT Hub](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-toolkit)
 
 <!-- Prerequisites end -->
@@ -75,17 +74,15 @@ 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:
-
-   ```bash
-   sudo iotedge config mp --connection-string 'PASTE_DEVICE_CONNECTION_STRING_HERE'
-   ```
+You can configure your IoT Edge device with symmetric key authentication by using the following command:
 
-   This `iotedge config mp` command creates a configuration file on the device and enters your connection string in the configuration file.
+```bash
+sudo iotedge config mp --connection-string 'PASTE_DEVICE_CONNECTION_STRING_HERE'
+```
 
 1. Apply the configuration changes.
 
@@ -156,13 +153,13 @@ Verify that the runtime was successfully installed and configured on your IoT Ed
 
    A successful status response shows the `aziot` services as running or ready.
 
-1. If you need to troubleshoot the service, retrieve the service logs.
+1. If you need to troubleshoot the service, retrieve the service logs:
 
    ```bash
    sudo iotedge system logs
    ```
 
-1. Use the `check` tool to verify configuration and connection status of the device.
+1. Use the `check` tool to verify configuration and connection status of the device:
 
    ```bash
    sudo iotedge check

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

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 04/29/2025
+ms.date: 02/19/2026
 author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
@@ -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
@@ -154,21 +154,21 @@ 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 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).
+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. For more information 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. 
+The following steps show you how to configure your container to use the [`local` logging driver](https://docs.docker.com/config/containers/logging/local/) as the logging mechanism. 
 
 # [Ubuntu / Debian / RHEL](#tab/ubuntu+debian+rhel)
 
-1. Create or edit the existing Docker [daemon's config file](https://docs.docker.com/config/daemon/)
+1. Create or edit the existing Docker [daemon's config file](https://docs.docker.com/config/daemon/):
 
     ```bash
     sudo nano /etc/docker/daemon.json
     ```
 
-1. Set the default logging driver to the `local` logging driver as shown in the example.
+1. Set the default logging driver to the `local` logging driver as shown in the example:
 
-    ```JSON
+    ```json
        {
           "log-driver": "local"
        }
@@ -182,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 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

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 04/29/2025
+ms.date: 02/19/2026
 author: sethmanheim
 ms.author: sethm
 ms.service: azure-iot-edge
@@ -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-prerequisites-register-device.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 04/29/2025
+ms.date: 02/19/2026
 author: sethmanheim
 ms.author: sethm
 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 might need to be installed:
+You can use the Azure portal, Visual Studio Code, or the Azure CLI to register your device. Each utility has its own prerequisites or might need to be installed:
 
 # [Portal](#tab/azure-portal)