Addressed PLR comments

Author: SnehaSudhirG

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

@@ -42,8 +42,8 @@ MySQL assessments are performed on the **performance-based** sizing criteria, ma
 
 You can assess your on-premises MySQL instances using the configuration and utilization data collected by lightweight Azure Migrate appliances, which discover the instances and databases and send the data to the Azure Migrate service.
 
-1. Deploy the Azure Migrate appliances to discover the MySQL instances: [Refer this tutorial](tutorial-discover-mysql-database-instances.md) to deploy the Azure Migrate appliances and discover the MySQL instances that you want to assess.
-1. Create a MySQL assessment: Refer this [tutorial](create-mysql-assessment.md) to create a new assessment and review the reports.
+1. Deploy the Azure Migrate appliances to discover the MySQL instances: See this [tutorial](tutorial-discover-mysql-database-instances.md) to deploy the Azure Migrate appliances and discover the MySQL instances that you want to assess.
+1. Create a MySQL assessment: See this [tutorial](create-mysql-assessment.md) to create a new assessment and review the reports.
 
 ## Properties to create and customize a MySQL assessment
 
@@ -73,12 +73,12 @@ The Azure Database for MySQL assessment properties includes:
 
 | **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.
+| **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. As per the assessment report, we recommend 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
 
-The appliance collects performance data for compute settings with these steps:
+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.
@@ -133,7 +133,7 @@ Azure Migrate recommends the [Autoscale IOPS feature in Azure Database for MySQL
 ## Confidence ratings
 
 Each MySQL assessment is associated with a confidence rating. The rating ranges from one (lowest) to five (highest) stars. The confidence rating helps you estimate the reliability of the size recommendations Azure Migrate provides.
--  The rating is based on the availability of data points that are needed to compute the assessment.
+-  The rating is based on the availability of data points that are required to compute the assessment.
 - For performance-based sizing, the assessment collects performance data of all the MySQL instances and databases, which include:
   - CPU utilization (%)
   -	Memory utilization (%)

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

@@ -14,8 +14,11 @@ This article describes how to discover MySQL database instances running on serve
 
 In this tutorial, you learn how to:
 > [!div class="checklist"]
-> - Set up Kubernetes based appliance for discovery of MySQL database instances
-> - Configure the appliance and initiate continuous discovery 
+> - [Set up Kubernetes based appliance for discovery of MySQL database instances](#set-up-kubernetes-based-appliance)
+> - [Encryption at rest](#encryption-at-rest)
+> - [Configure the appliance and initiate continuous discovery](#configure-kubernetes-based-appliance)
+> - [Clean up of setup](#clean-up-of-setup)
+> - [Overview of Discovery results](#overview-of-discovery-results)
 
 
 > [!NOTE]
@@ -42,14 +45,14 @@ The following table lists the regions that support MySQL Discovery and Assessmen
 ## Prerequisites
 
 - An Azure subscription. If you don't have one, create a [free account](https://azure.microsoft.com/pricing/free-trial/).
-- Before you begin to discover MySQL database instances, use the relevant tutorial to create an Azure Migrate project as per your requirements in one of the [supported regions](#supported-regions):
+- Before you begin to discover MySQL database instances, use the below tutorials to create an Azure Migrate project as per your requirements in one of the [supported regions](#supported-regions):
 
    - [Discover servers running in a VMware environment](tutorial-discover-vmware.md)
    - [Discover servers running in Hyper-V environment](tutorial-discover-hyper-v.md)
    - [Discover physical servers](tutorial-discover-physical.md)
    - [Discover AWS instances](tutorial-discover-aws.md)
    - [Discover GCP instances](tutorial-discover-gcp.md)
-   - 
+   
 - After you create a project, ensure you've completed the server discovery using the Azure Migrate appliance.
 - Ensure that you perform the [discovery of software inventory](how-to-discover-applications.md) by providing the server credentials to the appliance configuration manager.
 
@@ -142,7 +145,7 @@ Before you execute the installer script, ensure that you have verified the follo
 
 **Packaged Kubernetes cluster**
 
- - This script needs to be run after you connect to a Linux machine on its terminal that has met the networking prerequisite and OS compatibility.  
+ - Run the script after you connect to a Linux machine on its terminal that has met the networking prerequisite and OS compatibility.  
  - Ensure that you install curl on the server. For Ubuntu, you can install it using the command `sudo apt-get install curl`, and for other OS (RHEL), you can use the command `yum install curl`.
  - Ensure that you install microk8s 1.29 on the server. For Ubuntu, you can install using the command `sudo snap install microk8s --classic --channel=1.29/stable`. Learn more on [how to install microk8s on Red Hat Enterprise Linux 9](https://snapcraft.io/install/microk8s/rhel).
 
@@ -152,7 +155,7 @@ Before you execute the installer script, ensure that you have verified the follo
  - Ensure that you have curl installed on the server. For Ubuntu, you can install it using the command </br> `sudo apt-get install curl` </br> and for other OS (RHEL), you can use the command </br> `yum install curl`
 
 > [!Important]
-> Don't edit the script before you execute it. You can only edit the script when want to [clean up the setup](#clean-up-of-setup).
+> Don't edit the script before you execute it. You can only edit the script when you want to [clean up the setup](#clean-up-of-setup).
 
 After you save the script on the Linux server, follow these steps: