Merge pull request #186953 from danewalton/dev-update

add link to import manifest

Author: PRMerger14

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

@@ -13,13 +13,15 @@ ms.service: iot-hub-device-update
 
 ## Overview
 
-Device Update for IoT Hub uses an _update manifest_ to communicate actions and also metadata supporting those actions through the
+Device Update for IoT Hub uses an _update manifest_ to communicate actions and metadata that supports those actions through the
  [AzureDeviceUpdateCore.OrchestratorMetadata:4](./device-update-plug-and-play.md)interface properties.
  This document describes the fundamentals of how the `updateManifest` property, in the
  `AzureDeviceUpdateCore.OrchestratorMetadata:4` interface, is used by the Device Update Agent. The
  `AzureDeviceUpdateCore.OrchestratorMetadata:4` interface properties are sent from the Device Update for IoT Hub service
  to the Device Update Agent. The `updateManifest` is a serialized JSON Object that is parsed by the Device Update Agent.
 
+The update manifest is auto generated after creation of an import manifest. For more information on how to generate an import manifest, [see here](./import-update.md).
+
 ### An example update manifest
 
 ```JSON
@@ -47,11 +49,11 @@ Device Update for IoT Hub uses an _update manifest_ to communicate actions and a
 
 The purpose of the update manifest is to describe the contents of an update, namely its identity, type,
 installed criteria, and update file metadata. In addition, the update manifest is cryptographically signed to
-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.
+allow the Device Update Agent to verify its authenticity. For more information, see the document on [Device Update security](./device-update-security.md).
 
 ## Import manifest vs update manifest
 
-It is important to understand the differences between the import manifest and the update manifest concepts in Device Update for IoT Hub. 
+It is important to understand the differences between the import manifest and the update manifest. 
 * The [import manifest](./import-concepts.md) is created by whoever creates the corresponding update. It describes the contents of the update that will be imported into Device Update for IoT Hub. 
 * The update manifest is automatically generated by the Device Update for IoT Hub service, using some of the properties that were defined in the import manifest. It is used to communicate relevant information to the Device Update Agent during the update process. 
 
@@ -70,7 +72,7 @@ to determine compatible devices for the update.
 
 ### updateType
 
-Represents the type of update which is handled by a specific type of update handler. It follows the form
+Represents the type of update that is handled by a specific type of update handler. It follows the form
 of `microsoft/swupdate:1` for an image-based update and `microsoft/apt:1` for a package-based update (see `Update Handler Types` section below).
 
 ### installedCriteria
@@ -81,7 +83,7 @@ for each update type supported by Device Update for IoT Hub.
 
 ### files
 
-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.
+Tells the Device Update Agent which files to download, and the hash that will be used to verify that the files downloaded correctly.
 Here's a closer look at the `files` property contents:
 
 ```json