addressed reviewrs notes excluding image names and PII info

Author: markingmyname

articles/postgresql/migrate/migration-service/includes/aws/prerequisites-migration-service-postgresql-offline-aws.md

@@ -4,7 +4,7 @@ description: Providing the offline prerequisites for the migration service in Az
 author: apduvuri
 ms.author: adityaduvuri
 ms.reviewer: maghan
-ms.date: 06/07/2024
+ms.date: 06/20/2024
 ms.service: postgresql
 ms.topic: include
 ---
@@ -37,9 +37,9 @@ Proper networking setup is essential to ensure successful migration connectivity
 
 - **Networking requirements for migration:**
 
-- **ExpressRoute/IPsec VPN/VPN tunneling**: When connecting your on-premises/AWS source to Azure, you might need to set up an ExpressRoute, IPsec VPN, or VPN tunneling to facilitate secure data transfer.
+  - **ExpressRoute/IPsec VPN/VPN tunneling**: When connecting your on-premises/AWS source to Azure, you might need to set up an ExpressRoute, IPsec VPN, or VPN tunneling to facilitate secure data transfer.
 
-- **VNET peering**: Establish virtual network peering between the two distinct VNets to enable direct network connectivity, a prerequisite for migration between the Azure VM and the Azure Database for PostgreSQL.
+  - **VNET peering**: Establish virtual network peering between the two distinct VNets to enable direct network connectivity, a prerequisite for migration between the Azure VM and the Azure Database for PostgreSQL.
 
 - **Connectivity Scenarios:**
 
@@ -51,7 +51,7 @@ The following table can help set up the network between the source and target.
 | Private | Public | This configuration isn't supported; use pg_dump/pg_restore for data transfer. |
 | Public | Private | No other action is required if the source is whitelisted in the target's firewall rules. |
 | Private | Private | Establish an ExpressRoute, IPsec VPN, VPN Tunneling, or virtual network Peering between the source and target. |
-| Private | Private Endpoint | This configuration isn't supported; contact [Microsoft support](https://support.microsoft.com/). |
+| Private | Private Endpoint | This configuration isn't supported; contact [Microsoft support](https://support.microsoft.com/en-US). |
 
 - **Additional networking considerations:**
 
@@ -72,7 +72,7 @@ Search for the Azure.extensions server parameter on the Server parameter page on
 
 - Save the parameter changes and restart the Azure Database for PostgreSQL to apply the new configuration if necessary.
 
-:::image type="content" source="../../media/tutorial-migration-service-aws-offline/extensions-enable-flexible-server.png" alt-text="Screenshot of Screenshot of extensions in the Azure portal.":::
+:::image type="content" source="../../media/tutorial-migration-service-aws-offline/extensions-enable-flexible-server.png" alt-text="Screenshot of extensions in the Azure portal." lightbox="../../media/tutorial-migration-service-aws-offline/extensions-enable-flexible-server.png":::
 
 - Check if the list contains any of the following extensions:
     - PG_CRON

articles/postgresql/migrate/migration-service/includes/aws/prerequisites-migration-service-postgresql-online-aws.md

@@ -4,7 +4,7 @@ description: Providing the online prerequisites for the migration service in Azu
 author: apduvuri
 ms.author: adityaduvuri
 ms.reviewer: maghan
-ms.date: 06/07/2024
+ms.date: 06/12/2024
 ms.service: postgresql
 ms.topic: include
 ---
@@ -40,7 +40,7 @@ If the source PostgreSQL version is less than 9.5, upgrade it to 9.5 or higher b
 
 ### Enable CDC as a source
 
-- test_decoding logical decoding plugin captures the changed records from the source.
+- `test_decoding` logical decoding plugin captures the changed records from the source.
 - In the source, PostgreSQL instance, modify the following parameters by creating a new parameter group:
     - Set `rds.logical_replication = 1`
     - Set `max_replication_slots` to a value greater than one; the value should be greater than the number of databases selected for migration.
