Update how-to-manage-virtual-network-portal.md

Author: GennadNY

articles/postgresql/flexible-server/how-to-manage-virtual-network-portal.md

@@ -18,7 +18,7 @@ Azure Database for PostgreSQL - Flexible Server supports two types of mutually e
 * Public access (allowed IP addresses)
 * Private access (VNet Integration)
 
-In this article, we will focus on creation of PostgreSQL server with **Private access (VNet integration)** using Azure portal. With Private access (VNet Integration), you can deploy your flexible server into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. With private access, connections to the PostgreSQL server are restricted to your virtual network. To learn more about it, refer to [Private access (VNet Integration)](./concepts-networking.md#private-access-vnet-integration).
+In this article, we focus on creation of PostgreSQL server with **Private access (VNet integration)** using Azure portal. With Private access (VNet Integration), you can deploy your flexible server into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. With private access, connections to the PostgreSQL server are restricted to your virtual network. To learn more about it, refer to [Private access (VNet Integration)](./concepts-networking.md#private-access-vnet-integration).
 
 You can deploy your flexible server into a virtual network and subnet during server creation. After the flexible server is deployed, you cannot move it into another virtual network, subnet or to *Public access (allowed IP addresses)*.
 
@@ -32,12 +32,12 @@ To create a flexible server in a virtual network, you need:
 -  To [delegate a subnet](../../virtual-network/manage-subnet-delegation.md#delegate-a-subnet-to-an-azure-service) to **Microsoft.DBforPostgreSQL/flexibleServers**. This delegation means that only Azure Database for PostgreSQL Flexible Servers can use that subnet. No other Azure resource types can be in the delegated subnet.
 -  Add `Microsoft.Storage` to the service end point for the subnet delegated to Flexible servers. This is done by performing following steps:
      1. Go to your virtual network page.
-     2. Select the VNET in which you are planning to deploy your flexible server.
+     2. Select the VNET in which you're planning to deploy your flexible server.
      3. Choose the subnet that is delegated for flexible server.
      4. On the pull-out screen, under **Service endpoint**, choose `Microsoft.storage` from the drop-down.
      5. Save the changes.
 
-- If you want to setup your own private DNS zone to use with the flexible server, please see [private DNS overview](../../dns/private-dns-overview.md) documentation for more details. 
+- If you want to set up your own private DNS zone to use with the flexible server, see [private DNS overview](../../dns/private-dns-overview.md) documentation for more details. 
 
 ## Create Azure Database for PostgreSQL - Flexible Server in an already existing virtual network
 
@@ -46,14 +46,14 @@ To create a flexible server in a virtual network, you need:
 3. Select **Flexible server** as the deployment option.
 4. Fill out the **Basics** form.
 5. Go to the **Networking** tab to configure how you want to connect to your server.
-6. In the **Connectivity method**, select **Private access (VNet Integration)**. Go to **Virtual Network** and select the already existing *virtual network* and *Subnet* created as part of prerequisites above.
+6. In the **Connectivity method**, select **Private access (VNet Integration)**. Go to **Virtual Network** and select the already existing *virtual network* and *Subnet* created as part of prerequisites.
 7. Under **Private DNS Integration**,  by default, a new private DNS zone will be created using the server name. Optionally, you can choose the *subscription* and the *Private DNS zone* from the drop-down list.
 8. Select **Review + create** to review your flexible server configuration.
 9. Select **Create** to provision the server. Provisioning can take a few minutes.
 :::image type="content" source="./media/how-to-manage-virtual-network-portal/how-to-inject-flexible-server-vnet.png" alt-text="Injecting flexible server into a VNET":::
 
 >[!Note]
-> After the flexible server is deployed to a virtual network and subnet, you cannot move it to Public access (allowed IP addresses).
+> After the flexible server is deployed to a virtual network and subnet, you can't move it to Public access (allowed IP addresses).
 
 >[!Note]
 > If you want to connect to the flexible server from a client that is provisioned in another VNET, you have to link the private DNS zone with the VNET. See this [linking the virtual network](../../dns/private-dns-getstarted-portal.md#link-the-virtual-network) documentation on how to do it.