minor edits

Author: habibaum

articles/migrate/assessment-properties.md

@@ -17,10 +17,10 @@ This article explains the assessment properties on the **General** tab that you
 |-------------------|---------|--------  |                                                     
 | **Target settings**   | **Target location**         | The Azure region to which you want to migrate. Azure target configuration and cost recommendations are based on the location that you specify. |
 | **Target settings**   | **Default Environment**      | The environment for the target deployments to apply pricing applicable to Production or Dev/Test. |
-| **Right-Sizing**      | **Sizing criteria**          | This attribute is used for right-sizing the target recommendations. <br> Use as-is on-premises sizing if you don't want to right-size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data. Use the storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
-| **Right-Sizing**              | **Performance history**      | Used with performance-based sizing. Performance history specifies the duration used when performance data is evaluated. |
-|  **Right-Sizing**               | **Percentile utilization**   | Used with performance-based sizing. Percentile utilization specifies the percentile value of the performance sample used for rightsizing. Learn more about [sampling mechanism](target-right-sizing.md). |
-|  **Right-Sizing**                 | **Comfort factor**           | This is the buffer applied during assessment. It's a multiplying factor used with performance metrics of CPU, RAM, disk, and network data for VMs. It accounts for issues like seasonal usage, short performance history, and likely increases in future usage. The comfort factor is applied irrespective of type of assessment (As-is on premises or performance based). For **performance-based** assessment, it's multiplied with utilization value of the resources, whereas for **As-is on premises** assessment it's multiplied by allocated resources. <br> The default values change. <br>  For example, a 10-core VM with 20% utilization normally results in a two-core VM. With a comfort factor of 2.0, the result is a four-core VM instead. |
+| **Right Sizing**      | **Sizing criteria**          | This attribute is used for right-sizing the target recommendations. <br> Use as-is on-premises sizing if you don't want to right-size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data. Use the storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
+| **Right Sizing**              | **Performance history**      | Used with performance-based sizing. Performance history specifies the duration used when performance data is evaluated. |
+|  **Right Sizing**               | **Percentile utilization**   | Used with performance-based sizing. Percentile utilization specifies the percentile value of the performance sample used for rightsizing. Learn more about [sampling mechanism](target-right-sizing.md). |
+|  **Right Sizing**                 | **Comfort factor**           | This is the buffer applied during assessment. It's a multiplying factor used with performance metrics of CPU, RAM, disk, and network data for VMs. It accounts for issues like seasonal usage, short performance history, and likely increases in future usage. The comfort factor is applied irrespective of type of assessment (As-is on premises or performance based). For **performance-based** assessment, it's multiplied with utilization value of the resources, whereas for **As-is on premises** assessment it's multiplied by allocated resources. <br> The default values change. <br>  For example, a 10-core VM with 20% utilization normally results in a two-core VM. With a comfort factor of 2.0, the result is a four-core VM instead. |
 | **Pricing settings**  | **Default savings option**  | Specify the savings option that you want the assessment to consider to help optimize your Azure compute cost. </br> [Azure reservations](/azure/cost-management-billing/reservations/save-compute-costs-reservations?view=migrate&preserve-view=true) (One year or three years reserved) are a good option for the most consistently running resources. </br> [Azure Savings Plan](/azure/cost-management-billing/savings-plan/savings-plan-compute-overview?view=migrate&preserve-view=true) (One year or three years savings plan) provide additional flexibility and automated cost optimization. </br> When you select **None**, the Azure compute cost is based on the Pay-as-you-go rate considering 730 hours as VM uptime, unless specified otherwise in VM uptime attribute.|
 | |**Offer/Licensing program**| The [Azure offer](https://azure.microsoft.com/support/legal/offer-details/) in which you're enrolled. The assessment estimates the cost for that offer. Select one of the pay-as-you-go, Enterprise Agreement support, or pay-as-you-go Dev/Test. </br> You need to select pay-as-you-go in offer/licensing program to be able to use Reserved Instances or Azure Savings Plan. When you select any savings option other than **None**, the *Discount (%)* and *VM uptime* properties aren't applicable. The monthly cost estimates are calculated by multiplying 744 hours in the VM uptime field with the hourly price of the recommended SKU.|
 | |**Currency** | The billing currency for your account.| 

articles/migrate/assessment-report.md

@@ -52,7 +52,7 @@ This value is multiplied by the comfort factor(taken as an input in assessment s
 
 ### Monthly costs 
 
-After right-sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default **Minimizing the cost** is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more [about how pricing](cost-estimation.md) works in Azure Migrate assessments. 
+After right sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default **Minimizing the cost** is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more [about how pricing](cost-estimation.md) works in Azure Migrate assessments. 
 
 ### Confidence ratings (performance-based) 
 

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

@@ -83,8 +83,8 @@ 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.
-    - 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.
+- 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.
 - This value is multiplied by the comfort factor to get the effective performance utilization data for these metrics that the appliance collects:

articles/migrate/review-sap-assessment.md

@@ -17,8 +17,8 @@ This tutorial explains how to review assessments created for your on-premises SA
 In this tutorial, you'll learn: 
 
 * Step-by-step instructions to review assessments created for on-premises SAP systems using Azure Migrate. 
-* Navigate to the Azure Migrate page to access the relevant options to view assessments for SAP systems.
-* Navigate Assessments page to view detailed information, including SAP system essentials, assessed entities, and cost estimates.
+* How to navigate Azure Migrate page to access the relevant options to view assessments for SAP systems.
+* How to navigate Assessments page to view detailed information, including SAP system essentials, assessed entities, and cost estimates.
 
 ## Review an assessment 
 
@@ -36,7 +36,7 @@ To review an assessment, follow these steps:
     :::image type="content" source="./media/tutorial-assess-sap-systems/sap-on-azure.png" alt-text="Screenshot that shows to select SAP on Azure." lightbox="./media/tutorial-assess-sap-systems/sap-on-azure.png":::
 
 > [!NOTE]
-> When you update any of the assessment settings, it triggers a new assessment, which takes a few minutes to reflect the updates.
+> When you update any of the assessment settings, it triggers a new assessment. It takes a few minutes to reflect the updates.
 
 ## Next steps
 Find server dependencies using [dependency mapping](concepts-dependency-visualization.md).