@@ -60,7 +60,7 @@ For more information on network setup, visit [Network guide for migration servic
 - Use the select command in the source to list all the extensions that are being used - `select extname, extversion from pg_extension;`
 - Search for azure.extensions server parameter on the Server parameter page on your Azure Database for PostgreSQL – Flexible server. Enable the extensions found in the source within the PostgreSQL flexible server.
 
-:::image type="content" source="../../media/tutorial-migration-service-aws-online/az-flexible-server-enable-extensions.png" alt-text="Screenshot of enable extensions":::
+:::image type="content" source="../../media/tutorial-migration-service-aws-online/az-flexible-server-enable-extensions.png" alt-text="Screenshot of enable extensions." lightbox="../../media/tutorial-migration-service-aws-online/az-flexible-server-enable-extensions.png":::
 
 - Check if the list contains any of the following extensions:
     - PG_CRON
@@ -82,5 +82,3 @@ If yes, search the server parameters page for the shared_preload_libraries param
 
 - The users and different roles must be migrated manually to the Azure Database for PostgreSQL – Flexible server. For migrating users and roles, you can use `pg_dumpall --globals-only -U <<username> -f <<filename>>.sql`.
 - Azure Database for PostgreSQL – The flexible server doesn't support any superuser; users having roles of superuser need to be removed before migration.
-
-

articles/postgresql/migrate/migration-service/media/tutorial-migration-service-aws-offline/portal-offline-connect-target-migration-aws.png

@@ -53,7 +53,7 @@ You can perform the migration by using the Azure portal or the Azure CLI.
 
 The Azure portal provides a simple and intuitive wizard-based experience that guides you through migration. Following the steps outlined in this tutorial, you can seamlessly transfer your database to Azure Database for PostgreSQL - Flexible Server and take advantage of its powerful features and scalability.
 
-To migrate with the Azure portal, you'll first configure the migration task, connect to the source and target, and then perform the migration.
+To migrate with the Azure portal, you first configure the migration task, connect to the source and target, and then perform the migration.
 
 ### Configure the migration task
 
@@ -140,7 +140,7 @@ The **select migration target** tab displays metadata for the Flexible Server ta
 
 After the successful test connection, select the **Next: Select Database(s) for Migration**
 
-:::image type="content" source="media/tutorial-migration-service-aws-offline/portal-offline-connect-target-migration-aws.png" alt-text="Screenshot of the connect target migration page.":::
+:::image type="content" source="media/tutorial-migration-service-aws-offline/portal-offline-connect-target-migration.png" alt-text="Screenshot of the connect target migration page.":::
 
 #### Select databases for migration
 
@@ -227,7 +227,6 @@ Copy other server settings, such as tags, alerts, and firewall rules (if applica
 
 You can cancel any ongoing validations or migrations. The workflow must be in the **InProgress** state to be canceled. You can't cancel a validation or migration that's in the **Succeeded** or **Failed** state.
 
-- Canceling a validation stops further validation activity, and the validation moves to a **Cancelled** state.
 - Canceling a migration stops further migration activity on your target server and moves to a **Cancelled** state. The cancel action rolls back all changes made by the migration service on your target server.
 
 #### [CLI](#tab/cli)

articles/postgresql/migrate/migration-service/media/tutorial-migration-service-aws-offline/portal-offline-fetchdb-migration.png

@@ -4,7 +4,7 @@ description: "Learn to migrate online seamlessly from AWS RDS to Azure Database
 author: apduvuri
 ms.author: adityaduvuri
 ms.reviewer: maghan
-ms.date: 06/20/2024
+ms.date: 06/12/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.topic: tutorial
@@ -65,11 +65,11 @@ The migration service comes with a simple, wizard-based experience on the Azure
 
 1. Select the **Create** button to migrate from AWS RDS to Azure Database for PostgreSQL - Flexible Server. If this is your first time using the migration service, an empty grid appears with a prompt to begin your first migration.
 
-    :::image type="content" source="media/tutorial-migration-service-aws-online/portal-online-create-migration.png" alt-text="Screenshot of creating a migration." lightbox="media/tutorial-migration-service-aws-online/portal-online-create-migration.png"::: image type="content" source="media/tutorial-migration-service-aws-online/portal-online-create-migration.png" alt-text="Screenshot of creating a migration."
+    :::image type="content" source="media/tutorial-migration-service-aws-online/portal-online-create-migration.png" alt-text="Screenshot of creating a migration." lightbox="media/tutorial-migration-service-aws-online/portal-online-create-migration.png":::
 
-  If you've already created migrations to your Azure Database for PostgreSQL - Flexible Server target, the grid contains information about attempted migrations.
+If you've already created migrations to your Azure Database for PostgreSQL target, the grid contains information about attempted migrations.
 
-1. Select the ** Create ** button. You'll then go through a wizard-based series of tabs to create a migration into this Azure Database for PostgreSQL—Flexible Server target from the PostgreSQL source instance.
+1. Select the **Create** button. You then go through a wizard-based series of tabs to create a migration into this Azure Database for PostgreSQL target from the PostgreSQL source instance.
 
 #### Setup
 
@@ -116,11 +116,11 @@ The **Connect to Source** tab prompts you to provide details related to the Sour
 
 After the successful test connection, select the **Next: Select Migration target**
 
-#### Select migration targett
+#### Select migration target
 
 The **select migration target** tab displays metadata for the Flexible Server target, such as the subscription name, resource group, server name, location, and PostgreSQL version.
 
-:::image type="content" source="media/tutorial-migration-service-aws-online/aws-connect-target.png" alt-text="Screenshot of Connecttargetmigration.":::
+:::image type="content" source="media/tutorial-migration-service-aws-online/aws-connect-target.png" alt-text="Screenshot of the connect target migration screen.":::
 
 - **Admin username** - Admin username of the target PostgreSQL server
 - **Password** - Password of the target PostgreSQL server
@@ -148,7 +148,7 @@ After you select the start button, a notification appears in a few seconds sayin
 
 :::image type="content" source="media/tutorial-migration-service-aws-online/aws-monitor.png" alt-text="Screenshot of Monitor migration." lightbox="media/tutorial-migration-service-aws-online/aws-monitor.png":::
 
-The grid that displays the migrations has these columns: **Name**, **Status**, **Migration mode**, **Migration type**, **Source server**, **Source server type**, **Databases**, **Duration, and **Start time**. The entries are displayed in the descending order of the start time, with the most recent entry at the top. You can use the refresh button to refresh the status of the validation or migration.
+The grid that displays the migrations has these columns: **Name**, **Status**, **Migration mode**, **Migration type**, **Source server**, **Source server type**, **Databases**, **Duration**, and **Start time**. The entries are displayed in the descending order of the start time, with the most recent entry at the top. You can use the refresh button to refresh the status of the validation or migration.
 Select the migration name in the grid to see the associated details.
 
 As soon as the validation or migration is created, it moves to the **InProgress** state and **PerformingPreRequisiteSteps** substrate. The workflow takes 2-3 minutes to set up the migration infrastructure and network connections.
@@ -249,7 +249,7 @@ For more information about this command, use the `help` parameter.
 
 #### Create target Azure Database for PostgreSQL
 
-We used the [Create an Azure Database for PostgreSQL Flexible Server instance](../../flexible-server/quickstart-create-server-portal.md) to create a corresponding PostgreSQL target flexible server. Below is the target server screenshot once created –
+We used the [Create an Azure Database for PostgreSQL Flexible Server instance](../../flexible-server/quickstart-create-server-portal.md) to create a corresponding PostgreSQL target flexible server.
 
 ### Migrate using Azure CLI
 
@@ -309,8 +309,8 @@ az postgres flexible-server migration update --subscription <<subscription ID>>
 
 You can cancel any ongoing validations or migrations. The workflow must be in the **InProgress** state to be canceled. You can't cancel a validation or migration in the **Succeeded** or **Failed** state.
 
-Canceling a validation stops any further validation activity and the validation moves to a **Can be celled** state.
-Canceling a migration stops further migration activity on your target server and moves to a **Can be celled** state. It doesn't drop or roll back any changes on your target server. Be sure to drop the databases on your target server that is involved in a canceled migration.
+Cancelling a validation stops any further validation activity and the validation moves to a **Cancelled** state.
+Cancelling a migration stops further migration activity on your target server and moves to a **Cancelled** state. It doesn't drop or roll back any changes on your target server. Be sure to drop the databases on your target server that is involved in a canceled migration.
 
 ### Check the migration when completed