Merge pull request #299957 from DENKEN02MSFT/Top50_patricka_Row33

Top50 - row 33

Author: prmerger-automator[bot]

articles/iot-edge/module-development.md

@@ -4,7 +4,7 @@ description: Develop custom modules for Azure IoT Edge that can communicate with
 author: PatAltimore
 
 ms.author: patricka
-ms.date: 06/10/2024
+ms.date: 05/16/2025
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -48,18 +48,18 @@ When writing a module, you can connect to the IoT Edge hub and use IoT Hub primi
 
 #### Device-to-cloud messages
 
-An IoT Edge module can send messages to the cloud via the IoT Edge hub that acts as a local broker and propagates messages to the cloud. To enable complex processing of device-to-cloud messages, an IoT Edge module can intercept and process messages sent by other modules or devices to its local IoT Edge hub. The IoT Edge module will then send new messages with processed data. Chains of IoT Edge modules can thus be created to build local processing pipelines.
+An IoT Edge module can send messages to the cloud via the IoT Edge hub that acts as a local broker and propagates messages to the cloud. To enable complex processing of device-to-cloud messages, an IoT Edge module can intercept and process messages sent by other modules or devices to its local IoT Edge hub. The IoT Edge module then sends new messages with processed data. Chains of IoT Edge modules can thus be created to build local processing pipelines.
 
 To send device-to-cloud telemetry messages using routes:
 
-* Use the Module Client class of the [Azure IoT SDK](https://github.com/Azure/azure-iot-sdks). Each module has *input* and *output* endpoints. 
-* Use a send message method from your Module Client class to send messages on the output endpoint of your module. 
-* Set up a route in the edgeHub module of your device to send this output endpoint to IoT Hub.
+* Use the ModuleClient class of the [Azure IoT SDK](https://github.com/Azure/azure-iot-sdks). Each module has *input* and *output* endpoints. 
+* To send messages on the output endpoint of your module, use a send message method from your ModuleClient class. 
+* To send this output endpoint to IoT Hub, set up a route in the edgeHub module of your device.
 
 To process messages using routes:
 
 * Set up a route to send messages coming from another endpoint (module or device) to the input endpoint of your module.
-* Listen for messages on the input endpoint of your module. Each time a new message comes back, a callback function is triggered by the Azure IoT SDK. 
+* Listen for messages on the input endpoint of your module. Each time a new message comes back, the Azure IoT SDK triggers a callback function. 
 * Process your message with this callback function and (optionally) send new messages in your module endpoint queue.
 
 >[!NOTE]
@@ -83,7 +83,7 @@ IoT Edge supports multiple operating systems, device architectures, and developm
 
 ### Linux
 
-For all languages in the following table, IoT Edge [supports](support.md) development for AMD64 and most ARM64 Linux containers. There is support for Debian 11 ARM32 containers, as well.
+For all languages in the following table, IoT Edge [supports](support.md) development for AMD64 and most ARM64 Linux containers. There's support for Debian 11 ARM32 containers, as well.
 
 | Development language | Development tools |
 | -------------------- | ----------------- |
@@ -94,21 +94,21 @@ For all languages in the following table, IoT Edge [supports](support.md) develo
 | Python | Visual Studio Code |
 
 >[!NOTE]
->For cross-platform compilation, like compiling an ARM32 IoT Edge module on an AMD64 development machine, you need to configure the development machine to compile code on target device architecture matching the IoT Edge module. For more information about target device architectures, see [Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md).
+>For cross-platform compilation, like compiling an ARM32 IoT Edge module on an AMD64 development machine, you need to configure the development machine to compile code on target device architecture matching the IoT Edge module. For more information about target device architectures, see [Tutorial: Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md).
 
 ### Windows
 
 We no longer support Windows containers. [IoT Edge for Linux on Windows](iot-edge-for-linux-on-windows.md) is the recommended way to run IoT Edge on Windows devices.
 
 ## Module security
 
-You should develop your modules with security in mind. To learn more about securing your modules, see [Docker security](https://docs.docker.com/engine/security/).
+You should develop your modules with security in mind. To learn more about securing your modules, see [Docker Engine security](https://docs.docker.com/engine/security/).
 
 To help improve module security, IoT Edge disables some container features by default. You can override the defaults to provide privileged capabilities to your modules if necessary.
 
 ### Allow elevated Docker permissions
 
-In the config file on an IoT Edge device, there's a parameter called `allow_elevated_docker_permissions`. When set to **true**, this flag allows the `--privileged` flag and any additional capabilities that you define in the `CapAdd` field of the Docker HostConfig in the [container create options](how-to-use-create-options.md). 
+In the config file on an IoT Edge device, there's a parameter called `allow_elevated_docker_permissions`. When set to **true**, this flag allows the `--privileged` flag and any other capabilities that you define in the `CapAdd` field of the Docker HostConfig in the [container create options](how-to-use-create-options.md). 
 
 > [!NOTE]
 > Currently, this flag is true by default, which allows deployments to grant privileged permissions to modules. We recommend that you set this flag to false to improve device security.
@@ -123,8 +123,8 @@ If you need these capabilities, you can manually re-enable them using CapADD in
 
 [Prepare your development and test environment for IoT Edge](development-environment.md)
 
-[Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md)
+[Tutorial: Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md)
 
 [Debug Azure IoT Edge modules using Visual Studio Code](debug-module-vs-code.md)
 
-[Understand and use Azure IoT Hub SDKs](../iot-hub/iot-hub-devguide-sdks.md)
+[Azure IoT Hub SDKs](../iot-hub/iot-hub-devguide-sdks.md)