Update common-questions-appliance.md

Author: rayne-wiselman

articles/migrate/common-questions-appliance.md

@@ -7,35 +7,40 @@ ms.date: 02/17/2020
 
 # Azure Migrate appliance: Common questions
 
-This article answers common questions about the Azure Migrate appliance. If you have further queries after reading this article, post them on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). If you have other questions, review these articles:
+This article answers common questions about the Azure Migrate appliance. If you have other questions, review these articles:
 
 - [General questions](resources-faq.md) about Azure Migrate.
 - [Questions](common-questions-discovery-assessment.md) about the discovery, assessment, and dependency visualization.
 - [Questions](common-questions-server-migration.md) about server migration.
+- Get questions answered on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). 
 
 
 ## What is the Azure Migrate appliance?
 
-The Azure Migrate appliance is a lightweight appliance used by the Azure Migrate: Server Assessment tool to discover and assess on-premises servers, and used by the Azure Migrate: Server Migration tool for agentless migration of on-premises VMware VMs. 
+The Azure Migrate appliance is a lightweight appliance used by the Azure Migrate:Server Assessment tool to discover and assess on-premises servers. The appliance is also used by the Azure Migrate:Server Migration tool, for agentless migration of on-premises VMware VMs. 
 
-The appliance is deployed on-premises as a VM or physical machine. The appliance discovers on-premises machines, and continually sends machine metadata and performance data to Azure Migrate. Appliance discovery is agentless. Nothing is installed on discovered machines. [Learn more](migrate-appliance.md) about the appliance.
+- The appliance is deployed on-premises as a VM or physical machine.
+- The appliance discovers on-premises machines, and continually sends machine metadata and performance data to Azure Migrate.
+- Appliance discovery is agentless. Nothing is installed on discovered machines.
+
+[Learn more](migrate-appliance.md) about the appliance.
 
 ## How does the appliance connect to Azure?
 
-The connection can be over the internet, or use Azure ExpressRoute with public/Microsoft peering.
+The appliance can connect over the internet, or using Azure ExpressRoute with public/Microsoft peering.
 
 ## Does appliance analysis impact performance?
 
-The Azure Migrate appliance profiles on-premises machines continuously to measure VM performance data. This profiling has almost no performance impact on the Hyper-V/ESXi hosts or on VMware vCenter Server.
+The Azure Migrate appliance profiles on-premises machines continuously to measure performance data. This profiling has almost no performance impact profiled machines.
 
 ### Can I harden the appliance VM?
 
-When you create the appliance VM using the downloaded template, you can add components (for example an antivirus) to the template, as long as you leave the communication and firewall rules required for the Azure Migrate appliance as-is.
+When you create the appliance VM using the downloaded template, you can add components (for example an antivirus) to the template, as long as you leave the communication and firewall rules required for the Azure Migrate appliance in place.
 
 
 ## What network connectivity is needed?
 
-Review the following:
+Review information about network connectivity:
 - VMware assessment using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-vmware.md#port-access) access requirements.
 - VMware agentless migration using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-vmware-migration.md#agentless-ports) access requirements.
 - Hyper-V assessment using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-hyper-v.md#port-access) access requirements.
@@ -51,14 +56,14 @@ Review the collected data:
 
 ## How is data stored?
 
-Data collected by the Azure Migrate appliance is stored in the Azure location that you choose when you created the migration project. 
+Data collected by the Azure Migrate appliance is stored in the Azure location in which you created the Azure Migrate project. 
 
 - The data is securely stored in a Microsoft subscription, and is deleted when you delete the Azure Migrate project.
 - If you use [dependency visualization](concepts-dependency-visualization.md), the data collected is stored in the United States, in a Log Analytics workspace created in the Azure subscription. This data is deleted when you delete the Log Analytics workspace in your subscription.
 
 ## How much data is uploaded in continuous profiling?
 
-The volume of data sent to Azure Migrate depends on a number of parameters. To give you a sense of the volume, an Azure Migrate project with 10 machines (each with one disk and one NIC) sends around 50 MB per day. This value is approximate, and changes based on the number of data points for the NICs and disks. The increase in data sent is non-linear if there's an increase in the number of machines, NICs, or disks.
+The volume of data sent to Azure Migrate depends on a number of parameters. To give you a sense, an Azure Migrate project with 10 machines (each with one disk and one NIC) sends around 50 MB per day. This value is approximate, and changes, based on the number of data points for the NICs and disks. The increase in data sent is non-linear if there's an increase in the number of machines, NICs, or disks.
 
 ## Is data encrypted at-rest/in-transit?
 
@@ -79,31 +84,31 @@ Yes, for both.
 
 No. There's a one-to-one mapping between an appliance and vCenter Server. To discover VMs on multiple vCenter Server instances, you need to deploy multiple appliances.
 
-### How many VMs or servers can I discover with an appliance?
+## How many VMs or servers can I discover with an appliance?
 
-You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs and up to 250 servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
+You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs, and up to 250 physical servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
 
 ## Can I delete an appliance?
 
-Currently deletion of appliance from the project isn't supported.
+Currently, deleting an appliance from the project isn't supported.
 
 - The only way to delete the appliance is to delete the resource group that contains the Azure Migrate project associated with the appliance.
 - However, deleting the resource group will also delete other registered appliances, the discovered inventory, assessments, and all other Azure components associated with the project in the resource group.
 
 
 ## Can I use the appliance with a different subscription/project?
 
-After using the appliance to initiate discovery, you can't reconfigure it with a different Azure subscription, or in a different Azure Migrate project. You also can't discover VMs on a different vCenter Server. Set up a fresh appliance for these tasks.
+After using the appliance to initiate discovery, you can't reconfigure it with a different Azure subscription, or use it in a different Azure Migrate project. You also can't discover VMs on a different vCenter Server. Set up a new appliance for these tasks.
 
 ## Can I set up the appliance on an Azure VM?
-Not currently supported. 
+No. This isn't currently supported. 
 
 ## Can I discover on an ESXi host?
-Not you need a vCenter Server to discover VMware VMs.
+No. You need a vCenter Server to discover VMware VMs.
 
 ## How do I update the appliance?
 
-By default, the appliance and its installed agents are updated automatically. The appliance checks for updates once every 24 hours. If there are any failures during the update process, there's a retry process. Automatic updates only update the appliance and appliance agents. The operating system isn't updated. Use Microsoft Updates to keep the operating system up-to-date.
+By default, the appliance and its installed agents are updated automatically. The appliance checks for updates once every 24 hours. If the update process fails, there's a retry. Automatic updates only update the appliance and appliance agents. The operating system isn't updated. Use Microsoft Updates to keep the operating system up-to-date.
 
 ## Can I check agent health?