touchups

Author: v-thepet

articles/iot-hub-device-update/import-concepts.md

@@ -190,7 +190,7 @@ The `files` section of the import manifest contains update payload file metadata
 
 ## Create an import manifest
 
-Once you understand the structure of an import manifest, create an import manifest to describe your update. You can author a JSON import manifest manually using a text editor, but the Azure CLI [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command simplifies the process. For more information and instructions, see [Prepare an update to import into Device Update](create-update.md).
+Once you understand the structure of an import manifest, create an import manifest file to describe your update. You can author a JSON import manifest file manually using a text editor, but the Azure CLI [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command simplifies the process. For more information and instructions, see [Prepare an update to import into Device Update](create-update.md).
 
 > [!IMPORTANT]
 > To import into the Azure portal, an import manifest JSON filename must end with *.importmanifest.json*.
@@ -204,6 +204,7 @@ Certain limits are enforced for Device Update instances, including import limits
 
 ## Related content
 
-- [Import manifest schema](import-schema.md).
-- [Prepare an update to import](create-update.md).
+- [Import manifest schema](import-schema.md)
+- [Device Update update manifest](update-manifest.md)
+- [Prepare an update to import](create-update.md)
 - [Import an update](import-update.md)

articles/iot-hub-device-update/import-schema.md

@@ -13,7 +13,7 @@ ms.subservice: device-update
 
 When you import an update into Azure Device Update for Iot Hub, you also submit an associated JSON import manifest file that defines important information about the update. This article describes the schema used to create the JSON import manifest file.
 
-To learn more about import manifest concepts and file structure, see [Azure Device Update for IoT Hub import manifest concepts](import-concepts.md). To learn how to create the file, see [Prepare an update to import into Device Update for IoT Hub](import-update.md).
+To learn more about import manifest concepts and file structure, see [Azure Device Update for IoT Hub import manifest](import-concepts.md). To learn how to create the file, see [Prepare an update to import into Device Update for IoT Hub](import-update.md).
 
 ## Schema
 
@@ -29,16 +29,16 @@ The import manifest JSON schema is hosted at [SchemaStore.org](https://json.sche
 |**instructions**|`instructions`|Update installation instructions.|Yes|
 |**files**|`file` `[0-10]`|List of update payload files. Sum of all file sizes can't exceed 2 GB. Can be empty or null if all instruction steps are reference steps.|No|
 |**manifestVersion**|`string`|Import manifest schema version. Must be 5.0.|Yes|
-|**createdDateTime**|`string`|Date and time import manifest was created in ISO 8601 format, for example `"2020-10-02T22:18:04.9446744Z"`.|Yes|
+|**createdDateTime**|`string`|Import manifest creation date and time in ISO 8601 format, for example `"2020-10-02T22:18:04.9446744Z"`.|Yes|
 
 ### Update object
 
 The `updateID` object is a unique identifier for each update.
 
 |Property|Type|Description|Required|
 |---|---|---|---|
-|**provider**|`string`|Entity who is creating or directly responsible for the update. It can be a company name.<br>Pattern: `^[a-zA-Z0-9.-]+$`<br>Maximum length: 64 characters|Yes|
-|**name**|`string`|Identifier for a class of update. It can be a device class or model name.<br>Pattern: `^[a-zA-Z0-9.-]+$`<br>Maximum length: 64 characters|Yes|
+|**provider**|`string`|Entity who is creating or directly responsible for the update, such as a company name.<br>Pattern: `^[a-zA-Z0-9.-]+$`<br>Maximum length: 64 characters|Yes|
+|**name**|`string`|Identifier for a class of update, such as a device class or model name.<br>Pattern: `^[a-zA-Z0-9.-]+$`<br>Maximum length: 64 characters|Yes|
 |**version**|`string`|Two- to four-part dot-separated numerical version numbers. Each part must be a number between 0 and 2147483647, and leading zeroes are dropped.<br>Pattern: `^\d+(?:\.\d+)+$`<br>Examples: `"1.0"`, `"2021.11.8"`|Yes|
 
 No other properties are allowed.
@@ -136,12 +136,12 @@ For example:
 
 #### Reference step object
 
-A `reference` step object is an installation instruction step that installs another update.
+A `reference` step object is an installation instruction step to install another update.
 
 |Property|Type|Description|Required|
 |---|---|---|---|
 |**type**|`referenceStepType`|Instruction step type that installs another update. Must be `reference`.|Yes|
-|**description**|`stepDescription`|Optional instruction step description. Maximum length: 64 characters |No|
+|**description**|`stepDescription`|Optional instruction step description. Maximum length: 64 characters. |No|
 |**updateId**|`updateId`|Unique update identifier.|Yes|
 
 No other properties are allowed.
@@ -249,7 +249,7 @@ The `downloadHandler` object specifies how to process any related files.
 
 |Property|Type|Description|Required|
 |---|---|---|---|
-|**id**|`string`|Identifier for `downloadHandler`. Limit of 64 ASCII characters.|Yes|
+|**id**|`string`|Identifier for `downloadHandler`. Limit of 64 ASCII characters.|Yes, if using `relatedFiles`|
 
 No other properties are allowed.
 

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

@@ -18,6 +18,11 @@ To deploy an update to devices using Azure Device Update for IoT Hub, you first
 - A [Device Update account and instance configured with an IoT hub](create-device-update-account.md).
 - An IoT device or simulator [provisioned for Device Update](device-update-agent-provisioning.md) within the IoT hub.
 - Update files for your device, and an associated import manifest file created by following the instructions in [Prepare an update to import into Device Update](create-update.md).
+- An Azure Storage account and container to hold the imported files. Or, you can create a new storage account and container as part of the Azure portal based import process.
+
+  > [!IMPORTANT]
+  > Make sure the storage account you use or create doesn't have private endpoints enabled. To see if private endpoints are enabled, you can check for your Azure Storage account name under **Private endpoints** in the [Private Link Center](https://portal.azure.com/#blade/Microsoft_Azure_Network/PrivateLinkCenterBlade/overview).
+
 ## Import an update
 
 This section shows how to import an update using either the Azure portal or the Azure CLI. You can also [import an update by using the Device Update APIs](#import-using-the-device-update-apis) instead.
@@ -38,9 +43,6 @@ To import an update, you first upload the update and import manifest files into
 
 1. On the **Storage accounts** page, select an existing storage account or create a new account by selecting **Storage account**. You use the storage account for a container to stage the update files.
 
-   > [!IMPORTANT]
-   > Make sure the storage account you use or create doesn't have private endpoints enabled. To see if private endpoints are enabled, you can check for your Azure Storage account name under **Private endpoints** in the [Private Link Center](https://portal.azure.com/#blade/Microsoft_Azure_Network/PrivateLinkCenterBlade/overview).
-
 1. On the **Containers** page, select an existing container or create a new container by selecting **Container**. You use the container to stage the update files for import.
 
    :::image type="content" source="media/import-update/storage-account-ppr.png" alt-text="Screenshot that shows Storage accounts and Containers.":::

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

@@ -21,7 +21,7 @@ Device Update uses [IoT Plug and Play](device-update-plug-and-play.md) to send t
 The update manifest is different from the Device Update *import manifest*.
 
 - The [import manifest](import-concepts.md) is a JSON file that describes the update to import into Device Update. Whoever creates the update for Device Update creates the corresponding import manifest file.
-- The update manifest is a JSON string object that communicates information to the Device Update agent during an update. The Device Update service automatically generates the update manifest by using some of the same properties defined in the import manifest.
+- The update manifest is a JSON string object that communicates information to the Device Update agent during an update. The Device Update service automatically generates the update manifest by including some of the same properties defined in the import manifest.
 
 Each manifest type has its own schema and schema version. For more information about the import manifest schema, see [Device Update import manifest schema](import-schema.md).