Language edits

Author: v-sreedevank

articles/migrate/concepts-assessment-calculation.md

@@ -33,7 +33,7 @@ There are three types of assessments you can create using Azure Migrate: Discove
 **Azure VMware Solution (AVS)** | Assessments to migrate your on-premises servers to [Azure VMware Solution (AVS)](../azure-vmware/introduction.md). You can assess your on-premises [VMware VMs](how-to-set-up-appliance-vmware.md) for migration to Azure VMware Solution (AVS) using this assessment type. [Learn more](concepts-azure-vmware-solution-assessment-calculation.md)
 
 > [!NOTE]
-> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
+> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, select the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
 
 Assessments you create with Azure Migrate are a point-in-time snapshot of data. An Azure VM assessment provides two sizing criteria options:
 

articles/migrate/concepts-azure-sql-assessment-calculation.md

@@ -28,7 +28,7 @@ There are four types of assessments that you can create using the Azure Migrate:
 **Azure VMware Solution (AVS)** | Assessments to migrate your on-premises servers to [Azure VMware Solution (AVS)](../azure-vmware/introduction.md). <br/><br/> You can assess your on-premises [VMware VMs](how-to-set-up-appliance-vmware.md) for migration to Azure VMware Solution (AVS) using this assessment type. [Learn more](concepts-azure-vmware-solution-assessment-calculation.md).
 
 > [!NOTE]
-> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool then shows the correct count for that assessment type. 
+> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, select the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool then shows the correct count for that assessment type. 
 
 An Azure SQL assessment provides two sizing criteria:
 

articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md

@@ -31,7 +31,7 @@ Assessments you create with Azure Migrate are a point-in-time snapshot of data.
 **Azure VMware Solution (AVS)** | Assessments to migrate your on-premises vSphere servers to [Azure VMware Solution](../azure-vmware/introduction.md). You can assess your on-premises [VMware vSphere VMs](how-to-set-up-appliance-vmware.md) for migration to Azure VMware Solution using this assessment type. [Learn more](concepts-azure-vmware-solution-assessment-calculation.md)
 
 > [!NOTE]
-> If the number of Azure VM or Azure VMware Solution assessments are incorrect on the Discovery and assessment tool, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or Azure VMware Solution assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
+> If the number of Azure VM or Azure VMware Solution assessments are incorrect on the Discovery and assessment tool, select the total number of assessments to navigate to all the assessments and recalculate the Azure VM or Azure VMware Solution assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
 
 Azure VMware Solution assessment provides two sizing criteria options:
 

articles/migrate/create-manage-projects.md

@@ -87,19 +87,6 @@ Find a project as follows:
 
 3. Select the appropriate subscription and project.
 
