acronlinx

Author: danewalton-msft

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

@@ -13,7 +13,7 @@ ms.service: iot-hub-device-update
 
 ## Overview
 
-Device Update for IoT Hub uses an _update manifest_ to communicate actions and metadata which supports 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
@@ -53,7 +53,7 @@ allow the Device Update Agent to verify its authenticity. For more information,
 
 ## 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.