Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into vnet-delegation-update

Author: asudbring

articles/azure-netapp-files/backup-introduction.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 08/09/2023
+ms.date: 08/23/2023
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -41,6 +41,7 @@ Azure NetApp Files backup is supported for the following regions:
 * Australia East
 * Australia Southeast
 * Brazil South
+* Canada Central
 * Canada East
 * East Asia
 * East US
@@ -49,7 +50,10 @@ Azure NetApp Files backup is supported for the following regions:
 * Germany West Central
 * Japan East
 * Japan West
+* Korea Central
+* North Central US
 * North Europe
+* Norway East
 * Qatar Central
 * South Africa North
 * South Central US

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

@@ -52,7 +52,7 @@ The [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5)
 * `--update-provider`, `--update-name`, and `--update-version`: These three parameters define the **updateId** object that is a unique identifier for each update.
 * `--compat`: The **compatibility** object is a set of name-value pairs that describe the properties of a device that this update is compatible with.
   * The same exact set of compatibility properties can't be used with more than one provider and name combination.
-* `--step`: The update handler on the device (for example, `microsoft/script:1`, `microsoft/swupdate:1`, or `microsoft/apt:1`) and its associated properties for this update.
+* `--step`: The update **handler** on the device (for example, `microsoft/script:1`, `microsoft/swupdate:1`, or `microsoft/apt:1`) and its associated **properties** for this update.
 * `--file`: The paths to your update file or files.
 
 For more information about these parameters, see [Import schema and API information](import-schema.md).
@@ -83,7 +83,7 @@ For handler properties, you may need to escape certain characters in your JSON.
 
 The `init` command supports advanced scenarios, including the [related files feature](related-files.md) that allows you to define the relationship between different update files. For more examples and a complete list of optional parameters, see [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5).
 
-Once you've created your import manifest and saved it as a JSON file, you're ready to [import your update](import-update.md).
+Once you've created your import manifest and saved it as a JSON file, you're ready to [import your update](import-update.md). If you are planning to use the Azure portal UI for importing, be sure to name your import manifest in the following format: "\<manifestname\>.importmanifest.json".
 
 ## Create an advanced Device Update import manifest for a proxy update