Merge pull request #231305 from GennadNY/gennadyk898

Gennadyk898

Author: v-dirichards

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)*.
 
@@ -27,17 +27,17 @@ To create a flexible server in a virtual network, you need:
 - A [Virtual Network](../../virtual-network/quick-create-portal.md#create-a-virtual-network)
     > [!Note]
     > -  The virtual network and subnet should be in the same region and subscription as your flexible server.
-    > -  The virtual network should not have any resource lock set at the VNET or subnet level. Make sure to remove any lock (**Delete** or **Read only**) from your VNET and all subnets before creating the server in a virtual network, and you can set it back after server creation.
+    > -  The virtual network should not have any resource lock set at the VNET or subnet level, as locks may interfere with operations on the network and DNS.  Make sure to remove any lock (**Delete** or **Read only**) from your VNET and all subnets before creating the server in a virtual network, and you can set it back after server creation.
 
 -  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.

articles/postgresql/flexible-server/tutorial-django-app-service-postgres.md

@@ -76,16 +76,16 @@ These changes are specific to configuring Django to run in any production enviro
 Create a private flexible server and a database inside a virtual network (VNET) using the following command:
 
 ```azurecli
-# Create Flexible server in a VNET
+# Create Flexible server in a private virtual network (VNET) 
 
-az postgres flexible-server create --resource-group myresourcegroup --location westus2
+az postgres flexible-server create --resource-group myresourcegroup  --vnet myvnet --location westus2
 ```
 
 This command performs the following actions, which may take a few minutes:
 
 - Create the resource group if it doesn't already exist.
 - Generates a server name if it isn't provided.
-- Create a new virtual network for your new postgreSQL server. **Make a note of virtual network name and subnet name** created for your server since you need to add the web app to the same virtual network.
+- Create a new virtual network for your new postgreSQL server, if you choose to do so after prompted. **Make a note of virtual network name and subnet name** created for your server since you need to add the web app to the same virtual network.
 - Creates admin username, password for your server if not provided. **Make a note of the username and password** to use in the next step.
 - Create a database ```postgres``` that can be used for development. You can run [**psql** to connect to the database](quickstart-create-server-portal.md#connect-to-the-postgresql-database-using-psql) to create a different database.
 
@@ -156,11 +156,11 @@ Django database migrations ensure that the schema in the PostgreSQL on Azure dat
 
 ### Create a poll question in the app
 
-4. In a browser, open the URL *http:\//\<app-name>.azurewebsites.net*. The app should display the message "No polls are available" because there are no specific polls yet in the database.
+1. In a browser, open the URL *http:\//\<app-name>.azurewebsites.net*. The app should display the message "No polls are available" because there are no specific polls yet in the database.
 
-5. Browse to *http:\//\<app-name>.azurewebsites.net/admin*. Sign in using superuser credentials from the previous section (`root` and `postgres1`). Under **Polls**, select **Add** next to **Questions** and create a poll question with some choices.
+2. Browse to *http:\//\<app-name>.azurewebsites.net/admin*. Sign in using superuser credentials from the previous section (`root` and `postgres1`). Under **Polls**, select **Add** next to **Questions** and create a poll question with some choices.
 
-6. Browse again to *http:\//\<app-name>.azurewebsites.net/* to confirm that the questions are now presented to the user. Answer questions however you like to generate some data in the database.
+3. Browse again to *http:\//\<app-name>.azurewebsites.net/* to confirm that the questions are now presented to the user. Answer questions however you like to generate some data in the database.
 
 **Congratulations!** You're running a Python Django web app in Azure App Service for Linux, with an active Postgres database.
 
@@ -261,7 +261,7 @@ python manage.py migrate
 
 ### Review app in production
 
-Browse to *http:\//\<app-name>.azurewebsites.net* and test the app again in production. (Because you only changed the length of a database field, the change is only noticeable if you try to enter a longer response when creation a question.)
+Browse to *http:\//\<app-name>.azurewebsites.net* and test the app again in production. (Because you only changed the length of a database field, the change is only noticeable if you try to enter a longer response when creating a question.)
 
 > [!TIP]
 > You can use [django-storages](https://django-storages.readthedocs.io/en/latest/backends/azure.html) to store static & media assets in Azure storage. You can use Azure CDN for gzipping for static files.