Merge pull request #176738 from v-rajagt/jasonh-oct-18

Broken link fixed.

Author: PRMerger5

articles/hdinsight/network-virtual-appliance.md

@@ -13,7 +13,7 @@ ms.date: 06/30/2020
 
 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:
 
-* Service Endpoint capable services can be configured with service endpoints which results in bypassing the NVA, usually for cost or performance considerations.
+* 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.
 * IP Address dependencies are for non-HTTP/S traffic (both TCP and UDP traffic).
 * FQDN HTTP/HTTPS endpoints can be approved in your NVA device.
@@ -39,7 +39,7 @@ You can optionally enable one or more of the following service endpoints which w
 
 ### FQDN HTTP/HTTPS dependencies
 
-You can get the list of FQDNs dependencies (mostly Azure Storage and Azure Service Bus) for configuring your NVA [in this repo](https://github.com/Azure-Samples/hdinsight-fqdn-lists/). For the regional list see [here](https://github.com/Azure-Samples/hdinsight-fqdn-lists/tree/master/Regional). These dependencies are used by HDInsight resource provider(RP) to create and monitor/manage clusters successfully. These include telemetry/diagnostic logs, provisioning metadata, cluster related configurations, scripts, etc. This FQDN dependency list might change with releasing future HDInsight updates.
+You can get the list of dependent FQDNs (mostly Azure Storage and Azure Service Bus) for configuring your network virtual appliance [in this repo](https://github.com/Azure-Samples/hdinsight-fqdn-lists/). For the regional list see [here](https://github.com/Azure-Samples/hdinsight-fqdn-lists/tree/main/Public). These dependencies are used by HDInsight resource provider(RP) to create and monitor/manage clusters successfully. These include telemetry/diagnostic logs, provisioning metadata, cluster-related configurations, scripts, etc. This FQDN dependency list might change with releasing future HDInsight updates.
 
 The list below only gives a few FQDNs that may be needed for OS and security patching or certificate validations *after* the cluster is created and during the lifetime of cluster operations: