Merge pull request #312100 from jlian/fix/bug-fixes-batch

Fix wrong cmdlet, truncated sentence, restartPolicy warning, and broken anchor in IoT Edge docs

Author: prmerger-automator[bot]

articles/iot-edge/deploy-confidential-applications.md

@@ -6,7 +6,7 @@ ms.author: sethm
 ms.service: azure-iot-edge
 services: iot-edge
 ms.topic: concept-article
-ms.date: 05/08/2025
+ms.date: 02/20/2026
 ---
 
 # Confidential computing at the edge
@@ -44,7 +44,7 @@ The Open Enclave repository includes samples to help developers get started. For
 
 ## Hardware
 
-Currently, [TrustBox by Scalys](https://scalys.com/) is the only device supported with manufacturer service agreements for deploying confidential applications as IoT Edge modules. The TrustBox is built on  The TrustBox Edge and TrustBox EdgeXL devices both come preloaded with the Open Enclave SDK and Azure IoT Edge.
+Currently, [TrustBox by Scalys](https://scalys.com/) is the only device supported with manufacturer service agreements for deploying confidential applications as IoT Edge modules. The TrustBox Edge and TrustBox EdgeXL devices both come preloaded with the Open Enclave SDK and Azure IoT Edge.
 
 For more information, see [Getting started with Open Enclave for the Scalys TrustBox](https://aka.ms/scalys-trustbox-edge-get-started).
 

articles/iot-edge/how-to-configure-iot-edge-for-linux-on-windows-networking.md

@@ -3,7 +3,7 @@ title: Networking for Azure IoT Edge for Linux on Windows
 description: Learn about how to configure custom networking for Azure IoT Edge for Linux on Windows virtual machine.
 author: sethmanheim
 ms.author: sethm
-ms.date: 01/21/2025
+ms.date: 02/20/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 ms.custom: linux-related-content
@@ -95,7 +95,7 @@ C:\> Get-EflowVmAddr
 172.27.120.111
 ``` 
 
-Another way, is using the `Connect-Eflow` cmdlet to remote into the VM, and then you can use the `ifconfig eth0` bash command, and check for the *eth0* interface. The output should be similar to the following:
+Another way, is using the `Connect-EflowVm` cmdlet to remote into the VM, and then you can use the `ifconfig eth0` bash command, and check for the *eth0* interface. The output should be similar to the following:
 
 ```Output
 eth0      Link encap:Ethernet  HWaddr 00:15:5d:4e:15:2c

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

@@ -3,7 +3,7 @@ title: Create and provision Azure IoT Edge devices using symmetric keys on Linux
 description: 'Deploy IoT Edge at scale: Use symmetric keys to provision multiple Linux devices with Azure IoT Hub device provisioning service.'
 author: sethmanheim
 ms.author: sethm
-ms.date: 05/16/2025
+ms.date: 02/20/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 ms.custom:
@@ -55,7 +55,7 @@ Have the following information ready:
 
 * The DPS **ID Scope** value
 * The device **Registration ID** you created
-* Either the **Primary Key** from an individual enrollment, or a [derived key](#derive-a-device-key) for devices using a group enrollment.
+* Either the **Primary Key** from an individual enrollment, or a [derived key](/azure/iot-dps/concepts-symmetric-key-attestation#install-the-derived-device-key) for devices using a group enrollment.
 
 Create a configuration file for your device based on a template file that is provided as part of the IoT Edge installation.
 

articles/iot-edge/module-edgeagent-edgehub.md

@@ -3,7 +3,7 @@ title: Properties of the Azure IoT Edge agent and hub module twins
 description: Review the specific properties and their values for the edgeAgent and edgeHub module twins
 author: sethmanheim
 ms.author: sethm
-ms.date: 05/08/2025
+ms.date: 02/20/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -30,7 +30,7 @@ The module twin for the IoT Edge agent is called `$edgeAgent`. It coordinates co
 | Property | Description | Required |
 | -------- | ----------- | -------- |
 | imagePullPolicy | Specifies when to pull the image: *OnCreate* or *Never*. Use *Never* if the image is already on the device. | Yes |
-| restartPolicy | When the module should be restarted. Possible values are: *Never*: don't restart module if not running, *Always*: always restart module if not running, *On-Unhealthy*: restart module if unhealthy. Unhealthy is what Docker reports based on a health check, for example "Unhealthy - the container isn't working correctly", *On-Failed*: restart if Failed. | Yes |
+| restartPolicy | When the module should be restarted. Possible values are: *Never*: don't restart module if not running, *Always*: always restart module if not running, *On-Unhealthy*: restart module if unhealthy, *On-Failed*: restart if Failed. **Note:** Only *Never* and *Always* are currently implemented. *On-Unhealthy* and *On-Failed* are accepted by the schema but don't initiate a restart. See [IoT Edge limits and restrictions](iot-edge-limits-and-restrictions.md) for details. | Yes |
 | runtime.type | Must be *docker*. | Yes |
 | runtime.settings.minDockerVersion | Specifies the minimum Docker version required by this deployment manifest. | Yes |
 | runtime.settings.loggingOptions | Specifies a stringified JSON with the logging options for the IoT Edge agent container. Learn more about [Docker logging options](https://docs.docker.com/engine/admin/logging/overview/). | No |