UI terms update

Author: v-sreedevank

articles/migrate/tutorial-migrate-aws-virtual-machines.md

@@ -5,8 +5,8 @@ author: vijain
 ms.author: vijain
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 12/30/2024
-ms.custom: MVC, engagement-fy24
+ms.date: 12/31/2024
+ms.custom: MVC, engagement-fy25
 ---
 
 # Discover, assess, and migrate Amazon Web Services (AWS) VMs to Azure
@@ -276,7 +276,7 @@ A Mobility service agent must be preinstalled on the source AWS VMs to be migrat
 
 You can track job status in the portal notifications.
 
-You can monitor replication status by selecting **Replicating servers** in **Azure Migrate: Server Migration**.
+You can monitor replication status by selecting **Replicating servers** in **Migration and modernization**.
 
 ## Run a test migration
 

articles/migrate/tutorial-migrate-physical-virtual-machines.md

@@ -6,7 +6,7 @@ ms.author: vijain
 ms.manager: kmadnani
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 10/18/2024
+ms.date: 12/31/2024
 ms.custom: MVC, engagement-fy25
 ---
 
@@ -147,7 +147,7 @@ The first step of migration is to set up the replication appliance. To set up th
 
     ![Screenshot that shows Finalize registration.](./media/tutorial-migrate-physical-virtual-machines/finalize-registration.png)
 
-The mobility service agent must be installed on the servers to get them discovered by using the replication appliance. Discovered machines appear in **Azure Migrate: Server Migration**. As VMs are discovered, the **Discovered servers** count rises.
+The mobility service agent must be installed on the servers to get them discovered by using the replication appliance. Discovered machines appear in **Migration and modernization**. As VMs are discovered, the **Discovered servers** count rises.
 
 > [!NOTE]
 > We recommend that you perform discovery and assessment prior to the migration by using the Azure Migrate: Discovery and assessment tool, a separate lightweight Azure Migrate appliance. You can deploy the appliance as a physical server to continuously discover servers and performance metadata. For detailed steps, see [Discover physical servers](tutorial-discover-physical.md).
@@ -256,7 +256,7 @@ Now, select machines for migration.
 
 You can track job status in the portal notifications.
 
-You can monitor replication status by selecting **Replicating servers** in **Azure Migrate: Server Migration**.
+You can monitor replication status by selecting **Replicating servers** in **Migration and modernization**.
 
 ## Run a test migration
 

articles/migrate/tutorial-modernize-asp-net-aks.md

@@ -5,8 +5,8 @@ author: SnehaSudhirG
 ms.author: sudhirsneha
 ms.service: azure-migrate
 ms.topic: tutorial
-ms.date: 09/18/2024
-ms.custom: template-tutorial, engagement-fy24
+ms.date: 12/31/2024
+ms.custom: template-tutorial, engagement-fy25
 ---
 
 # Modernize ASP.NET web apps to Azure Kubernetes Service (preview)
@@ -143,7 +143,7 @@ Once you begin replication, Azure Migrate creates a replication job which can be
 
     :::image type="content" source="./media/tutorial-modernize-asp-net-aks/select-overview.png" alt-text="Screenshot of the Overview option selected.":::
 
-2. Select **Azure Migrate: Server Migration** hub > **Modernization (Preview)** > **Jobs**.
+2. Select **Migration and modernization** hub > **Modernization (Preview)** > **Jobs**.
 
     :::image type="content" source="./media/tutorial-modernize-asp-net-aks/migration-hub-jobs.png" alt-text="Screenshot of the Jobs tab in the migration hub.":::
 
@@ -186,7 +186,7 @@ With the container image ready, run a test migration to ensure your application
 
 If the test migration fails:
 
-1. Navigate to **Azure Migrate: Server Migration** hub > **Modernization (Preview)** > **Jobs**.
+1. Navigate to **Migration and modernization** hub > **Modernization (Preview)** > **Jobs**.
 2. Select the **Initiate test migrate** job that failed.
 
     :::image type="content" source="./media/tutorial-modernize-asp-net-aks/migration-hub-jobs-failed-test-migrate.png" alt-text="Screenshot of the failed test migrate job.":::

articles/migrate/vmware/troubleshoot-replication-vmware.md

@@ -6,13 +6,13 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: troubleshooting
 ms.service: azure-migrate
-ms.date: 12/08/2022
-ms.custom: vmware-scenario-422, mvc, engagement-fy23
+ms.date: 12/31/2024
+ms.custom: vmware-scenario-422, mvc, engagement-fy25
 ---
 
 # Troubleshoot slow replication or stuck migration issues in agentless VMware migration 
 
-This article helps you troubleshoot slow replication or stuck migration issues that you may encounter when you replicate on-premises VMware VMs using the Azure Migrate: Server Migration agentless method.
+This article helps you troubleshoot slow replication or stuck migration issues that you may encounter when you replicate on-premises VMware VMs using the Server Migration agentless method.
 
 [!INCLUDE [scenario-banner.md](../includes/scenario-banner.md)]