Update private-endpoint.md

little improvments

Author: Ericgre

articles/app-service/networking/private-endpoint.md

@@ -1,6 +1,6 @@
 ---
-title: Connect privately to a Web App and secure data exfiltration using Azure Private Endpoint
-description: Connect privately to a Web App and secure data exfiltration using Azure Private Endpoint
+title: Connect privately to a Web App using Azure Private Endpoint
+description: Connect privately to a Web App using Azure Private Endpoint
 author: ericgre
 ms.assetid: 2dceac28-1ba6-4904-a15d-9e91d5ee162c
 ms.topic: article
@@ -13,14 +13,14 @@ ms.workload: web
 
 # Using Private Endpoints for Azure Web App (Preview)
 
-You can use Private Endpoint for your Azure Web App to allow clients located in your private network to securely access to the app over Private Link. The Private Endpoint uses an IP address from your Azure VNet address space. Network traffic between client on your private network and the Web App traverses over the Vnet and a Private Link on the Microsoft backbone network, eliminating exposure from the public Internet. With Private Endpoint, you can disable outgoing network flows from the subnet with NSG and eliminate the data leakage risk.
+You can use Private Endpoint for your Azure Web App to allow clients located in your private network to securely access to the app over Private Link. The Private Endpoint uses an IP address from your Azure VNet address space. Network traffic between client on your private network and the Web App traverses over the Vnet and a Private Link on the Microsoft backbone network, eliminating exposure from the public Internet.
 
 Using Private Endpoint for your Web App enables you to:
 
 - Secure your Web App by configuring the Service Endpoint, eliminating public exposure
 - Securely connect to Web App from on-premises networks that connect to the Vnet using a VPN or ExpressRoute private peering.
 
-If you just need a secure connection between your Vnet and your Web App, Service Endpoint is the simplest solution. if you also need to reach the web app from on-premises, Private Endpoint is the solution.  
+If you just need a secure connection between your Vnet and your Web App, Service Endpoint is the simplest solution. If you also need to reach the web app from on-premises through an Azure gateway, a regionally peered Vnet or a globally peered Vnet, Private Endpoint is the solution.  
 
 For more information about [Service Endpoint][serviceendpoint]
 
@@ -31,23 +31,24 @@ When you create a Private Endpoint for your Web App, it provides a secure connec
 The connection between the Private Endpoint and the Web App uses a secure [Private Link][privatelink]. Private endpoint is only used for incoming flows to your Web App. Outgoing flows will not use this Private Endpoint, but you can inject outgoing flows to your network in a different subnet through the [Vnet integration feature][vnetintegrationfeature].
 
 The Subnet where you plug the Private Endpoint can have other resources in it, you don't need a dedicated empty Subnet.
-You can deploy Private Endpoint in region A for the Web App deployed in region B. 
+You can deploy Private Endpoint in a different region than the Web App. 
 
 > [!Note]
 >The Vnet integration feature cannot use the same subnet than Private Endpoint, this is a limitation of the Vnet integration feature
 
 From the security perspective:
 
 - When you enable Service Endpoint to your Web App, you disable all public access
-- You can enable multiple Private Endpoints in others Vnets and Subnets
+- You can enable multiple Private Endpoints in others Vnets and Subnets, including Vnets in other regions
+- The IP address of the Private endpoint NIC must be dynamic, but will remain the same until you delete the Private Endpoint
 - The NIC of the Private Endpoint cannot have an NSG associated
-- The Subnet that hosts the Private Endpoint can have an NSG associated, but you must disable the network policies enforcement for the Private Endpoint see [this article] [disablesecuritype]. As a result, you cannot filter by any NSG the access to your Private Endpoint.
+- The Subnet that hosts the Private Endpoint can have an NSG associated, but you must disable the network policies enforcement for the Private Endpoint see [this article] [disablesecuritype]. As a result, you cannot filter by any NSG the access to your Private Endpoint
 - When you enable Private Endpoint to your Web App, the [access restrictions][accessrestrictions] configuration of the Web App is not evaluated.
-- You can reduce data exfiltration from the vnet by removing all NSG rules where destination is tag Internet or Azure services, but adding a Service Endpoint in your subnet will allow you to reach any Web App hosted in the same stamp and exposed to Internet.
+- You can reduce data exfiltration risk from the vnet by removing all NSG rules where destination is tag Internet or Azure services. But adding a Web App Service Endpoint in your subnet, will let you reach any Web App hosted in the same stamp and exposed to Internet.
 
 Private Endpoint for Web App is available for tier PremiumV2, and Isolated with an external ASE.
 
-In the Web http logs of your Web App, you will discover that we are aware of the client source IP. We implemented the TCP Proxy protocol, forwarding up to the Web App the client IP. For more information, see [this article][tcpproxy].
+In the Web http logs of your Web App, you will find the client source IP. We implemented the TCP Proxy protocol, forwarding up to the Web App the client IP property. For more information, see [this article][tcpproxy].
 
 ![Global overview][1]