Freshness updates for iot ops

Author: sethmanheim

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/19/2026
 ms.custom:
   - linux-related-content
   - sfi-ropc-nochange
@@ -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; for example 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)]
@@ -62,7 +62,6 @@ If you're using Visual Studio Code, there are helpful Azure IoT extensions that
 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 -->
@@ -81,11 +80,13 @@ Now that the container engine and the IoT Edge runtime are installed on your dev
 
 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'
-   ```
+```bash
+sudo iotedge config mp --connection-string 'PASTE_DEVICE_CONNECTION_STRING_HERE'
+```
+
+The following `iotedge config mp` command creates a configuration file on the device and enters your connection string in the configuration file:
 
-   This `iotedge config mp` command creates a configuration file on the device and enters your connection string in the configuration file.
+```bash
 
 1. Apply the configuration changes.
 
@@ -156,13 +157,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
@@ -67,7 +67,7 @@ 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 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)
 
@@ -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"
        }

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

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)
 

articles/iot-edge/includes/iot-edge-register-device-symmetric.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 @@ ms.custom: sfi-ropc-nochange
 
 ## Register your device
 
-You can use the **Azure portal**, **Visual Studio Code**, or **Azure CLI** to register your device, depending on your preference.
+You can use the Azure portal, Visual Studio Code, or Azure CLI to register your device, depending on your preference.
 
 # [Portal](#tab/azure-portal)
 
@@ -41,23 +41,23 @@ Once Azure IoT Edge and Azure IoT Hub extensions are installed, you notice an Az
 
 ### Register a new device with Visual Studio Code
 
-Registering a new device is akin to creating an IoT Edge device in the Azure portal. This virtual device is one of the *twins*, whereas the real world device is the other twin. Visual Studio Code can set up this virtual device for you through the following steps.
+Registering a new device is similar to creating an IoT Edge device in the Azure portal. This virtual device is one of the *twins*, whereas the real world device is the other twin. Visual Studio Code can set up this virtual device for you through the following steps:
 
 1. In the Visual Studio Code Explorer menu, expand the **Azure IoT Hub** section.
-1. Select on the **...** in the **Azure IoT Hub** section header. If you don't see the ellipsis, select or hover over the header.
+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; for example, `my-edge-device-1` (all lowercase), then 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** 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.
+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.
 
-You can now see your device listed under the **Azure IoT Hub** > **Devices** section of the Explorer menu.
+You can now see your device listed under the **Azure IoT Hub > Devices** section of the Explorer menu.
 
 > [!NOTE]
 > If your device isn't listed, you might need to choose your IoT hub from the link **Select IoT Hub** provided under **Azure IoT Hub** and then follow the prompts. The prompts ask you to choose your subscription first and then your IoT hub. This process lets Visual Studio Code know about your IoT hub (and all devices in it). Refresh Visual Studio Code and your device should show.
 
 # [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; for example, `my-edge-device-1` (all lowercase). Replace `hub_name_here` with your existing IoT hub.
 
 This command includes three parameters:
 
@@ -69,53 +69,51 @@ This command includes three parameters:
    az iot hub device-identity create --device-id device_id_here --hub-name hub_name_here --edge-enabled
    ```
 
-If your CLI says **The command requires the extension azure-iot. Do you want to install it now?**, then type `Y` and press `Enter` to initiate the download to create your device.
+If your CLI says **The command requires the extension azure-iot. Do you want to install it now?**, type **Y** and press **Enter** to initiate the download and create your device.
 
 ---
 
-Now that you have a device registered in IoT Hub, you can retrieve provisioning information used to complete the installation and provisioning of the [IoT Edge runtime](../iot-edge-runtime.md) in the next step.
+Now that you have a device registered in IoT Hub, in the next step you can retrieve provisioning information used to complete the installation and provisioning of the [IoT Edge runtime](../iot-edge-runtime.md).
 
 ## 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 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.
+Devices that use symmetric key authentication need their connection strings to complete installation and provisioning of the IoT Edge runtime. The connection string is generated for your IoT Edge device when you create the device. For Visual Studio Code and Azure CLI, the connection string appears 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)
 
-The edge-enabled devices that connect to your IoT hub are listed on the **Devices** page of your IoT hub. If you have multiple devices, you can filter the list by selecting the type **Iot Edge Devices**, then select **Apply**. 
+The edge-enabled devices that connect to your IoT hub are listed on the **Devices** page of your IoT hub. If you have multiple devices, you can filter the list by selecting the **Iot Edge Devices** type, then select **Apply**. 
 
-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:
+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.
 
 # [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 see the **$edgeAgent** and **$edgeHub** modules are deployed to each IoT Edge device.
+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.
 
-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.
+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:
 
-1. Right-click on the ID (name) of your device in the **Azure IoT Hub** section.
-1. Select **Copy Device Connection String**.
+1. Right-click the ID (name) of your device in the **Azure IoT Hub** section.
+1. Select **Copy Device Connection String**. The connection string is copied to your clipboard.
 
-   The connection string is copied to your clipboard.
-
-You can also select **Get Device Info** from the right-click menu to see all the device info, including the connection string, in the output window.
+You can also select **Get Device Info** from the right-click context menu to see all the device info, including the connection string, in the output window.
 
 # [Azure CLI](#tab/azure-cli)
 
-To see all devices in your IoT hub, use the [az iot hub device-identity list](/cli/azure/iot/hub/device-identity) command. Replace `hub_name_here` with your own IoT hub name.
+To see all devices in your IoT hub, use the [`az iot hub device-identity list`](/cli/azure/iot/hub/device-identity) command. Replace `hub_name_here` with your own IoT hub name:
 
-   ```azurecli
-   az iot hub device-identity list --hub-name hub_name_here
-   ```
+```azurecli
+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 see a lot of other metadata as JSON output as well, including your device IDs.
+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.
 
-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.
+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]
-   ```
+```azurecli
+az iot hub device-identity connection-string show --device-id [device_id] --hub-name [hub_name]
+```
 
 You should see JSON output in the console, similar to the following example:
 

articles/iot-edge/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: sethmanheim
   ms.author: sethm
-  ms.date: 03/31/2025
+  ms.date: 02/19/2026
   ms.custom: e2e-hybrid
 
 landingContent: