Merge pull request #282698 from hariramt/task/MigrationdocUpdate-31stJuly2024

Minor typo and content update

Author: prmerger-automator[bot]

articles/postgresql/migrate/automigration-single-to-flexible-postgresql.md

@@ -29,7 +29,7 @@ The automigration provides a highly resilient and self-healing offline migration
 
 - The **migrated Flexible Server is online** and can now be managed via Azure portal/CLI.
 
-- The **updated connection strings** to connect to your old single server are shared with you by email. The connection strings can be used to log in to the Single server if you want to copy any settings to your new Flexible server.
+- The **updated connection strings** to connect to your old single server are shared with you by email if you have enabled Service health notifications on the Azure portal. Alternatively, you can find the connection strings in the Single server portal page under **Settings->Connection strings**. The connection strings can be used to log in to the Single server if you want to copy any settings to your new Flexible server.
 
 - The **legacy Single Server** is deleted **seven days** after the migration.
 

articles/postgresql/migrate/migration-service/includes/single-server/postgresql-single-server-portal-migrate.md

@@ -384,7 +384,7 @@ You can see the results of **Validate and Migrate** once the operation is comple
 
 ### Cutover migration
 
-For the **Migrate** and for the **Validate and Migrate** migration options, completion of the online migration requires the user to complete an additional step, which is to trigger the Cutover action. After the copy/clone of the base data is complete, the migration moves to the **WaitingForUserAction** state and the `**aitingForCutoverTrigger** substate. In this state, user can trigger cutover from the portal by selecting the migration, and selecting the **Cutover** button.
+For the **Migrate** and for the **Validate and Migrate** migration options, completion of the online migration requires the user to complete an additional step, which is to trigger the Cutover action. After the copy/clone of the base data is complete, the migration moves to the **WaitingForUserAction** state and the `**WaitingForCutoverTrigger** substate. In this state, user can trigger cutover from the portal by selecting the migration, and selecting the **Cutover** button.
 
 Before initiating cutover, it's essential to ensure that: