Skip to content

Commit b95836f

Browse files
authored
Merge pull request #207849 from andrewbrownmsft/andbrown081222
Edits to import section for clarity
2 parents 1f91853 + e29bb78 commit b95836f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,10 +97,10 @@ deployment. If there are no updates in progress, the status is returned as “Id
9797
### Importing
9898

9999
Importing is how your updates are ingested into Device Update so they can be deployed to devices. Device Update supports rolling out a single update per device. This makes it ideal for
100-
full-image updates that update an entire OS partition at once, or an [APT manifest](device-update-apt-manifest.md)] that describes all the packages you want to update
100+
full-image updates that update an entire OS partition at once, or an [APT manifest](device-update-apt-manifest.md) that describes all the packages you want to update
101101
on your device from a designated repository. To import updates into Device Update, you first create an import manifest
102102
describing the update, then upload the update file(s) and the import
103-
manifest to an Internet-accessible location. After that, you can use the Azure portal or the [Device Update
103+
manifest to an Azure Storage container. After that, you can use the Azure portal or the [Device Update
104104
REST API](/rest/api/deviceupdate/) to initiate the asynchronous process of update import. Device Update uploads the files, processes
105105
them, and makes them available for distribution to IoT devices.
106106

0 commit comments

Comments
 (0)