Skip to content

Commit 5209ae6

Browse files
committed
edit pass: two-iot-hub-articles
1 parent 3252d27 commit 5209ae6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub/iot-hub-devguide-file-upload.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ The following reference topics provide you with more information about uploading
9090

9191
Optionally, when a device notifies IoT Hub that an upload is complete, IoT Hub generates a notification message. This message contains the name and storage location of the file.
9292

93-
As explained in [Endpoints](iot-hub-devguide-endpoints.md), IoT Hub delivers file upload notifications through a service-facing endpoint (**/messages/servicebound/fileuploadnotifications**) as messages. The receive semantics for file upload notifications are the same as for cloud-to-device messages and have the same [message lifecycle](iot-hub-devguide-messages-c2d.md#the-cloud-to-device-message-lifecycle). Each message retrieved from the file upload notification endpoint is a JSON record with the following properties:
93+
As explained in [Endpoints](iot-hub-devguide-endpoints.md), IoT Hub delivers file upload notifications through a service-facing endpoint (**/messages/servicebound/fileuploadnotifications**) as messages. The receive semantics for file upload notifications are the same as for cloud-to-device messages and have the same [message life cycle](iot-hub-devguide-messages-c2d.md#the-cloud-to-device-message-life-cycle). Each message retrieved from the file upload notification endpoint is a JSON record with the following properties:
9494

9595
| Property | Description |
9696
| --- | --- |

0 commit comments

Comments
 (0)