fixed blocing issues

Author: habibaum

articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md

@@ -83,7 +83,7 @@ The appliance collects the following performance data for compute settings:
 - The appliance collects a real-time sample point. For MySQL instances, it collects a sample point every 30 seconds.
 - The appliance aggregates the sample data points collected every 30 seconds over 10 minutes. To create the data point, the appliance selects the peak values from all samples. It sends the max and means for each counter to Azure.
 - Azure Migrate stores all the 10-minute data points for the last month.
-- When you create an assessment, Azure Migrate identifies the appropriate data point to use for right-sizing. Identification is based on the percentile values for performance history and percentile utilization.
+- When you create an assessment, Azure Migrate identifies the appropriate data point to use for right sizing. Identification is based on the percentile values for performance history and percentile utilization.
     - For example, if the performance history spans a week and the utilization is at 95th percentile, the assessment sorts the 10-minute sample points for the last week. It sorts them in ascending order and picks the 95th percentile value for right-sizing.
     - The 95th percentile value ensures you ignore any outliers, which might be included if you picked the 99th percentile.
     - If you want to pick the peak usage for the period and don't want to miss any outliers, select the 99th percentile for percentile utilization.
@@ -104,7 +104,7 @@ Readiness to migrate a MySQL instance to Azure Database for MySQL is determined
 
 An instance is then marked as:
 - **Ready**: If no major compatibility issues were found between source and target MySQL instances.
-- **Ready with conditions**: If there are non-critical compatibility issues such as degraded or unsupported features, that don't block the migration to Azure Database for MySQL. Azure Migrate displays the migration warnings with impact details and recommended remediation guidelines.
+- **Ready with conditions**: If there are non-critical compatibility issues such as degraded or unsupported features that don't block the migration to Azure Database for MySQL. Azure Migrate displays the migration warnings with impact details and recommended remediation guidelines.
 - **Not ready**: If there are any compatibility issues that may block the migration to Azure Database for MySQL. Azure Migrate displays the migration issues with impact details and recommended remediation guidance.
 - **Unknown**:  If the discovery is still in progress or there are any discovery issues in the source instance.
 

articles/migrate/concepts-assessment-overview.md

@@ -66,7 +66,7 @@ If you're using the appliance for discovery, it collects performance data using
 1. The assessment stores all the 10-minute data points for the last month. 
 
 1. The created assessment identifies the appropriate data point to use for rightsizing. Identification is based on the percentile value for *performance history* and *percentile utilization*. 
-    - For example,  If you selected performance history as one week and percentile utilization as 95th percentile while creating the assessments, all the data points are sorted in ascending order and the 95th percentile value is picked for right-sizing. 
+    - For example,  if you selected performance history as one week and percentile utilization as 95th percentile while creating the assessments, all the data points are sorted in ascending order and the 95th percentile value is picked for right-sizing. 
     - The 95th percentile value makes sure you ignore any outliers, which might be included if you picked the 99th percentile.  
     - If you want to consider all the outliers while calculating the assessments, select 99th percentile as percentile utilization. 
 

articles/migrate/vmware/migrate-support-matrix-vmware.md

@@ -342,7 +342,7 @@ Azure Government | Agent-based dependency analysis isn't supported.
 Requirement | Details
 --- | ---
 Project limits | You can create multiple Azure Migrate projects in an Azure subscription.<br /><br /> You can discover and assess up to 50,000 servers in a VMware environment in a single [project](../migrate-support-matrix.md#project). A project can include physical servers and servers from a Hyper-V environment, up to the assessment limits.
-Discovery | The Azure Migrate appliance can discover up to 10,000 servers running across multiple vCenter Servers.<br /><br /> The appliance supports adding multiple vCenter Servers. You can add up to 10 vCenter Servers per appliance.<br /><br />The scale is also valid to access discovered servers for Azure Migrate VMWare Solution (AVS).<br /><br />The same vCenter can be discovered by multiple appliances within the same project, but it is not recommended to have same VM discovered by multiple appliances. More details on how to set [discovery scope](./set-discovery-scope.md).
+Discovery | The Azure Migrate appliance can discover up to 10,000 servers running across multiple vCenter Servers.<br /><br /> The appliance supports adding multiple vCenter Servers. You can add up to 10 vCenter Servers per appliance.<br /><br />The scale is also valid to access discovered servers for Azure Migrate VMware Solution (AVS).<br /><br />The same vCenter can be discovered by multiple appliances within the same project, but it is not recommended to have same VM discovered by multiple appliances. More details on how to set [discovery scope](./set-discovery-scope.md).
 Assessment | You can add up to 35,000 servers in a single group.<br /><br /> You can assess up to 35,000 servers in a single assessment.
 
 Learn more about [assessments](../concepts-assessment-calculation.md).