Skip to content

Commit f7809a4

Browse files
committed
Fixed acrolinx item
1 parent d13bf0d commit f7809a4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub/c2d-messaging-howto.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ For a back end application to send cloud-to-device messages, it must connect to
4747

4848
To understand cloud-to-device messaging, it's important to understand some fundamentals about how IoT Hub device message queues work.
4949

50-
Cloud-to-device messages sent from a solution backend application to an IoT device are routed through IoT Hub. There is no direct peer-to-peer messaging communication between the solution backend application and the target device. IoT Hub places incoming messages into it's message queue, ready to be downloaded by target IoT devices.
50+
Cloud-to-device messages sent from a solution backend application to an IoT device are routed through IoT Hub. There's no direct peer-to-peer messaging communication between the solution backend application and the target device. IoT Hub places incoming messages into its message queue, ready to be downloaded by target IoT devices.
5151

5252
To guarantee at-least-once message delivery, IoT hub persists cloud-to-device messages in per-device queues. Devices must explicitly acknowledge completion of a message before IoT Hub removes the message from the queue. This approach guarantees resiliency against connectivity and device failures.
5353

0 commit comments

Comments
 (0)