Update network-virtual-appliance.md

Author: v-akarnase

articles/hdinsight/network-virtual-appliance.md

@@ -1,17 +1,17 @@
 ---
 title: Configure network virtual appliance in Azure HDInsight
-description: Learn how to configure a number of additional features for your network virtual appliance in Azure HDInsight.
+description: Learn how to configure many additional features for your network virtual appliance in Azure HDInsight.
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 09/19/2023
+ms.date: 09/20/2023
 ---
 
 # Configure network virtual appliance in Azure HDInsight
 
 > [!Important]
 > The following information is **only** required if you wish to configure a network virtual appliance (NVA) other than [Azure Firewall](./hdinsight-restrict-outbound-traffic.md).
 
-Azure Firewall FQDN tag is automatically configured to allow traffic for many of the common important FQDNs. Using another network virtual appliance will require you to configure a number of additional features. Keep the following factors in mind as you configure your network virtual appliance:
+Azure Firewall FQDN tag is automatically configured to allow traffic for many of the common important FQDNs. Using another network virtual appliance requires you to configure a number of additional features. Keep the following factors in mind as you configure your network virtual appliance:
 
 * Service Endpoint capable services can be configured with service endpoints that results in bypassing the NVA, usually for cost or performance considerations.
 * If ResourceProviderConnection is set to *outbound*, you can use private endpoints for the storage and SQL servers for metastores and there is no need to add them to the NVA.
@@ -21,7 +21,7 @@ Azure Firewall FQDN tag is automatically configured to allow traffic for many of
 
 ## Service endpoint capable dependencies
 
-You can optionally enable one or more of the following service endpoints which will result in bypassing the NVA. This option can be useful for large amounts of data transfers to save on cost and also for performance optimizations. 
+You can optionally enable one or more of the following service endpoints, which result in bypassing the NVA. This option can be useful for large amounts of data transfers to save on cost and also for performance optimizations. 
 
 | **Endpoint** |
 |---|
@@ -33,7 +33,7 @@ You can optionally enable one or more of the following service endpoints which w
 
 | **Endpoint** | **Details** |
 |---|---|
-| IPs published [here](hdinsight-management-ip-addresses.md) | These IPs are for HDInsight resource provider and should be included in the UDR to avoid asymmetric routing. This rule is only needed if the ResourceProviderConnection is set to *Inbound*. If the ResourceProviderConnection is set to *Outbound* then these IPs are not needed in the UDR.  |
+| IPs published [here](hdinsight-management-ip-addresses.md) | These IPs are for HDInsight resource provider and should be included in the UDR to avoid asymmetric routing. This rule is only needed if the ResourceProviderConnection is set to *Inbound*. If the ResourceProviderConnection is set to *Outbound*, then these IPs are not needed in the UDR.  |
 | AAD-DS private IPs | Only needed for ESP clusters, if the VNETs are not peered.|