Update keyvault-moveregion.md

Author: itechedit

articles/key-vault/general/keyvault-moveregion.md

@@ -16,18 +16,17 @@ Customer intent: As a key vault administrator, I want to move my vault to anothe
 
 # Move an Azure key vault across regions
 
-Key Vault doesn't support a resource move operation that permits moving a key vault from one region to another. This article covers workarounds for organizations that have a business need to move a key vault to another region. Each workaround option has limitations. It is critical to understand the implications of these workarounds before you attempt to apply them in a production environment.
+Azure Key Vault doesn't support a resource move operation that permits moving a key vault from one region to another. This article covers workarounds for organizations that have a business need to move a key vault to another region. Each workaround option has limitations. It's critical to understand the implications of these workarounds before you attempt to apply them in a production environment.
 
 To move a key vault to another region, you create a key vault in that other region and then manually copy each individual secret from your existing key vault to the new key vault. You can do this by using either of the following two options.
 
 ## Design considerations
 
-* Key vault names are globally unique. You can't reuse a vault name.
-
-* You need to reconfigure access policies and network configuration settings in the new key vault.
+Before you begin, keep in mind the following concepts:
 
+* Key vault names are globally unique. You can't reuse a vault name.
+* You need to reconfigure your access policies and network configuration settings in the new key vault.
 * You need to reconfigure soft-delete and purge protection in the new key vault.
-
 * The backup and restore operation won't preserve your autorotation settings. You might need to reconfigure the settings.
 
 ## Option 1: Use the key vault backup and restore commands
@@ -38,8 +37,8 @@ Using the backup and restore commands has two limitations:
 
 * You can't back up a key vault in one geography and restore it into another geography. For more information, see [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/).
 
-* The backup command backs up all versions of each secret. If you have a secret with a large number (more than 10) of previous versions, the request might exceed the maximum allowed request size and the operation might fail.
+* The backup command backs up all versions of each secret. If you have a secret with a large number of previous versions (more than 10), the request size might exceed the allowed maximum and the operation might fail.
 
 ## Option 2: Manually download and upload the key vault secrets
 
-You can download certain secret types manually. For example, you can download certificates as a .pfx file. This option eliminates the geographical restrictions for some secret types, such as certificates. You can upload the .pfx files to any key vault in any region. The secrets are downloaded in a non-password protected format. You are responsible for securing your secrets during the move.
+You can download certain secret types manually. For example, you can download certificates as a PFX file. This option eliminates the geographical restrictions for some secret types, such as certificates. You can upload the PFX files to any key vault in any region. The secrets are downloaded in a non-password protected format. You are responsible for securing your secrets during the move.