Addressed Pre-PLR comments - 2

Author: SnehaSudhirG

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

@@ -49,19 +49,29 @@ You can assess your on-premises MySQL instances using the configuration and util
 
 The Azure Database for MySQL assessment properties includes:
 
-**Section** | **Setting** | **Details**
---- | --- | ---
-Target and pricing settings | **Target location**  | The Azure region to which you want to migrate. Azure Database for MySQL configuration and cost recommendations are based on the location that you specify.
+**Target and pricing settings**
+
+| **Setting** | **Details**
+| --- | ---
+| **Target location**  | The Azure region to which you want to migrate. Azure Database for MySQL configuration and cost recommendations are based on the location that you specify.
 Target and pricing settings | **Environment type** | The environment for the MySQL deployments to apply Azure Database for MySQL configuration and cost recommendations applicable to Production or Development/Testing.
-Target and pricing settings | **Licensing program**  | The Azure offer if you're enrolled. Currently, the field is Pay-as-you-go by default, which gives you retail Azure prices.
-Target and pricing settings | **Currency** | The billing currency for your account.
-Target and pricing settings | **Savings options**  | Specify the reserved capacity savings option that you want the assessment to consider to optimize your Azure compute cost. <br/><br> Azure reservations (one year or three years reserved) are a good option for the most consistently running resources. <br/><br> When you select None, the Azure compute cost is based on the Pay-as-you-go rate or based on actual usage. <br/><br> You need to select pay-as-you-go in the offer/licensing program to be able to use Reserved Instances. When you select any savings option other than None, the Discount (%) setting isn’t applicable. The monthly cost estimates are calculated by multiplying 744 hours with the hourly price of the recommended SKU.
-Target and pricing settings | **Discount (%)** | Any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
-Assessment criteria | **Sizing criteria**  | Set to be **Performance-based** by default, which means Azure Migrate collects performance metrics pertaining to MySQL instances to recommend an optimal-sized Azure Database for MySQL instance configuration.
-Assessment criteria | **Performance history** | Indicate the data duration on which you want to base the assessment (Default is one day).
-Assessment criteria | **Percentile utilization** | Indicate the percentile value you want to use for the performance sample (Default is 95th percentile).
-Assessment criteria | **Comfort factor** | Indicate the buffer you want to use during assessment. This accounts for issues like seasonal usage, short performance history, and likely increases in future usage.
-Azure DB for MySQL – Flexible Server sizing | **Service Tier** | Choose the most appropriate service tier option to accommodate your business needs for migration to Azure Database for MySQL. <br/><br> By default, all three service tiers are selected. Azure Migrate recommends the best suited service tier for your servers based on your Environment Type and the collected performance data. <br/><br> Select *General Purpose* if you want an Azure Database for MySQL configuration designed for business workloads that require balanced computing and memory with scalable I/O throughput. <br/><br> Select *Business Critical* if you want an Azure Database for MySQL configuration designed for high-performance database workloads that require in-memory performance for faster transaction processing and higher concurrency.
+| **Licensing program**  | The Azure offer if you're enrolled. Currently, the field is Pay-as-you-go by default, which gives you retail Azure prices.
+| **Currency** | The billing currency for your account.
+| **Savings options**  | Specify the reserved capacity savings option that you want the assessment to consider to optimize your Azure compute cost. <br/><br> Azure reservations (one year or three years reserved) are a good option for the most consistently running resources. <br/><br> When you select None, the Azure compute cost is based on the Pay-as-you-go rate or based on actual usage. <br/><br> You need to select pay-as-you-go in the offer/licensing program to be able to use Reserved Instances. When you select any savings option other than None, the Discount (%) setting isn’t applicable. The monthly cost estimates are calculated by multiplying 744 hours with the hourly price of the recommended SKU.
+| **Discount (%)** | Any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
+
+**Assessment criteria**
+| **Setting** | **Details**
+| --- | ---
+| **Sizing criteria**  | Set to be **Performance-based** by default, which means Azure Migrate collects performance metrics pertaining to MySQL instances to recommend an optimal-sized Azure Database for MySQL instance configuration.
+| **Performance history** | Indicate the data duration on which you want to base the assessment (Default is one day).
+| **Percentile utilization** | Indicate the percentile value you want to use for the performance sample (Default is 95th percentile).
+| **Comfort factor** | Indicate the buffer you want to use during assessment. This accounts for issues like seasonal usage, short performance history, and likely increases in future usage.
+
+**Azure DB for MySQL – Flexible Server sizing**
+| **Setting** | **Details**
+| --- | ---
+| **Service Tier** | Choose the most appropriate service tier option to accommodate your business needs for migration to Azure Database for MySQL. <br/><br> By default, all three service tiers are selected. Azure Migrate recommends the best suited service tier for your servers based on your Environment Type and the collected performance data. <br/><br> Select *General Purpose* if you want an Azure Database for MySQL configuration designed for business workloads that require balanced computing and memory with scalable I/O throughput. <br/><br> Select *Business Critical* if you want an Azure Database for MySQL configuration designed for high-performance database workloads that require in-memory performance for faster transaction processing and higher concurrency.
 
 
 ## Performance data calculation for MySQL instances

articles/migrate/tutorial-discover-mysql-database-instances.md

@@ -19,7 +19,7 @@ In this tutorial, you learn how to:
 
 
 > [!NOTE]
-> - A Kubernetes-based appliance is required to discover MySQL database instances. [Learn more].(migrate-appliance.md) about scenarios covered by a Windows-based appliance.
+> - A Kubernetes-based appliance is required to discover MySQL database instances [Learn more].(migrate-appliance.md) about scenarios covered by a Windows-based appliance.
 > - This tutorial shows you the quickest path for trying out a scenario. They use default options where possible.
 
 
@@ -94,10 +94,10 @@ After you have performed server discovery and software inventory using the Azure
 
    1. You can select a Key Vault from the drop-down or **Create new** Key Vault. This Key Vault is used to process the credentials provided in the project to start discovery of MySQL database instances.
 
-    > [!Note]
-    > The Key Vault can be chosen or created in the same subscription and region as that of the Azure Migrate project. When you create/select a Key Vault, ensure that purge protection is disabled else there will be issues in processing of credentials through the Key Vault.
+   > [!Note]
+   > The Key Vault can be chosen or created in the same subscription and region as that of the Azure Migrate project. When you create/select a Key Vault, ensure that purge protection is disabled else there will be issues in processing of credentials through the Key Vault.
 
-   ---
+    ---
 
 1.	After you provide the appliance name and Key Vault, select **Generate script** to generate an installer script that you can download or copy the script and save it as Deploy.sh on a Linux server on-premises.