Learn Editor: Update about-move-process.md

Author: ankitaduttaMSFT

articles/resource-mover/about-move-process.md

@@ -32,18 +32,18 @@ These components are used during region move.
 
 ![Diagram showing the move steps](./media/about-move-process/move-steps.png)
 
+
 Each move resource goes through the summarized steps.
 
 | **Step** | **Details** | **State/Issues** |
 | --- | --- | --- |
 | **Step 1: Select resources** | Select a resource. The resource is added to the move collection. | Resource state moves to *Prepare pending*. |
-| **Step 2: Validate dependencies** | Validation of the dependencies is carried out along with addition of resources in the background. <br/><br/> You must add dependent resources if validation shows that dependent resources are pending. <br><br> Add them to the move collection. <br/><br/> Add all dependent resources, even if you don't want to move them. You can later specify that the resources you're moving should use different resources in the target region instead of using the **Configuration** option.<br/><br/> You may need to manually validate if there are outstanding dependencies in the **Validate dependencies** tab. |
+| **Step 2: Validate dependencies** | Validation of the dependencies is carried out along with addition of resources in the background. <br/><br/> You must add dependent resources if validation shows that dependent resources are pending. <br><br> Add them to the move collection. <br/><br/> Add all dependent resources, even if you don't want to move them. You can later specify that the resources you're moving should use different resources in the target region instead of using the **Configuration** option.<br/><br/> You may need to manually validate if there are outstanding dependencies in the **Validate dependencies** tab. ||
 | **Step 3: Prepare** | Kick off the prepare process. Preparation steps depend on the resources you're moving:<br/><br/> - **Stateless resources**: Stateless resources have configuration information only. These resources don't need continuous replication of data in order to move them. Examples include Azure virtual networks (VNets), network adapters, load balancers, and network security groups. For this type of resource, the Prepare process generates an Azure Resource Manager template.<br/><br/> - **Stateful resources**: Stateful resources have both configuration information, and data that needs to be moved. Examples include Azure VMs, and Azure SQL databases. The Prepare process differs for each resource. It might include replicating the source resource to the target region. | Kicking off moves resource state to *Prepare in progress*.<br/><br/> After prepare finishes, resource state moves to *Initiate move pending*, with no issues.<br/><br/> An unsuccessful process moves state to *Prepare failed*. |
 | **Step 4: Initiate move** | Kick off the move process. The move method depends on the resource type:<br/><br/> - **Stateless**: Typically, for stateless resources, the move process deploys an imported template in the target region. The template is based on the source resource settings, and any manual edits you make to target settings.<br/><br/> - **Stateful**: For stateful resources, the move process might involve creating the resource, or enabling a copy, in the target region.<br/><br/>  For stateful resources only, initiating a move might result in downtime of source resources. For example, VMs and SQL. | Kicking off move shifts the state to *Initiate move in progress*.<br/><br/> A successful initiate move moves resource state to *Commit move pending*, with no issues. <br/><br/> An unsuccessful move process moves state to *Initiate move failed*. |
 | **Step 5 Option 1: Discard move** | After the initial move, you can decide whether you want to go ahead with a full move. If you don't, you can discard the move, and Resource Mover deletes the resources created in the target. The replication process for stateful resources continues after the Discard process. This option is useful for testing. | Discarding resources moves state to *Discard in progress*.<br/><br/> Successful discard moves state to *Initiate move pending*, with no issues.<br/><br/> A failed discard moves state to *Discard move failed*. |
 | **Step 5 Option 2: Commit move** | After the initial move, if you want to go ahead with a full move, you verify resources in the target region, and when you're ready, you commit the move.<br/><br/> For stateful resources only, commit can result in source resources like VMs or SQL becoming inaccessible. | If you commit the move, resource state moves to *Commit move in progress**.<br/><br/> After a successful commit, the resource state shows *Commit move completed*, with no issues.<br/><br/> A failed commit moves state to *Commit move failed*. |
-| **Step 6: Delete source** | After committing the move, and verifying resources in the target region, you can delete the source resource. | After committing, a resource state moves to *Delete source pending*. You can then select the source resource and delete it.<br/><br/> - Only resources in the *Delete source pending* state can be deleted. <br/><br/>Deleting a resource group or SQL Server in the Resource Mover portal isn't supported. These resources can only be deleted from the resource properties page. |
-
+| **Step 6: Delete source** | After committing the move, and verifying resources in the target region, you can delete the source resource. | After committing, a resource state moves to *Delete source pending*. You can then select the source resource and delete it.<br/><br/> Only resources in the *Delete source pending* state can be deleted. <br/><br/>Deleting a resource group or SQL Server in the Resource Mover portal isn't supported. These resources can only be deleted from the resource properties page. |
 
 ## Move region states
 
@@ -80,3 +80,4 @@ The table summarizes what's impacted when you're moving across regions.
 
 [Move](tutorial-move-region-virtual-machines.md) Azure VMs to another region.
 [Move](tutorial-move-region-sql.md) Azure SQL resources to another region.
+