updated syntax.

Author: AbdullahBell

articles/private-link/troubleshoot-private-link-connectivity.md

@@ -50,12 +50,12 @@ If you experience connectivity problems with your private link setup, review the
 
      - If the state is **Pending**, select it and approve it.
 
-    - Select the private endpoint you are connecting from by clicking on its name. Ensure the connection status is **Approved**.
+    - Select the private endpoint you're connecting from by clicking on its name. Ensure the connection status is **Approved**.
 
      - After both sides are approved, try the connectivity again.
 
     e. Review **Alias** on the **Overview** tab and **Resource ID** on the **Properties** tab.
-    - Ensure that the **Alias** and **Resource ID** details match the ones you are using to create a private endpoint for this service.
+    - Ensure that the **Alias** and **Resource ID** details match the ones you're using to create a private endpoint for this service.
 
     f. Review **Visibility** information on the **Overview** tab. Select **See more** in the overview pane to see the details.
 
@@ -65,7 +65,7 @@ If you experience connectivity problems with your private link setup, review the
 
      - View the load balancer by selecting the load balancer link in the *Overview* pane.
 
-     -Confirm the load balancer settings are configured as per your requirements.
+     - Confirm the load balancer settings are configured as per your requirements.
 
        - Review **Frontend IP configuration**.
 
@@ -75,9 +75,9 @@ If you experience connectivity problems with your private link setup, review the
 
      - Confirm load balancer is working as per the previous settings.
 
-      - Choose a VM located in a subnet different from the one where the load balancer back-end pool resides.  
+      - Choose a virtual machine located in a subnet different from the one where the load balancer back-end pool resides.  
 
-      - Access the load balancer front end from the previous VM.
+      - Access the load balancer front end from the previous virtual machine.
 
       - If the connection reaches the back-end pool according to the load-balancing rules, then your load balancer is functioning correctly.    
 
