Merge pull request #218706 from ankitaduttaMSFT/RM-typo-fixes

RM typo fixes

Author: v-ccolin

articles/resource-mover/common-questions.md

@@ -26,10 +26,10 @@ Currently, you can move resources from any source public region to any target pu
 
 Azure Resource Mover is currently available as follows:
 
-**Support** | **Details**
---- | ---
-Move support | Azure resources that are supported for move with Resource Mover can be moved from any public region to another public region and within regions in China. Moving resources within Azure Gov is also supported (US DoD Central, US DoD East, US Gov Arizona, US Gov Texas, US Gov Virginia).  US Sec East/West/West Central are not currently supported.
-Metadata support |  Supported regions for storing metadata about machines to be moved include East US2, North Europe, Southeast Asia, Japan East, UK South, and Australia East as metadata regions. <br/><br/> Moving resources within the Azure China region is also supported with the metadata region China North2.
+| Support | Details|
+|-------- | -------|
+|Move support | Azure resources that are supported for a move with Resource Mover can be moved from any public region to another public region and within regions in China. Moving resources within Azure Gov is also supported (US DoD Central, US DoD East, US Gov Arizona, US Gov Texas, US Gov Virginia).  US Sec East/West/West Central are not currently supported.|
+|Metadata support |  Supported regions for storing metadata about machines to be moved include East US2, North Europe, Southeast Asia, Japan East, UK South, and Australia East as metadata regions. <br/><br/> Moving resources within the Azure China region is also supported with the metadata region China North2.|
 
 ### What resources can I move across regions using Resource Mover?
 
@@ -50,7 +50,7 @@ You can't select disks as resources to the moved across regions. However, disks
 
 ### What does it mean to move a resource group?
 
-When a resource is selected for move, the corresponding resource group is added automatically for moving. This is so that the destination resource can be placed in a resource group. You can choose to customize and provide an existing resource group, after it's added for move. Moving a resource group doesn't mean that all the resources in the source resource group will be moved.
+When a resource is selected for move, the corresponding resource group is added automatically for moving. This is so that the destination resource can be placed in a resource group. You can choose to customize and provide an existing resource group after it's added for move. Moving a resource group doesn't mean that all the resources in the source resource group will be moved.
 
 ### Can I move resources across subscriptions when I move them across regions?
 
@@ -61,7 +61,7 @@ No. Resource Mover service doesn't store customer data, it only stores metadata
 
 ### Where is the metadata for moving across regions stored?
 
-It's stored in an [Azure Cosmos DB](../cosmos-db/database-encryption-at-rest.md) database, and in [Azure Blob storage](../storage/common/storage-service-encryption.md), in a Microsoft subscription. Currently metadata is stored in East US 2 and North Europe. We will expand this coverage to other regions. This doesn't restrict you from moving resources across any public regions.
+It's stored in an [Azure Cosmos DB](../cosmos-db/database-encryption-at-rest.md) database, and in [Azure Blob storage](../storage/common/storage-service-encryption.md), in a Microsoft subscription. Currently, metadata is stored in East US 2 and North Europe. We will expand this coverage to other regions. This doesn't restrict you from moving resources across any public region.
 
 ### Is the collected metadata encrypted?
 
@@ -92,23 +92,22 @@ When you add resources in the Resource Mover hub in the portal, permissions are
 
 ### What if I don't have permissions to assign role identity?
 
-There are a couple of reasons you might not have permissions.
+There are a couple of reasons you might not have permission.
 
-**Possible cause** | **Recommendation**
---- | ---
-You're not a *Contributor* and *User Access Administrator* (or *Owner*) when you add a resource for first time. | Use an account with *Contributor* and *User Access Administrator* (or *Owner*) permissions for the subscription.
-The Resource Mover managed identity doesn't have the required role. | Add the 'Contributor' and 'User Access administrator' roles.
-The Resource Mover managed identity was reset to *None*. | Reenable a system-assigned identity in the move collection settings > **Identity**. Alternatively, in **Add Resources**, add the resource again, which does the same thing.  
-The subscription was moved to a different tenant. | Disable and then enable managed identity for the move collection.
+|Possible cause | Recommendation|
+|-------------- | --------------|
+|You're not a *Contributor* and *User Access Administrator* (or *Owner*) when you add a resource for the first time. | Use an account with *Contributor* and *User Access Administrator* (or *Owner*) permissions for the subscription.|
+|The Resource Mover managed identity doesn't have the required role. | Add the 'Contributor' and 'User Access administrator' roles. |
+|The Resource Mover managed identity was reset to *None*. | Reenable a system-assigned identity in the move collection settings > **Identity**. Alternatively, in **Add Resources**, add the resource again, which does the same thing. |
+|The subscription was moved to a different tenant. | Disable and then enable managed identity for the move collection.|
 
 ### How can I do multiple moves together?
 
 Change the source/target combinations as needed using the change option in the portal.
 
 ### What happens when I remove a resource from a list of move resources?
 
-You can remove resources that you've added to move list. The exact remove behavior depends on the resource state. [Learn more](remove-move-resources.md#vm-resource-state-after-removing).
-
+You can remove resources that you've added to the move list. The exact remove behavior depends on the resource state. [Learn more](remove-move-resources.md#vm-resource-state-after-removing).
 
 
 ## Next steps

articles/resource-mover/overview.md

@@ -19,11 +19,11 @@ This article provides an overview of the Azure Resource Mover service. Resource
 You might move resources to different Azure regions to:
 
 - **Align to a region launch**: Move resources to a newly introduced Azure region that wasn't previously available.
