azdns

Author: greg-lindsay

articles/dns/dns-overview.md

@@ -11,7 +11,7 @@ ms.author: greglin
 
 # What is Azure DNS?
 
-The Domain Name System (DNS) is responsible for translating (resolving) a service name to an IP address.  Azure DNS provides DNS hosting, resolution, and load balancing for your applications using the Microsoft Azure infrastructure. Azure DNS supports both internet-facing DNS domains and private DNS zones.
+The Domain Name System (DNS) is responsible for translating (resolving) a service name to an IP address. Azure DNS provides DNS hosting, resolution, and load balancing for your applications using the Microsoft Azure infrastructure. Azure DNS supports both internet-facing DNS domains and private DNS zones.
 
 Azure DNS provides the following services:
 - [Azure Public DNS](public-dns-overview.md) is a hosting service for DNS domains. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
@@ -34,4 +34,4 @@ Using Azure DNS, you can:
 * For frequently asked questions about Azure DNS, see [Azure DNS FAQ](dns-faq-private.yml).
 * For frequently asked questions about Azure Private DNS, see [Azure Private DNS FAQ](dns-faq.yml).
 * For frequently asked questions about Traffic Manager, see [Traffic Manager routing methods](/azure/traffic-manager/traffic-manager-faqs)
-* Also see the learn module: [Introduction to Azure DNS](/training/modules/intro-to-azure-dns).
+* Also see [Learn module: Introduction to Azure DNS](/training/modules/intro-to-azure-dns).

articles/dns/dns-private-resolver-overview.md

@@ -17,7 +17,7 @@ Azure DNS Private Resolver is a new service that enables you to query Azure DNS
 
 ## How does it work?
 
-Azure DNS Private Resolver requires an [Azure Virtual Network](../virtual-network/virtual-networks-overview.md).  When you create an Azure DNS Private Resolver inside a virtual network, one or more [inbound endpoints](#inbound-endpoints) are established that can be used as the destination for DNS queries. The resolver's [outbound endpoint](#outbound-endpoints) processes DNS queries based on a [DNS forwarding ruleset](#dns-forwarding-rulesets) that you configure.  DNS queries that are initiated in networks linked to a ruleset can be sent to other DNS servers.
+Azure DNS Private Resolver requires an [Azure Virtual Network](../virtual-network/virtual-networks-overview.md). When you create an Azure DNS Private Resolver inside a virtual network, one or more [inbound endpoints](#inbound-endpoints) are established that can be used as the destination for DNS queries. The resolver's [outbound endpoint](#outbound-endpoints) processes DNS queries based on a [DNS forwarding ruleset](#dns-forwarding-rulesets) that you configure. DNS queries that are initiated in networks linked to a ruleset can be sent to other DNS servers.
 
 You don't need to change any DNS client settings on your virtual machines (VMs) to use the Azure DNS Private Resolver.
 
@@ -101,7 +101,7 @@ The following limits currently apply to Azure DNS Private Resolver:
 ### Virtual network restrictions 
 
 The following restrictions hold with respect to virtual networks:
-- VNets with [encryption](/azure/virtual-network/virtual-network-encryption-overview) enabled do not support Azure DNS Private Resolver.
+- VNets with [encryption](/azure/virtual-network/virtual-network-encryption-overview) enabled don't support Azure DNS Private Resolver.
 - A DNS resolver can only reference a virtual network in the same region as the DNS resolver.
 - A virtual network can't be shared between multiple DNS resolvers. A single virtual network can only be referenced by a single DNS resolver.
 
@@ -126,7 +126,7 @@ Outbound endpoints have the following limitations:
 ### Other restrictions
 
 - IPv6 enabled subnets aren't supported.
-- DNS private resolver does not support Azure ExpressRoute FastPath.
+- DNS private resolver doesn't support Azure ExpressRoute FastPath.
 - DNS private resolver inbound endpoint provisioning isn't compatible with [Azure Lighthouse](../lighthouse/overview.md).
     - To see if Azure Lighthouse is in use, search for **Service providers** in the Azure portal and select **Service provider offers**. 
 

articles/dns/private-dns-overview.md

@@ -19,7 +19,7 @@ To resolve the records of a private DNS zone from your virtual network, you must
 ![DNS overview](./media/private-dns-overview/scenario.png)
 
 > [!NOTE]
-> As a best practice, do not use a *.local* domain for your private DNS zone. Not all operating systems support this.
+> As a best practice, don't use a *.local* domain for your private DNS zone. Not all operating systems support this.
 
 ## Private zone resiliency
 

articles/dns/public-dns-overview.md

@@ -33,7 +33,7 @@ For more information, see [How to protect DNS zones and records](dns-protect-zon
 
 ## DNSSEC
 
-Azure Public DNS does not currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
+Azure Public DNS doesn't currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
 
 ## Ease of use