Update how-to-restore-server-cli.md

Author: kabharati

articles/postgresql/flexible-server/how-to-restore-server-cli.md

@@ -10,16 +10,16 @@ ms.topic: how-to
 ms.date: 11/30/2021
 ---
 
-# Point-in-time restore of a Azure Database for PostgreSQL - Flexible Server with Azure CLI
+# Point-in-time restore of an Azure Database for PostgreSQL - Flexible Server with Azure CLI
 
-[!INCLUDE [!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
+[! INCLUDE [!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
 
 This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups.
 
 ## Prerequisites
 - If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
 - Install or upgrade Azure CLI to the latest version. See [Install Azure CLI](/cli/azure/install-azure-cli).
--  Login to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
+-  Log in to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
 
     ```azurecli-interactive
     az login
@@ -31,7 +31,7 @@ This article provides step-by-step procedure to perform point-in-time recoveries
     az account set --subscription <subscription id>
     ```
 
-- Create a PostgreQL Flexible Server if you have not already created one using the ```az postgres flexible-server create``` command.
+- Create a PostgreQL Flexible Server if you haven't already created one using the ```az postgres flexible-server create``` command.
 
     ```azurecli
     az postgres flexible-server create --resource-group myresourcegroup --name myservername
@@ -70,7 +70,7 @@ Time taken to restore will depend on the size of the data stored in the server.
 After the restore is completed, you should perform the following tasks to get your users and applications back up and running:
 
 - If the new server is meant to replace the original server, redirect clients and client applications to the new server
-- Ensure appropriate VNet rules are in place for users to connect. These rules are not copied over from the original server.
+- Ensure appropriate VNet rules are in place for users to connect. These rules aren't copied over from the original server.
 - Ensure appropriate logins and database level permissions are in place
 - Configure alerts as appropriate for the newly restore server