Skip to content

Commit fb2f7d0

Browse files
acrolinx
1 parent c324df0 commit fb2f7d0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-hub-device-update/update-manifest.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ The update manifest is auto generated after creation of an import manifest. For
4949

5050
The purpose of the update manifest is to describe the contents of an update, namely its identity, type,
5151
installed criteria, and update file metadata. In addition, the update manifest is cryptographically signed to
52-
allow the Device Update Agent to verify its authenticity. Refer to the [Device Update security](./device-update-security.md) documentation for more information on how the update manifest is used to securely import content.
52+
allow the Device Update Agent to verify its authenticity. For more information, see the document on [Device Update security](./device-update-security.md).
5353

5454
## Import manifest vs update manifest
5555

@@ -83,7 +83,7 @@ for each update type supported by Device Update for IoT Hub.
8383

8484
### files
8585

86-
Tells the Device Update Agent which files to download, and the hash that will be used to use to verify the files were downloaded correctly.
86+
Tells the Device Update Agent which files to download, and the hash that will be used to use to verify that the files were downloaded correctly.
8787
Here's a closer look at the `files` property contents:
8888

8989
```json

0 commit comments

Comments
 (0)