@@ -109,6 +109,6 @@ Contact the [Azure Support](https://portal.azure.com/#blade/Microsoft_Azure_Supp
 
 ## Next steps
 
- * [Create a private link service (CLI)](./create-private-link-service-cli.md)
+* [Create a private link service (CLI)](./create-private-link-service-cli.md)
 
 * [Azure Private Endpoint troubleshooting guide](troubleshoot-private-endpoint-connectivity.md)

articles/private-link/tutorial-private-endpoint-sql-cli.md

@@ -49,9 +49,9 @@ az group create \
 
 ## Create a virtual network and bastion host
 
-In this section, you'll create a virtual network, subnet, and bastion host. 
+In this section, you create a virtual network, subnet, and bastion host. 
 
-The bastion host will be used to connect securely to the virtual machine for testing the private endpoint.
+The bastion host is used to connect securely to the virtual machine for testing the private endpoint.
 
 Create a virtual network with [az network vnet create](/cli/azure/network/vnet#az-network-vnet-create)
 
@@ -130,7 +130,7 @@ It can take a few minutes for the Azure Bastion host to deploy.
 
 ## Create test virtual machine
 
-In this section, you'll create a virtual machine that will be used to test the private endpoint.
+In this section, you create a virtual machine that is used to test the private endpoint.
 
 Create a VM with [az vm create](/cli/azure/vm#az-vm-create). When prompted, provide a password to be used as the credentials for the VM:
 
@@ -155,7 +155,7 @@ az vm create \
 
 ## Create an Azure SQL server
 
-In this section, you'll create a SQL server and database.
+In this section, you create a SQL server and database.
 
 Use [az sql server create](/cli/azure/sql/server#az-sql-server-create) to create a SQL server:
 
@@ -189,7 +189,7 @@ az sql db create \
 
 ## Create private endpoint
 
-In this section, you'll create the private endpoint.
+In this section, you create the private endpoint.
 
 Use [az sql server list](/cli/azure/sql/server#az-sql-server-list) to place the resource ID of the SQL server into a shell variable.
 
@@ -220,9 +220,9 @@ az network private-endpoint create \
 
 In this section, you'll create and configure the private DNS zone using [az network private-dns zone create](/cli/azure/network/private-dns/zone#az-network-private-dns-zone-create).  
 
-You'll use [az network private-dns link vnet create](/cli/azure/network/private-dns/link/vnet#az-network-private-dns-link-vnet-create) to create the virtual network link to the dns zone.
+You use [az network private-dns link vnet create](/cli/azure/network/private-dns/link/vnet#az-network-private-dns-link-vnet-create) to create the virtual network link to the dns zone.
 
-You'll create a dns zone group with [az network private-endpoint dns-zone-group create](/cli/azure/network/private-endpoint/dns-zone-group#az-network-private-endpoint-dns-zone-group-create).
+You create a dns zone group with [az network private-endpoint dns-zone-group create](/cli/azure/network/private-endpoint/dns-zone-group#az-network-private-endpoint-dns-zone-group-create).
 
 * Zone named **privatelink.database.windows.net**
 * In virtual network **myVNet**.
@@ -253,7 +253,7 @@ az network private-endpoint dns-zone-group create \
 
 ## Test connectivity to private endpoint
 
-In this section, you'll use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
+In this section, you use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -271,7 +271,7 @@ In this section, you'll use the virtual machine you created in the previous step
 
 8. Open Windows PowerShell on the server after you connect.
 
-9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps.  You'll receive a message similar to what is displayed below:
+9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps. You receive a message similar to what is displayed below:
 
     ```powershell
     Server:  UnKnown
@@ -283,7 +283,7 @@ In this section, you'll use the virtual machine you created in the previous step
     Aliases:  mysqlserver8675.database.windows.net
     ```
 
-    A private IP address of **10.0.0.5** is returned for the SQL server name.  This address is in the subnet of the virtual network you created previously.
+    A private IP address of **10.0.0.5** is returned for the SQL server name. This address is in the subnet of the virtual network you created previously.
 
 
 10. Install [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms?preserve-view=true&view=sql-server-2017) on **myVM**.
@@ -328,6 +328,6 @@ In this tutorial, you created a:
 
 You used the virtual machine to test connectivity securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL database](/azure/architecture/example-scenario/private-web-app/private-web-app)

articles/private-link/tutorial-private-endpoint-sql-portal.md

@@ -47,7 +47,7 @@ In this section, you create a SQL server in Azure.
 
 1. In **SQL databases**, select **+ Create**.
 
-1. In the **Basics** tab of **Create SQL Database**, enter or select the following information:
+1. In the **Basics** tab of **Create SQL Database**, enter, or select the following information:
 
     | Setting | Value |
     |---|---|
@@ -64,7 +64,7 @@ In this section, you create a SQL server in Azure.
 
 1. Select **Next: Networking**.
 
-1. In the **Networking** tab of **Create SQL Database**, enter or select the following information:
+1. In the **Networking** tab of **Create SQL Database**, enter, or select the following information:
 
     | Setting | Value |
     |---|---|
@@ -92,7 +92,7 @@ In this section, you create a SQL server in Azure.
 1. Select **Create**.
 
 > [!IMPORTANT]
-> When adding a Private endpoint connection, public routing to your Azure SQL server is not blocked by default. The setting "Deny public network access" under the "Firewall and virtual networks" blade is left unchecked by default. To disable public network access ensure this is checked.
+> When adding a Private endpoint connection, public routing to your Azure SQL server isn't blocked by default. The setting "Deny public network access" under the "Firewall and virtual networks" blade is left unchecked by default. To disable public network access, ensure this is checked.
  
 ## Disable public access to Azure SQL logical server
 
@@ -169,6 +169,6 @@ In this tutorial, you learned how to create:
 
 You used the virtual machine to test connectivity privately and securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL Database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL Database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL Database](/azure/architecture/example-scenario/private-web-app/private-web-app)

articles/private-link/tutorial-private-endpoint-sql-powershell.md

@@ -42,9 +42,9 @@ New-AzResourceGroup -Name 'CreateSQLEndpointTutorial-rg' -Location 'eastus'
 
 ## Create a virtual network and bastion host
 
-In this section, you'll create a virtual network, subnet, and bastion host. 
+In this section, you create a virtual network, subnet, and bastion host. 
 
-The bastion host will be used to connect securely to the virtual machine for testing the private endpoint.
+The bastion host is used to connect securely to the virtual machine for testing the private endpoint.
 
 Create a virtual network and bastion host with:
 
@@ -93,7 +93,7 @@ It can take a few minutes for the Azure Bastion host to deploy.
 
 ## Create test virtual machine
 
-In this section, you'll create a virtual machine that will be used to test the private endpoint.
+In this section, you create a virtual machine that is used to test the private endpoint.
 
 Create the virtual machine with:
 
@@ -148,7 +148,7 @@ New-AzVM -ResourceGroupName 'CreateSQLEndpointTutorial-rg' -Location 'eastus' -V
 
 ## Create an Azure SQL server
 
-In this section, you'll create a SQL server and database using:
+In this section, you create a SQL server and database using:
 
 * [New-AzSqlServer](/powershell/module/az.sql/new-azsqlserver)
 * [New-AzSQlDatabase](/powershell/module/az.sql/new-azsqldatabase)
@@ -181,7 +181,7 @@ New-AzSqlDatabase @parameters2
 
 ## Create private endpoint
 
-In this section, you'll create the private endpoint and connection using:
+In this section, you create the private endpoint and connection using:
 
 * [New-AzPrivateLinkServiceConnection](/powershell/module/az.network/New-AzPrivateLinkServiceConnection)
 * [New-AzPrivateEndpoint](/powershell/module/az.network/new-azprivateendpoint)
@@ -217,7 +217,7 @@ New-AzPrivateEndpoint @parameters2
 ```
 ## Configure the private DNS zone
 
-In this section you'll create and configure the private DNS zone using:
+In this section you create and configure the private DNS zone using:
 
 * [New-AzPrivateDnsZone](/powershell/module/az.privatedns/new-azprivatednszone)
 * [New-AzPrivateDnsVirtualNetworkLink](/powershell/module/az.privatedns/new-azprivatednsvirtualnetworklink)
@@ -263,7 +263,7 @@ New-AzPrivateDnsZoneGroup @parameters4
 
 ## Test connectivity to private endpoint
 
-In this section, you'll use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
+In this section, you use the virtual machine you created in the previous step to connect to the SQL server across the private endpoint.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -281,7 +281,7 @@ In this section, you'll use the virtual machine you created in the previous step
 
 8. Open Windows PowerShell on the server after you connect.
 
-9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps.  You'll receive a message similar to what is displayed below:
+9. Enter `nslookup <sqlserver-name>.database.windows.net`. Replace **\<sqlserver-name>** with the name of the SQL server you created in the previous steps. You receive a message similar to what is displayed below:
 
     ```powershell
     Server:  UnKnown
@@ -293,7 +293,7 @@ In this section, you'll use the virtual machine you created in the previous step
     Aliases:  mysqlserver8675.database.windows.net
     ```
 
-    A private IP address of **10.0.0.5** is returned for the SQL server name.  This address is in the subnet of the virtual network you created previously.
+    A private IP address of **10.0.0.5** is returned for the SQL server name. This address is in the subnet of the virtual network you created previously.
 
 
 10. Install [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms?preserve-view=true&view=sql-server-2017) on **myVM**.
@@ -338,6 +338,6 @@ In this tutorial, you created a:
 
 You used the virtual machine to test connectivity securely to the SQL server across the private endpoint.
 
-As a next step, you may also be interested in the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
+As a next step, review the **Web app with private connectivity to Azure SQL database** architecture scenario, which connects a web application outside of the virtual network to the private endpoint of a database.
 > [!div class="nextstepaction"]
 > [Web app with private connectivity to Azure SQL database](/azure/architecture/example-scenario/private-web-app/private-web-app)