Apply suggestions from code review

Author: JillGrant615

articles/postgresql/flexible-server/how-to-create-read-replica.md

@@ -97,7 +97,7 @@ Using the [Azure portal](https://portal.azure.com/):
 
 8.  A new deployment is launched to create your new Azure Database for PostgreSQL flexible server and make it a read replica of the primary server.
 
-    :::image type="content" source="./media/how-to-read-replicas/create-replica-deployment-progress.png" alt-text="Screenshot that shows the deployment in progress to create your new Azure Database for PostgreSQL flexible server" lightbox="./media/how-to-read-replicas/create-replica-deployment-progress.png":::
+    :::image type="content" source="./media/how-to-read-replicas/create-replica-deployment-progress.png" alt-text="Screenshot that shows the deployment in progress to create your new Azure Database for PostgreSQL flexible server." lightbox="./media/how-to-read-replicas/create-replica-deployment-progress.png":::
 
 9. When the deployment completes, you can select **Go to resource**, to start using your new Azure Database for PostgreSQL flexible server.
 

articles/postgresql/flexible-server/how-to-create-virtual-endpoints.md

@@ -36,7 +36,7 @@ Using the [Azure portal](https://portal.azure.com/):
 
     :::image type="content" source="./media/how-to-read-replicas/virtual-endpoints-base-name.png" alt-text="Screenshot showing where to enter the virtual endpoints base name." lightbox="./media/how-to-read-replicas/virtual-endpoints-base-name.png":::
 
-5. **Target of writer virtual endpoint** must always point to the primary server, because that's the only server that is configured to support user initiated write operations. If the server on on which you're creating the virtual endpoints don't have any read replica, then **Target of reader virtual endpoint** also points to the primary server. However, if the server on which you're creating the virtual endpoints has some read replica, by default **Target of reader virtual endpoint** is pointed to one of the read replicas, and can be changed to point to the primary server or to any other read replica, provided there's more than one.
+5. **Target of writer virtual endpoint** must always point to the primary server, because that's the only server that is configured to support user initiated write operations. If the server on which you're creating the virtual endpoints don't have any read replica, then **Target of reader virtual endpoint** also points to the primary server. However, if the server on which you're creating the virtual endpoints has some read replica, by default **Target of reader virtual endpoint** is pointed to one of the read replicas, and can be changed to point to the primary server or to any other read replica, provided there's more than one.
 
     :::image type="content" source="./media/how-to-read-replicas/target-of-reader-virtual-endpoint.png" alt-text="Screenshot showing how the Target of reader virtual endpoint refers to a read replica when there's one configured." lightbox="./media/how-to-read-replicas/target-of-reader-virtual-endpoint.png":::
 

articles/postgresql/flexible-server/how-to-promote-replica-to-standalone.md

@@ -14,7 +14,7 @@ ms.topic: how-to
 
 [!INCLUDE [applies-to-postgresql-flexible-server](~/reusable-content/ce-skilling/azure/includes/postgresql/includes/applies-to-postgresql-flexible-server.md)]
 
-This article provides step-by-step instructions to swicth over a read replica of an Azure Database for PostgreSQL flexible server so that it becomes the new primary server of the replication set.
+This article provides step-by-step instructions to switch over a read replica of an Azure Database for PostgreSQL flexible server so that it becomes the new primary server of the replication set.
 
 ## Steps to promote replica to standalone server
 
@@ -32,7 +32,7 @@ Using the [Azure portal](https://portal.azure.com/):
 
     :::image type="content" source="./media/how-to-read-replicas/switch-over-or-promote-to-standalone.png" alt-text="Screenshot showing the Switch over or Promote to standalone pane." lightbox="./media/how-to-read-replicas/switch-over-or-promote-to-standalone.png":::
 
-4. In **Replica server to promote**, select **Promote to independent server and remove from replication. This won't impact the primary server.** for **Action**. And select **Planned** or **Forced** for **Data sync**, depending on what suits your needs best. if you decide to use the **Planned** option, you have to mark the **I understand that this read replica will become an independent server and that this action can't be undone.** to acknowledge that the read replica will be dettached into its own standalone entity. If you decide to use the **Forced** option, you have to mark the **I understand that this read replica will become an independent server and that its data won't be synced first. This action can't be undone.** checkbox to also acknowledge the potential data loss. Finally, select **Promote**.
+4. In **Replica server to promote**, select **Promote to independent server and remove from replication. This won't impact the primary server.** for **Action**. And select **Planned** or **Forced** for **Data sync**, depending on what suits your needs best. if you decide to use the **Planned** option, you have to mark the **I understand that this read replica will become an independent server and that this action can't be undone.** to acknowledge that the read replica will be detached into its own standalone entity. If you decide to use the **Forced** option, you have to mark the **I understand that this read replica will become an independent server and that its data won't be synced first. This action can't be undone.** checkbox to also acknowledge the potential data loss. Finally, select **Promote**.
 
     :::image type="content" source="./media/how-to-read-replicas/promote-to-standalone.png" alt-text="Screenshot showing the Promote to standalone pane." lightbox="./media/how-to-read-replicas/promote-to-standalone.png":::
 

articles/postgresql/flexible-server/how-to-switch-over-replica-to-primary.md

@@ -14,7 +14,7 @@ ms.topic: how-to
 
 [!INCLUDE [applies-to-postgresql-flexible-server](~/reusable-content/ce-skilling/azure/includes/postgresql/includes/applies-to-postgresql-flexible-server.md)]
 
-This article provides step-by-step instructions to swicth over a read replica of an Azure Database for PostgreSQL flexible server so that it becomes the new primary server of the replication set.
+This article provides step-by-step instructions to switch over a read replica of an Azure Database for PostgreSQL flexible server so that it becomes the new primary server of the replication set.
 
 ## Steps to switch over read replica to primary