-- **Align for services/features**: Move resources to take advantage of services or features that are available in a specific region.
+- **Align for services/features**: Move resources to take advantage of the services or features that are available in a specific region.
 - **Respond to business developments**: Move resources to a region in response to business changes, such as mergers or acquisitions.
 - **Align for proximity**: Move resources to a region local to your business.
 - **Meet data requirements**: Move resources to align with data residency requirements, or data classification needs.
-- **Respond to deployment requirements**: Move resources that were deployed in error, or move in response to capacity needs.
+- **Respond to deployment requirements**: Move resources that were deployed in error or move in response to capacity needs.
 - **Respond to decommissioning**: Move resources because a region is decommissioned.
 
 
@@ -34,30 +34,30 @@ Resource Mover provides:
 - A single hub for moving resources across regions.
 - Reduced move time and complexity. Everything you need is in a single location.
 - A simple and consistent experience for moving different types of Azure resources.
-- An easy way to identify dependencies across resources you want to move. This helps you to move related resources together, so that everything works as expected in the target region, after the move.
+- An easy way to identify dependencies across resources you want to move. This feature helps you to move related resources together so that everything works as expected in the target region after the move.
 - Automatic cleanup of resources in the source region, if you want to delete them after the move.
-- Testing. You can try out a move, and then discard it if you don't want to do a full move.
+- Testing. You can try out a move and then discard it if you don't want to do a full move.
 
 ## Move across regions
 
-To move resources across regions, you select the resources that you want to move. Resource Mover validates those resources, and resolves any dependencies they have on other resources. If there are dependencies, you have a couple of options:
+To move resources across regions, you select the resources that you want to move. Resource Mover validates those resources and resolves any dependencies they have on other resources. If there are dependencies, you have a couple of options:
 - Move the dependent resources to the target region.
-- Don't move the dependent resources, but use equivalent resources in the target region instead.
+- Don't move the dependent resources but use equivalent resources in the target region instead.
 
 After all dependencies are resolved, Resource Mover walks you through a simple move process.
 
 1. You kick off an initial move.
-2. After the initial move, you can decide whether to commit and complete the move, or to discard the move.
-3. After the move's done, you can decide whether you want to delete the resources in the source location.
+2. After the initial move, you can decide whether to commit and complete the move or discard the move.
+3. After the move is done you can decide whether you want to delete the resources in the source location.
 
-You can move resources across regions in the Resource Mover hub, or from within a resource group. [Learn more](select-move-tool.md)
+You can move resources across regions in the Resource Mover hub or from within a resource group. [Learn more](select-move-tool.md)
 
 ## What resources can I move across regions?
 
 Using Resource Mover, you can currently move the following resources across regions:
 
 - Azure VMs and associated disks
-- Encrypted Azure VMs and associated disks. This includes VMs with Azure disk encryption enabled, and Azure VMs using default server-side encryption (both with platform-managed keys and customer-managed keys)
+- Encrypted Azure VMs and associated disks. This includes VMs with Azure disk encryption enabled and Azure VMs using default server-side encryption (both with platform-managed keys and customer-managed keys)
 - NICs
 - Availability sets 
 - Azure virtual networks 

articles/resource-mover/select-move-tool.md

@@ -15,19 +15,19 @@ ms.custom: mvc
 
 You can move resources within Azure as follows:
 
-- **Move resources across regions**: Move resource from within the Resource Mover hub, or within a resource group. 
+- **Move resources across regions**: Move resources from within the Resource Mover hub, or a resource group. 
 - **Move resources across resource groups/subscriptions**: Move from within a resource group. 
 - **Move resources between Azure clouds**: Use the Azure Site Recovery service to move resources between public and government clouds.
 - **Move resources between availability zones in the same region**: Use the Azure Site Recovery service to move resources between availability zones in the same Azure region.
 
 
 ## Compare move tools
 
-**Tool** | **When to use** | **Learn more**
---- | --- | ---
-**Move within resource group** | Move resources to a different resource group/subscription, or across regions.<br/><br/> If you move across regions, in the resource group you select the resources you want to move, and then you move to the Resource Mover hub, to verify dependencies and move the resources to the target region. | [Move resources to another resource group/subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).<br/><br/> [Move resources to another region from a resource group](move-region-within-resource-group.md).
-**Move from the Resource Mover hub** | Move resources across regions. <br/><br/> You can move to a target region, or to a specific availability zone, or availability set, within the target region. | [Move resources across regions in the Resource Mover hub]().
-**Move VMs with Site Recovery** | Use for moving Azure VMs between government and public clouds.<br/><br/> Use if you want to move VMs between availability zones in the same region. |[Move resources between government/public clouds](../site-recovery/region-move-cross-geos.md), [Move resources to availability zones in the same region](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md).
+| Tool | When to use| Learn more |
+|----- | ---------- | ---------- |
+| **Move within resource group** | Move resources to a different resource group/subscription, or across regions.<br/><br/> If you move across regions, in the resource group you select the resources you want to move, and then you move to the Resource Mover hub, to verify dependencies and move the resources to the target region. | [Move resources to another resource group/subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).<br/><br/> [Move resources to another region from a resource group](move-region-within-resource-group.md). |
+| **Move from the Resource Mover hub** | Move resources across regions. <br/><br/> You can move to a target region, or to a specific availability zone, or availability set, within the target region. | [Move resources across regions in the Resource Mover hub](). |
+| **Move VMs with Site Recovery** | Use it for moving Azure VMs between government and public clouds.<br/><br/> Use if you want to move VMs between availability zones in the same region. |[Move resources between government/public clouds](../site-recovery/region-move-cross-geos.md), [Move resources to availability zones in the same region](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md).|
 
 ## Next steps