minor edits

Author: habibaum

articles/migrate/migrate-appliance.md

@@ -223,7 +223,7 @@ The appliance communicates with the discovery sources using the following proces
 
 **Process** | **VMware appliance** | **Hyper-V appliance** | **Physical appliance**
 ---|---|---|---
-**Start discovery** | The appliance communicates with the vCenter server on TCP port 443 by default. If the vCenter server listens on a different port, you can configure it in the appliance configuration manager. | The appliance communicates with the Hyper-V hosts on WinRM port 5986 (HTTPS) by default. <br/> If the https prerequisites aren't configured on the target Hyper-V servers, the communication would fall back to WinRM port 5985 (HTTP). <br/> To enforce https communication without fallback, enable the https protocol toggle in Appliance Config Manager. <br/> <br/> **Prerequisites** <br/> After enabling the checkbox, ensure that the prerequisites are configured on the target servers. <br/> - If certificates aren't configured on the target servers, discovery would fail on both current and newly added servers. <br/>  - WinRM HTTPS requires a local computer Server Authentication certificate with a CN matching the hostname to be installed. The certificate mustn't be expired, revoked, or self-signed. Refer to this [article](/troubleshoot/windows-client/system-management-components/configure-winrm-for-https) for configuring WINRM for HTTPS. |The appliance communicates with Windows servers over WinRM port 5986 (HTTPS) by default and with Linux servers over port 22 (TCP). <br/> If the https prerequisites aren't configured on the target Hyper-V servers, appliance communication would fall back to WinRM port 5985 (HTTP). <br/> To enforce https communication without fallback, enable the https protocol toggle in Appliance Config Manager. <br/> <br/> **Prerequisites** <br/> After enabling the checkbox, ensure that the pre-requisites are configured on the target servers. <br/> - If certificates aren't configured on the target servers, discovery would fail on the current discovered servers and on the newly added servers. <br/> - WinRM HTTPS requires a local computer Server Authentication certificate with a CN matching the hostname to be installed. The certificate mustn't be expired, revoked, or self-signed. Refer to this [article](/troubleshoot/windows-client/system-management-components/configure-winrm-for-https) for configuring WINRM for HTTPS.
+**Start discovery** | The appliance communicates with the vCenter server on TCP port 443 by default. If the vCenter server listens on a different port, you can configure it in the appliance configuration manager. | The appliance communicates with the Hyper-V hosts on WinRM port 5986 (HTTPS) by default. <br/> If the https prerequisites aren't configured on the target Hyper-V servers, the communication would fall back to WinRM port 5985 (HTTP). <br/> To enforce https communication without fallback, enable the https protocol toggle in Appliance Config Manager. <br/> <br/> **Prerequisites** <br/> After enabling the checkbox, ensure that the prerequisites are configured on the target servers. <br/> - If certificates aren't configured on the target servers, discovery would fail on the current discovered servers and on the newly added servers. <br/>  - WinRM HTTPS requires a local computer Server Authentication certificate with a CN matching the hostname to be installed. The certificate mustn't be expired, revoked, or self-signed. Refer to this [article](/troubleshoot/windows-client/system-management-components/configure-winrm-for-https) for configuring WINRM for HTTPS. |The appliance communicates with Windows servers over WinRM port 5986 (HTTPS) by default and with Linux servers over port 22 (TCP). <br/> If the https prerequisites aren't configured on the target Hyper-V servers, appliance communication would fall back to WinRM port 5985 (HTTP). <br/> To enforce https communication without fallback, enable the https protocol toggle in Appliance Config Manager. <br/> <br/> **Prerequisites** <br/> After enabling the checkbox, ensure that the pre-requisites are configured on the target servers. <br/> -If certificates aren't configured on the target servers, discovery would fail on the current discovered servers and on the newly added servers. <br/> - WinRM HTTPS requires a local computer Server Authentication certificate with a CN matching the hostname to be installed. The certificate mustn't be expired, revoked, or self-signed. Refer to this [article](/troubleshoot/windows-client/system-management-components/configure-winrm-for-https) for configuring WINRM for HTTPS.
 **Gather configuration and performance metadata** | The appliance collects the metadata of servers running on vCenter Server(s) using vSphere APIs by connecting on port 443 (default port) or any other port each vCenter Server listens on. | The appliance collects the metadata of servers running on Hyper-V hosts using a Common Information Model (CIM) session with hosts on port 5986.| The appliance collects metadata from Windows servers using Common Information Model (CIM) session with servers on port 5986 and from Linux servers using SSH connectivity on port 22.
 **Send discovery data** | The appliance sends the collected data to Azure Migrate: Discovery and assessment and Migration and modernization over SSL port 443.<br/><br/>  The appliance can connect to Azure over the internet or via ExpressRoute private peering or Microsoft peering circuits. | The appliance sends the collected data to Azure Migrate: Discovery and assessment over SSL port 443.<br/><br/> The appliance can connect to Azure over the internet or via ExpressRoute private peering or Microsoft peering circuits. | The appliance sends the collected data to Azure Migrate: Discovery and assessment over SSL port 443.<br/><br/> The appliance can connect to Azure over the internet or via ExpressRoute private peering or Microsoft peering circuits. 
 **Data collection frequency** | Configuration metadata is collected and sent every 15 minutes. <br/><br/> Performance metadata is collected every 50 minutes to send a data point to Azure. <br/><br/> Software inventory data is sent to Azure once every 24 hours. <br/><br/> Agentless dependency data is collected every 5 minutes, aggregated on appliance and sent to Azure every 6 hours. <br/><br/> The SQL Server configuration data is updated once every 24 hours and the performance data is captured every 30 seconds. <br/><br/> The web apps configuration data is updated once every 24 hours. Performance data is not captured for web apps.| Configuration metadata is collected and sent every 30 minutes. <br/><br/> Performance metadata is collected every 30 seconds and is aggregated to send a data point to Azure every 15 minutes.<br/><br/> Software inventory data is sent to Azure once every 24 hours. <br/><br/> Agentless dependency data is collected every 5 minutes, aggregated on appliance and sent to Azure every 6 hours.<br/><br/> The SQL Server configuration data is updated once every 24 hours and the performance data is captured every 30 seconds.|  Configuration metadata is collected and sent every 3 hours. <br/><br/> Performance metadata is collected every 5 minutes to send a data point to Azure.<br/><br/> Software inventory data is sent to Azure once every 24 hours. <br/><br/> Agentless dependency data is collected every 5 minutes, aggregated on appliance and sent to Azure every 6 hours.<br/><br/> The SQL Server configuration data is updated once every 24 hours and the performance data is captured every 30 seconds.