Fix factual errors and stale references in IoT Edge docs

- Fix incorrect 'Microsoft Monitoring Agent (MMA)' reference to 'IoT Edge agent' in module twins page
- Align SimulatedTemperatureSensor module version field from '1.0' to '1.5' to match image tag
- Standardize deployment manifest file extension guidance from .txt to .json
- Update stale .NET 6.0 LTS reference to .NET 8.0 LTS in dTPM page
- Update stale diagnostics image tag from :1.2 to :1.5 in troubleshoot nested edge example

Author: jlian

articles/iot-edge/how-to-access-dtpm.md

@@ -3,7 +3,7 @@ title: dTPM access for Azure IoT Edge for Linux on Windows
 description: Learn about how to configure access the dTPM on your  Azure IoT Edge for Linux on Windows virtual machine.
 author: sethmanheim
 ms.author: sethm
-ms.date: 06/05/2025
+ms.date: 04/01/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 ms.custom: linux-related-content
@@ -47,7 +47,7 @@ Follow these steps to create a sample executable to access a TPM index from the
 
 1. Fill in the **Project Name**, **Location**, and **Solution Name** fields, and then select **Next**.
 
-1. Choose a target framework. The latest .NET 6.0 LTS version is preferred. After you choose a target framework, select **Create**. Visual Studio creates a new console app solution.
+1. Choose a target framework. The latest .NET LTS version is preferred (currently .NET 8.0). After you choose a target framework, select **Create**. Visual Studio creates a new console app solution.
 
 1. In **Solution Explorer**, right-click the project name and select **Manage NuGet Packages**.
 

articles/iot-edge/how-to-deploy-cli-at-scale.md

@@ -3,7 +3,7 @@ title: Deploy Azure IoT Edge modules at scale using Azure CLI
 description: Deploy Azure IoT Edge modules at scale using Azure CLI to automate, monitor, and manage device deployments efficiently.
 author: sethmanheim
 ms.author: sethm
-ms.date: 05/16/2025
+ms.date: 04/01/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 ms.custom:
@@ -36,7 +36,7 @@ In this article, you set up the Azure CLI and the IoT extension. Then, you deplo
 
 A deployment manifest is a JSON document that describes which modules to deploy, how data flows between the modules, and the desired properties of the module twins. For more information, see [Learn how to deploy modules and establish routes in IoT Edge](module-composition.md).
 
-To deploy modules by using the Azure CLI, save the deployment manifest locally as a .txt file. You'll use the file path in the next section when you run the command to apply the configuration to your device.
+To deploy modules by using the Azure CLI, save the deployment manifest locally as a .json file. You'll use the file path in the next section when you run the command to apply the configuration to your device.
 
 Here's a basic deployment manifest with one module as an example.
 

articles/iot-edge/how-to-deploy-modules-cli.md

@@ -3,7 +3,7 @@ title: Deploy Azure IoT Edge Modules Using Azure CLI
 description: Use the Azure CLI with the Azure IoT Extension to push an IoT Edge module from your IoT Hub to your IoT Edge device, as configured by a deployment manifest.
 author: sethmanheim
 ms.author: sethm
-ms.date: 05/08/2025
+ms.date: 04/01/2026
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -81,7 +81,7 @@ Here is a basic deployment manifest with one module as an example:
           },
           "modules": {
             "SimulatedTemperatureSensor": {
-              "version": "1.0",
+              "version": "1.5",
               "type": "docker",
               "status": "running",
               "restartPolicy": "always",

articles/iot-edge/how-to-monitor-module-twins.md

@@ -3,7 +3,7 @@ title: Monitor module twins - Azure IoT Edge
 description: How to interpret device twins and module twins to determine connectivity and health.
 author: sethmanheim
 ms.author: sethm
-ms.date: 06/09/2025
+ms.date: 04/01/2026
 ms.topic: how-to
 ms.service: azure-iot-edge
 services: iot-edge
@@ -102,7 +102,7 @@ Check these properties when you troubleshoot:
     | running | The module is running. |
     | unhealthy | A health-probe check failed or timed out. |
     | stopped | The module exited successfully (with a zero exit code). |
-    | failed | The module exited with a failure exit code (non-zero). The module can go back to backoff from this state depending on the restart policy. This state means the module has an unrecoverable error. Failure happens when the Microsoft Monitoring Agent (MMA) can't restart the module, requiring a new deployment. |
+    | failed | The module exited with a failure exit code (non-zero). The module can go back to backoff from this state depending on the restart policy. This state means the module has an unrecoverable error. Failure happens when the IoT Edge agent can't restart the module, requiring a new deployment. |
 
 For details, see [EdgeAgent reported properties](module-edgeagent-edgehub.md#edgeagent-reported-properties).
 

articles/iot-edge/troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure IoT Edge
 description: Use this article to learn standard diagnostic skills for Azure IoT Edge, like retrieving component status and logs
 author: sethmanheim
 ms.author: sethm
-ms.date: 02/27/2026
+ms.date: 04/01/2026
 ms.topic: troubleshooting-general
 ms.service: azure-iot-edge
 services: iot-edge
@@ -39,7 +39,7 @@ The IoT Edge check tool uses a container to run its diagnostics. The container i
 In a scenario that uses nested IoT Edge devices, you can get access to the diagnostics image on downstream devices by routing the image pull through the parent devices.
 
 ```bash
-sudo iotedge check --diagnostics-image-name <parent_device_fqdn_or_ip>:<port_for_api_proxy_module>/azureiotedge-diagnostics:1.2
+sudo iotedge check --diagnostics-image-name <parent_device_fqdn_or_ip>:<port_for_api_proxy_module>/azureiotedge-diagnostics:1.5
 ```
 
 For information about each of the diagnostic checks this tool runs, including what to do if you get an error or warning, see [Built-in troubleshooting functionality](https://github.com/Azure/iotedge/blob/main/doc/troubleshoot-checks.md).