-
-### Find a classic project
-
-If you created the project in the [previous version](migrate-services-overview.md) of Azure Migrate, find it as follows:
-
-1. In the [Azure portal](https://portal.azure.com), search for *Azure Migrate*.
-2. In the Azure Migrate dashboard, if you've created a project in the previous version, a banner referencing older projects appears. Select the banner.
-
-    :::image type="content" source="./media/create-manage-projects/access-existing-projects.png" alt-text="Screenshot to access already existing projects.":::
-
-3. Review the list of old projects.
-
-
 ## Delete a project
 
 To delete a project, follow these steps: 
@@ -132,4 +119,4 @@ Note that:
 
 ## Next steps
 
-Add [assessment](how-to-assess.md) or [migration](how-to-migrate.md) tools to projects.
+Add [assessment](how-to-create-assessment.md) or [migration](how-to-migrate.md) tools to projects.

articles/migrate/deploy-appliance-script-government.md

@@ -42,10 +42,10 @@ You can use the script to deploy the Azure Migrate appliance on an existing phys
 
 ### Download the script
 
-1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, click **Discover**.
+1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Discover**.
 2. In **Discover server** > **Are your servers virtualized?**, select **Yes, with VMware vSphere hypervisor**.
 3. Provide an appliance name and generate a project key in the portal.
-3. Click **Download**, to download the zipped file.
+3. Select **Download**, to download the zipped file.
 
 ### Verify security
 
@@ -102,10 +102,10 @@ Make sure that the appliance can connect to Azure URLs for [government clouds](m
 
 ### Download the script
 
-1.	In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, click **Discover**.
-2.	In **Discover servers** > **Are your servers virtualized?**, select **Yes, with Hyper-V**.
+1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Discover**.
+2. In **Discover servers** > **Are your servers virtualized?**, select **Yes, with Hyper-V**.
 3. Provide an appliance name and generate a project key in the portal.
-3. Click **Download**, to download the zipped file. 
+1. Select **Download** to download the zipped file.
 
 ### Verify security
 
@@ -163,9 +163,9 @@ Make sure that the appliance can connect to Azure URLs for [government clouds](m
 
 ### Download the script
 
-1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, click **Discover**.
+1. In **Migration goals** > **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select **Discover**.
 2. In **Discover servers** > **Are your servers virtualized?**, select **Physical or other (AWS, GCP, Xen etc.)**.
-3. Click **Download**, to download the zipped file.
+3. Select **Download** to download the zipped file.
 
 ### Verify security
 

articles/migrate/how-to-create-a-group.md

@@ -32,11 +32,11 @@ You can create a group at the same time that you [create an assessment](how-to-c
 
 If you want to create a group manually outside of creating an assessment, do the following:
 
-1. In the Azure Migrate project > **Overview**, click **Assess and migrate servers**. In **Azure Migrate: Discovery and assessment**, click **Groups**
-    - If you haven't yet added the Azure Migrate: Discovery and assessment tool, click to add it. [Learn more](how-to-assess.md).
+1. In the Azure Migrate project > **Overview**, select **Assess and migrate servers**. In **Azure Migrate: Discovery and assessment**, select **Groups**
+    - If you haven't yet added the Azure Migrate: Discovery and assessment tool, select to add it. [Learn more](how-to-assess.md).
     - If you haven't yet created an Azure Migrate project, [learn more](./create-manage-projects.md).
 
-2. Click the **Group** icon.
+2. Select the **Group** icon.
 3. In **Create group**, specify a group name, and in **Appliance name**, select the Azure Migrate appliance you're using for server discovery.
 4. From the server list, select the servers you want to add to the group > **Create**.
 
@@ -54,19 +54,19 @@ If you've already [set up dependency mapping](how-to-create-group-machine-depend
 
 1. In the **Servers, databases and web apps** tab, in **Azure Migrate: Discovery and assessment** tile, select **Groups**.
 2. Select the group you want to refine.
-    - If you haven't yet set up dependency mapping, the **Dependencies** column will show a **Requires installation** status. For each server for which you want to visualize dependencies, click **Requires installation**. Install a couple of agents on each server, before you can map the server dependencies. [Learn more](how-to-create-group-machine-dependencies.md).
+    - If you haven't yet set up dependency mapping, the **Dependencies** column will show a **Requires installation** status. For each server for which you want to visualize dependencies, select **Requires installation**. Install a couple of agents on each server, before you can map the server dependencies. [Learn more](how-to-create-group-machine-dependencies.md).
 
         ![Add dependency mapping](./media/how-to-create-a-group/add-dependency-mapping.png)
 
-    - If you've already set up dependency mapping, on the group page, click **View dependencies** to open the group dependency map.
+    - If you've already set up dependency mapping, on the group page, select **View dependencies** to open the group dependency map.
 
-3. After clicking **View dependencies**, the group dependency map shows the following:
+3. After selecting **View dependencies**, the group dependency map shows the following:
 
     - Inbound (clients) and outbound (servers) TCP connections to and from all servers in the group that have the dependency agents installed.
     - Dependent servers that don't have the dependency agents installed are grouped by port numbers.
     - Dependent servers with dependency agents installed are shown as separate boxes.
     - Processes running inside the server. Expand each server box to view the processes.
-    - Server properties (including FQDN, operating system, MAC address). Click on each server box to view the details.
+    - Server properties (including FQDN, operating system, MAC address). Select each server box to view the details.
 
 4. To view dependencies in a time interval of your choice, modify the time range (an hour by default) by specifying  start and end dates, or the duration.
 

articles/migrate/how-to-create-azure-app-service-assessment.md

@@ -63,7 +63,7 @@ Run an assessment as follows:
 1. In **Select or create a group** > select **Create New** and specify a group name.
 1. Select the appliance, and select the servers you want to add to the group. Select **Next**.
 1. In **Review + create assessment**, review the assessment details, and select **Create Assessment** to create the group and run the assessment.
-1. After the assessment is created, go to **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** tile and refresh the tile data by clicking on the **Refresh** option on top of the tile. Wait for data to get refreshed.
+1. After the assessment is created, go to **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** tile and refresh the tile data by selecting the **Refresh** option on top of the tile. Wait for data to get refreshed.
      :::image type="content" source="./media/tutorial-assess-webapps/tile-refresh.png" alt-text="Refresh discovery and assessment tool data":::
 1. Select the number next to Azure App Service assessment.
      :::image type="content" source="./media/tutorial-assess-webapps/assessment-webapps-navigation.png" alt-text="Navigation to created assessment":::

articles/migrate/how-to-create-azure-sql-assessment.md

@@ -172,8 +172,8 @@ You can review readiness reports for different migration strategies:
     - **Unknown**: Azure Migrate can't assess readiness, because the discovery is in progress or there are issues during discovery that need to be fixed from the notifications blade. If the issue persists, contact [Microsoft support](https://support.microsoft.com).
 
 1. Select the instance name and drill-down to see the number of user databases, instance details including instance properties, compute (scoped to instance) and source database storage details.
-1. Click the number of user databases to review the list of databases and their details.
-1. Click review details in the **Migration issues** column to review the migration issues and warnings for a particular target deployment type.
+1. Select the number of user databases to review the list of databases and their details.
+1. Select review details in the **Migration issues** column to review the migration issues and warnings for a particular target deployment type.
 
 ### Review cost estimates
 The assessment summary shows the estimated monthly compute and storage costs for Azure SQL configurations corresponding to the recommended SQL Server on Azure VM and/or Azure SQL Managed Instances and/or Azure SQL Database deployment type.

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

@@ -134,7 +134,7 @@ Select the servers on which you want to stop dependency discovery.
 1. Select the **Dependency analysis** drop-down.
 1. Select **Remove servers**.
 1. In the **Remove servers** page, select the server, which you want to stop for dependency analysis.
-1. After selecting the servers, click **Remove servers**.
+1. After selecting the servers, select **Remove servers**.
 
 If you want to stop dependency simultaneously on multiple servers, you can use [PowerShell](#start-or-stop-dependency-analysis-using-powershell) to do so.