fixing pre-migration steps structure

Author: Sandeep Nair

articles/cosmos-db/mongodb/pre-migration-steps.md

@@ -49,11 +49,13 @@ When you plan a migration, we recommend that whenever possible you plan at the p
 
 ## Pre-migration assessment
 
-Second, as a prelude to planning your migration, assess the readiness of resources in your data estate for migration.
+The first pre-migration step, as a prelude to planning your migration, assess the readiness of resources in your data estate for migration.
 
 Assessment involves finding out whether you're using the [features and syntax that are supported](./feature-support-42.md). It also includes making sure you're adhering to the [limits and quotas](../concepts-limits.md#per-account-limits). The aim of this stage is to create a list of incompatibilities and warnings, if any. After you have the assessment results, you can try to address the findings during rest of the migration planning.
 
-## Azure Cosmos DB Migration for MongoDB extension
+There are 3 ways to complete the pre-migration steps, we recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension).
+
+### Azure Cosmos DB Migration for MongoDB extension
 
 The [Azure Cosmos DB Migration for MongoDB extension](/sql/azure-data-studio/extensions/database-migration-for-mongo-extension) in Azure Data Studio helps you assess a MongoDB workload for migrating to Azure Cosmos DB for MongoDB. You can use this extension to run an end-to-end assessment on your workload and find out the actions that you may need to take to seamlessly migrate your workloads on Azure Cosmos DB. During  the assessment of a MongoDB endpoint, the extension reports all the discovered resources.
 
@@ -64,9 +66,9 @@ The Azure Cosmos DB Migration for MongoDB extension tool does both the pre-migra
 > [!NOTE]
 > Azure Cosmos DB Migration for MongoDB extension does not perform an end-to-end assessment. We recommend you to go through [the supported features and syntax](./feature-support-42.md), [Azure Cosmos DB limits and quotas](../concepts-limits.md#per-account-limits) in detail, as well as perform a proof-of-concept prior to the actual migration.
 
-## Manual discovery
+### Manual discovery (legacy) 
 
-The first pre-migration step is resource discovery. In this step, you need to create a **data estate migration spreadsheet**. The purpose of this spreadsheet is to enhance your productivity and help you to plan migration from end-to-end and use it as a tracking document throughout the migration process.
+Alternatively, you could create a **data estate migration spreadsheet**. The purpose of this spreadsheet is to enhance your productivity and help you to plan migration from end-to-end and use it as a tracking document throughout the migration process.
 
 * This sheet contains a comprehensive list of the existing resources (databases or collections) in your MongoDB data estate.
 * The spreadsheet should be structured as a record of your data estate resources, in list form.
@@ -79,10 +81,10 @@ Here are some tools you can use for discovering resources:
 * [MongoDB Shell](https://www.mongodb.com/try/download/shell)
 * [MongoDB Compass](https://www.mongodb.com/try/download/compass)
 
-## Database Migration Assistant utility (legacy) 
+### Database Migration Assistant utility (legacy) 
 
 > [!NOTE]
-> Database Migration Assistant is a legacy utility meant to assist you with the pre-migration steps. Microsoft recommends you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension) for all pre-migration steps.
+> Database Migration Assistant is a legacy utility meant to assist you with the pre-migration steps. We recommend you to use the [Azure Cosmos DB Migration for MongoDB extension](#azure-cosmos-db-migration-for-mongodb-extension) for all pre-migration steps.
 
 You may use the [Database Migration Assistant](programmatic-database-migration-assistant-legacy.md) (DMA) utility to assist you with the discovery stage and create the data estate migration sheet programmatically.