edits

Author: jmart1428

articles/migration/migrate-from-aws.yml

@@ -18,7 +18,7 @@ landingContent:
     linkLists:
       - linkListType: concept
         links:
-          - text: Migrate workloads to Azure from other cloud based services
+          - text: Migrate workloads to Azure from other cloud-based services
             url:  ./migrate-to-azure.md
 
   - title: Component migration

articles/migration/migrate-to-azure.md

@@ -1,71 +1,63 @@
 ---
-title: Migrate workloads to Azure
-description: Before you migrate workloads, start with a strong foundation in Azure.
+title: Migrate Workloads to Azure
+description: Learn how to migrate workloads from AWS and Google Cloud to Azure, including planning, implementation, and optimization strategies.
 author: robbyatmicrosoft
 ms.author: robbymillsap
 ms.date: 03/24/2025
 ms.topic: conceptual
 ms.custom: migration
 ---
 
-# Migrate workloads to Azure from other clouds
+# Migrate workloads to Azure from other cloud platforms
 
-
-This collection is curated to assist workload teams in planning and executing the migration of their workloads. It covers migrations from cloud platforms like Amazon Web Services (AWS) and Google Cloud to Microsoft Azure. The expected outcome is that, after the migration to Azure is complete, the workload will be shut down on the source platform.
+The Azure migration guide collection helps workload teams plan and implement their workload migration. It includes guidance for migrations from cloud platforms, like Amazon Web Services (AWS) and Google Cloud, to Microsoft Azure. This guidance assumes that, after you complete your migration to Azure, you decommission the workload on the source platform.
 
 > [!IMPORTANT] 
 >
-> Certain migration scenarios are out of scope for this collection. It doesn't cover on-premises to Azure migrations, full data center migrations, or region relocations. Additionally, it doesn't address concurrently running a workload on multiple clouds.
-
-Migration to Azure typically involves _replatforming the workload_, which includes transitioning both the infrastructure and management layer from the source cloud provider to Azure. Finding the best match for your source components on Azure is an important step in the migration process. Keep in mind that not all components map one-to-one. You'll need to redesign the architecture or revisit some code to maintain functionality to accomplish your business objectives. This collection offers insights into such cloud-to-cloud transitions by comparing workload components and services, supported with example migration scenarios.
-
-
-## Prerequisite to workload migration
+> Some migration scenarios are out of scope for this collection. It doesn't cover on-premises to Azure migrations, full datacenter migrations, or region relocations. It also doesn't address workloads that concurrently run on multiple clouds.
 
-Workloads should be migrated only after the organization is committed to Azure and have established their approach for adopting Azure. Before migrating workloads, we recommend that you understand the fundamental concepts on Azure and have an active Azure enrollment. Explore these Cloud Adoption Framework (CAF) resources to achieve these goals:
+Migration to Azure typically involves replatforming the workload, which includes transitioning both the infrastructure and management layer from the source cloud provider to Azure. During the migration process, you need to find the best match for your source components on Azure. Not all components map one-to-one. To accomplish your business objectives, you might need to redesign the architecture or revisit code to maintain functionality.
 
-- Learn about terms used in Azure, and how the concepts relate to one another.
+This collection provides insight into such cloud-to-cloud transitions. It compares workload components and services, and includes example migration scenarios.
 
-    [**Azure fundamental concepts**](/azure/cloud-adoption-framework/ready/considerations/fundamental-concepts)
+## Prerequisites for workload migrations
 
-- Complete the learning objectives in the training module to develop your organization's migration plan and identify the types of workloads that need to be migrated.
+Before you migrate workloads, ensure that you commit your organization to Azure and establish your adoption approach. We recommend that you understand the fundamental Azure concepts and have an active Azure enrollment. To achieve these goals, explore the following Cloud Adoption Framework for Azure resources:
 
-    [**Learn about the Cloud Adoption Framework Migrate methodology**](/training/modules/cloud-adoption-framework-migrate/)
+- To learn about terms in Azure and how the concepts relate to one another, see [Azure fundamental concepts](/azure/cloud-adoption-framework/ready/considerations/fundamental-concepts).
 
