Merge pull request #300279 from DENKEN02MSFT/Top50_sonialopez_Row51

Top50 - row 51

Author: JillGrant615

articles/iot-hub/iot-hub-devguide-c2d-guidance.md

@@ -6,7 +6,7 @@ author: SoniaLopezBravo
 ms.author: sonialopez
 ms.service: azure-iot-hub
 ms.topic: concept-article
-ms.date: 01/29/2018
+ms.date: 05/22/2025
 ms.custom:  [amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device']
 ---
 
@@ -16,28 +16,28 @@ IoT Hub provides three options for device apps to expose functionality to a back
 
 * [Direct methods](iot-hub-devguide-direct-methods.md) for communications that require immediate confirmation of the result. Direct methods are often used for interactive control of devices such as turning on a fan.
 
-* [Twin's desired properties](iot-hub-devguide-device-twins.md) for long-running commands intended to put the device into a certain desired state. For example, set the telemetry send interval to 30 minutes.
+* [Device twin's desired properties](iot-hub-devguide-device-twins.md) for long-running commands intended to put the device into a certain desired state. For example, set the telemetry send interval to 30 minutes.
 
 * [Cloud-to-device messages](iot-hub-devguide-messages-c2d.md) for one-way notifications to the device app.
 
 To learn how [Azure IoT Plug and Play](../iot/overview-iot-plug-and-play.md) uses these options to control IoT Plug and Play devices, see [IoT Plug and Play service developer guide](../iot/concepts-developer-guide-service.md).
 
 [!INCLUDE [iot-hub-basic](../../includes/iot-hub-basic-whole.md)]
 
-Here is a detailed comparison of the various cloud-to-device communication options.
+Here's a detailed comparison of the various cloud-to-device communication options.
 
-| Categories | Direct methods | Twin's desired properties | Cloud-to-device messages |
+| Categories | Direct methods | Device twin's desired properties | Cloud-to-device messages |
 | ---------- | -------------- | ------------------------- | ------------------------ |
 | Scenario | Commands that require immediate confirmation, such as turning on a fan. | Long-running commands intended to put the device into a certain desired state. For example, set the telemetry send interval to 30 minutes. | One-way notifications to the device app. |
 | Data flow | Two-way. The device app can respond to the method right away. The solution back end receives the outcome contextually to the request. | One-way. The device app receives a notification with the property change. | One-way. The device app receives the message
-| Durability | Disconnected devices are not contacted. The solution back end is notified that the device is not connected. | Property values are preserved in the device twin. Device will read it at next reconnection. Property values are retrievable with the [IoT Hub query language](iot-hub-devguide-query-language.md). | Messages can be retained by IoT Hub for up to 48 hours. |
+| Durability | Disconnected devices aren't contacted. The solution back end is notified that the device isn't connected. | Property values are preserved in the device twin. Device will read it at next reconnection. Property values are retrievable with the [IoT Hub query language](iot-hub-devguide-query-language.md). | IoT Hub can retain messages for up to 48 hours. |
 | Targets | Single device using **deviceId**, or multiple devices using [jobs](iot-hub-devguide-jobs.md). | Single device using **deviceId**, or multiple devices using [jobs](iot-hub-devguide-jobs.md). | Single device by **deviceId**. |
-| Size | Maximum direct method payload size is 128 KB for the request and 128 KB for the response. | Maximum desired properties size is 32 KB. | Up to 64 KB messages. |
-| Frequency | High. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Medium. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). | Low. For more information, see [IoT Hub limits](iot-hub-devguide-quotas-throttling.md). |
+| Size | Maximum direct method payload size is 128 KB for the request and 128 KB for the response. | Maximum desired properties size is 32 KB. | Up to 64-KB messages. |
+| Frequency | High. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). | Medium. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). | Low. For more information, see [IoT Hub quotas and throttling](iot-hub-devguide-quotas-throttling.md). |
 | Protocol | Available using MQTT or AMQP. | Available using MQTT or AMQP. | Available on all protocols. Device must poll when using HTTPS. |
 
 Learn how to use direct methods, desired properties, and cloud-to-device messages in the following tutorials:
 
 * [Quickstart: Control a device connected to an IoT hub](quickstart-control-device.md)
-* [Use desired properties to configure devices](tutorial-device-twins.md) 
-* [Send cloud-to-device messages](c2d-messaging-node.md)
+* [Tutorial: Configure your devices from a back-end service](tutorial-device-twins.md) 
+* [Send and receive cloud-to-device messages](c2d-messaging-node.md)