Addressed pre-review issues

Author: stevenmatthew

articles/storage-mover/includes/agent-shell-connect.md

@@ -18,7 +18,7 @@ ssh <AgentIpAddress> -l admin
 > [!IMPORTANT]
 > A newly deployed Storage Mover agent has a default password: </br>**Local user:** admin </br>**Default password:** admin
 
-You are prompted and strongly advised to change the default password immediately after you first connect to a newly deployed agent. Note down the new password, there is no process to recover it. Losing your password locks you out from the administrative shell. Cloud management does not require this local admin password. If the agent was previously registered, you can still use it for migration jobs. Agents are somewhat disposable. They hold little value beyond the current migration job they are executing. You can always deploy a new agent and use that instead to run the next migration job. 
+You're prompted and advised to change the default password immediately after you first connect to a newly deployed agent. Note down the new password, there's no process to recover it. Losing your password locks you out from the administrative shell. Cloud management doesn't require this local admin password. If the agent was previously registered, you can still use it for migration jobs. Agents are disposable. They hold little value beyond the current migration job they're executing. You can always deploy a new agent and use that instead to run the next migration job.
 
 > [!NOTE]
 > Losing the local account password during public preview precludes you from accessing your detailed copy logs.

articles/storage-mover/migration-basics.md

@@ -124,8 +124,8 @@ How your files are copied from source to target matters just as much as from whe
 
 There are two copy modes:
 
-|                                                     |               |
-|-----------------------------------------------------|---------------|
+| Copy mode                                           | Migration behavior |
+|-----------------------------------------------------|--------------------|
 |**Mirror**<br/>The target will look like the source. | *- Files in the target will be deleted if they don’t exist in the source.*<br/>*- Files and folders in the target will be updated to match the source.* |
 |**Merge**<br/>The target has more content than the source, and you keep adding to it.    | *- Files will be kept in the target, even if they don’t exist in the source.*<br/>*- Files with matching names and paths will be updated to match the source.*<br/>*- Folder renames between copies may lead to duplicate content in the target.*|
 

articles/storage-mover/storage-mover-create.md

@@ -41,7 +41,7 @@ To deploy a storage mover into a resource group, you must be a member of the *Co
 
 ### [Azure portal](#tab/portal)
 
-   1. Navigate to the **Create a resource** link in the [Azure Portal](https://portal.azure.com).
+   1. Navigate to the **Create a resource** link in the [Azure portal](https://portal.azure.com).
 
        :::image type="content" source="media/resource-create/portal-new-resource.png" alt-text="An image showing the Azure portal landing page with two indicators raising attention to the Create a resource links" lightbox="media/resource-create/portal-new-resource-large.png":::