-The next phase involves the workload team planning and executing the migration. This includes assessing the current workload design, preparing a solution in Azure, making necessary code changes, and performing the migration. 
+- To develop your organization's migration plan and identify the types of workloads that you should migrate, see the training module, [Use the Cloud Adoption Framework Migrate methodology to migrate your workload to the cloud](/training/modules/cloud-adoption-framework-migrate/).
 
+In the next phase, the workload team plans and implements the migration. They assess the current workload design, prepare a solution in Azure, make necessary code changes, and perform the migration. 
 
 ## Target audience
 
-The content is applicable to workload roles and functions at the team level.
+This collection applies to the following workload roles and functions at the team level.
 
-- **Workload architect**. They might redesign certain aspects and validate the overall architecture to ensure it continues to meet business requirements. Architects must address gaps considering the workload's specific characteristics and business constraints.
-
-- **Workload team members**. They must understand how their responsibilities will change during the migration process and post migration. For example, database administrators (DBAs) who manage scripts and perform daily backups on Amazon RDS must adapt to performing these tasks on Azure SQL Database. 
+- **Workload architects** who redesign various architecture aspects and validate the overall architecture to ensure that it continues to meet business requirements. Architects address gaps by considering the workload's specific characteristics and business constraints.
 
+- **Workload team members** who need to understand how their responsibilities change during the migration process and after migration. For example, database administrators who manage scripts and perform daily backups on Amazon Relational Database Service must adapt to performing the same tasks on Azure SQL Database. 
 
 ## Content layout
 
-The content is organized by platform, starting with your source platform. Within each platform, you'll find a comparison sheet to help you get started on comparing the capabilities of your workload and the services used in it. Additionally, example scenarios and service-level migration guides are provided to illustrate the comparisons.
+The migration guide content is organized by platform, starting with your source platform. Each platform includes comparison articles. To get started, compare the capabilities of your workload and its services with their closest Azure counterparts. These articles also include example scenarios and service-level migration guides to illustrate the comparisons.
 
-We recommend starting your learning journey based on your source platform:
+Start your learning journey based on your source platform:
 
 > [!div class="nextstepaction"]
-> [Migrate a workload from Amazon Web Services (AWS)](./migrate-from-aws.yml)
-
+> [Migrate a workload from AWS](./migrate-from-aws.yml)
 
 > [!div class="nextstepaction"]
 > [Migrate a workload from Google Cloud](./migrate-from-google-cloud.yml)
 
-You'll also find guidance that's applicable to all platforms. Such platform-agnostic guidance is included in all sections for convenience.
-
+This collection also includes guidance that applies to all platforms. All sections include such platform-agnostic guidance for convenience.
 
 ## Tools
 
-In addition to content, there are specialized tools to assist with migration tasks or might be helpful in measuring the success of the migration against business goals.
+In addition to content, you can explore specialized tools to assist with migration tasks or measure the success of your migration against business goals.
 
-|Tool|Use to...|
+|Tool|Benefit|
 |---|---|
-|[Azure Migrate](/azure/migrate/migrate-services-overview)| Perform discovery and assessment of migration assets, primarily for infrastructure, applications, and data components. |
-|Well-Architected Review assessment of the source platform, if available|Review and measure the business goals of your architecture on the source platform. This will help you baseline your expectations on Azure.|
-|[Microsoft Azure Well-Architected Review assessment](/assessments/azure-architecture-review/)| Evaluate your architecture decisions to identify any regressions from the source baseline. Also explore optimization opportunities to get the best on Azure.|
+|[Azure Migrate and Modernize](/azure/migrate/migrate-services-overview)| Analyze and assess migration assets, primarily infrastructure, applications, and data components. |
+|Azure Well-Architected Review assessment of the source platform, if available|Review and measure the business goals of your architecture on the source platform. This assessment helps you establish a baseline for your expectations on Azure.|
+|[Azure Well-Architected Review assessment](/assessments/azure-architecture-review/)| Evaluate your architecture decisions to identify any regressions from the source baseline. Also explore optimization opportunities to maximize performance on Azure.|