few changes

Author: rayne-wiselman

articles/migrate/how-to-migrate-at-scale.md

@@ -56,7 +56,7 @@ Once the CSV is ready, you can execute the following steps to perform migration
 6 | asr_cleanuptestmigration.ps1 | Once you manually validate the VMs that were test failed-over, you can use this script to clean up the test failover VMs
 7 | asr_migration.ps1 | Perform an unplanned failover for the VMs listed in the csv, the script creates a CSV output with the job details for each VM. The script does not shut down the on premises VMs before triggering the failover, for application consistency, it is recommended that you manually shut down the VMs before executing the script.
 8 | asr_completemigration.ps1 | Perform the commit operation on the VMs and delete the Azure Site Recovery entities
-9 | asr_postmigration.ps1 | If you plan to assign network security groups to the NICs post-failover, you can use this script to do that. It assigns a NSG to any one NIC in the target VM.
+9 | asr_postmigration.ps1 | If you plan to assign network security groups to the NICs post-failover, you can use this script to do that. It assigns an NSG to any one NIC in the target VM.
 
 ## How to migrate to managed disks?
 The script, by default, migrates the VMs to managed disks in Azure. If the target storage account provided is a premium storage account, premium-managed disks are created post migration. The cache storage account can still be a standard account. If the target storage account is a standard storage account, standard disks are created post migration. 

articles/migrate/media/migrate-appliance/architecture.png

@@ -187,12 +187,16 @@ The appliance communicates with vCenter Servers and Hyper-V hosts/cluster using
 4. **Assess and migrate**: You can now create assessments from the metadata collected by the appliance using Azure Migrate Server Assessment. In addition, you can also start migrating VMware VMs using Azure Migrate Server Migration to orchestrate agentless VM replication.
 
 
+![Architecture](./media/migrate-appliance/architecture.png)
+
+
 ## Appliance upgrades
 
 The appliance is upgraded as the Azure Migrate agents running on the appliance are updated.
 
 - This happens automatically because the auto-update is enabled on the appliance by default.
-- You can change this default setting to update the agents manually. 
+- You can change this default setting to update the agents manually.
+- To disable automatic updates, set registry key Appliance Auto Update, in HKLM\SOFTWAREMicrosoft\Azure.
 
 ### Set agent updates to manual
 

articles/migrate/media/migrate-replication-appliance/architecture.png

@@ -9,11 +9,11 @@ ms.author: raynew
 ---
 
 
-# Azure Migrate replication appliance
+# Replication appliance
 
-This article describes the Azure Migrate replication appliance. You deploy the replication appliance when you use the Azure Migrate Server Migration tool to migrate apps, infrastructure, and workloads to Microsoft Azure.
+This article describes the replication appliance used by Azure Migrate: Server Assessment when migrating VMware VMs, physical machines, and private/public cloud VMs to Azure, using an agent-based migration. 
 
-The tool is available in The [Azure Migrate](migrate-overview.md) hub. The hub provides native tools for assessment and migration, as well as tools from other Azure services, and from third-party independent software vendors (ISVs).
+The tool is available in the [Azure Migrate](migrate-overview.md) hub. The hub provides native tools for assessment and migration, as well as tools from other Azure services, and from third-party independent software vendors (ISVs).
 
 
 ## Appliance overview
@@ -22,7 +22,7 @@ The replication appliance is deployed as a single on-premises machine, either as
 - **Replication appliance**: The replication appliance coordinates communications, and manages data replication, for on-premises VMware VMs and physical servers replicating to Azure.
 - **Process server**: The process server, which is installed by default on the replication appliance, and does the following:
     - **Replication gateway**: It acts as a replication gateway. It receives replication data from machines enabled for replication. It optimizes replication data with caching, compression, and encryption, and sends it to Azure.
-    - **Agent installer**: Performs a push installation of the Site Recovery Mobility Service. This service must be installed and running on each on-premises machine that you want to replicate for migration.
+    - **Agent installer**: Performs a push installation of the Mobility Service. This service must be installed and running on each on-premises machine that you want to replicate for migration.
 
 ## Appliance deployment
 
@@ -50,8 +50,9 @@ The appliance comes with a Windows Server 2016 evaluation license, which is vali
     - The replication appliance orchestrates replication with Azure over port HTTPS 443 outbound.
     - VMs send replication data to the process server (running on the replication appliance) on port HTTPS 9443 inbound. This port can be modified.
     - The process server receives replication data, optimizes and encrypts it, and sends it to Azure storage over port 443 outbound.
-5. The replication data logs first land in a cache storage account in Azure. These logs are processed and the data is stored in an Azure managed disk (**asr seed disk**).
+5. The replication data logs first land in a cache storage account in Azure. These logs are processed and the data is stored in an Azure managed disk.
 
+![Architecture](./media/migrate-replication-appliance/architecture.png)
 
 ## Appliance upgrades
 

articles/migrate/migrate-appliance.md

@@ -48,7 +48,7 @@ Device42 | Assess
 
 Azure Migrate Server Assessment discovers and assesses on-premises VMware VMs and Hyper-V VMs for migration to Azure. It uses a lightweight appliance that you deploy on-premises, and register with the Azure Migrate service. The appliance connects to Azure Migrate Server Assessment, and continually sends metadata and performance-related data to Azure Migrate.
 - Discovery is agentless. Nothing needs to be installed on the VMs you're discovering.
-- Collected data includes VM metadata, and performance data. [Learn more](migrate-appliance.md#collected-data).
+- Collected data includes VM metadata, and performance data. Learn more about data collected for [VMware](migrate-appliance.md#collected-performance-data-vmware) and [Hyper-V](migrate-appliance.md#collected-performance-data-hyper-v).
 
 After machines are discovered, in the Azure portal you gather them into groups that typically consist of VMs that you'd like to migrate together, and then run an assessment for a group. You can then analyze the assessment to figure out your migration strategy.