acrolinx

greg-lindsay · greg-lindsay · commit 8c587b73df26 · 2023-11-30T09:47:06.000-08:00
diff --git a/articles/dns/dns-faq-private.yml b/articles/dns/dns-faq-private.yml
@@ -103,8 +103,8 @@ sections:
         answer: |
           We strongly recommend that you migrate to the new resource model as soon as possible. Legacy resource model will be supported, however, further features won't be developed on top of this model. In future, we intend to deprecate it in favor of new resource model. For guidance on how to migrate your existing private DNS zones to new resource model see[migration guide for Azure DNS private zones](private-dns-migration-guide.md).
           
-          ### Does Azure DNS private zones store any customer content?
-          No, Azure DNS private zones doesn't store any customer content.
+          ### Do Azure DNS private zones store any customer content?
+          No, Azure DNS private zones don't store any customer content.
 
 additionalContent: |
 
diff --git a/articles/dns/dns-getstarted-powershell.md b/articles/dns/dns-getstarted-powershell.md
@@ -1,7 +1,7 @@
 ---
 title: 'Quickstart: Create an Azure DNS zone and record - Azure PowerShell'
 titleSuffix: Azure DNS
-description: Learn how to create a DNS zone and record in Azure DNS. This is a step-by-step quickstart to create and manage your first DNS zone and record using Azure PowerShell.
+description: Learn how to create a DNS zone and record in Azure DNS. This article is a step-by-step quickstart to create and manage your first DNS zone and record using Azure PowerShell.
 services: dns
 author: greg-lindsay
 ms.author: greglin
@@ -18,7 +18,7 @@ ms.custom: devx-track-azurepowershell, mode-api
 
 In this quickstart, you create your first DNS zone and record using Azure PowerShell. You can also perform these steps using the [Azure portal](dns-getstarted-portal.md) or the [Azure CLI](dns-getstarted-cli.md). 
 
-A DNS zone is used to host the DNS records for a particular domain. To start hosting your domain in Azure DNS, you need to create a DNS zone for that domain name. Each DNS record for your domain is then created inside this DNS zone. Finally, to publish your DNS zone to the Internet, you need to configure the name servers for the domain. Each of these steps is described below.
+A DNS zone is used to host the DNS records for a particular domain. To start hosting your domain in Azure DNS, you need to create a DNS zone for that domain name. Each DNS record for your domain is then created inside this DNS zone. Finally, to publish your DNS zone to the Internet, you need to configure the name servers for the domain. Each of these steps is described in this article.
 
 :::image type="content" source="media/dns-getstarted-portal/environment-diagram.png" alt-text="Diagram of DNS deployment environment using the Azure PowerShell." border="false":::
 
@@ -49,7 +49,7 @@ New-AzDnsZone -Name contoso.xyz -ResourceGroupName MyResourceGroup
 
 ## Create a DNS record
 
-You create record sets by using the `New-AzDnsRecordSet` cmdlet. The following example creates a record with the relative name "www" in the DNS Zone "contoso.xyz", in resource group "MyResourceGroup". The fully qualified name of the record set is "www.contoso.xyz". The record type is "A", with IP address "10.10.10.10", and the TTL is 3600 seconds.
+Create record sets by using the `New-AzDnsRecordSet` cmdlet. The following example creates a record with the relative name `www` in the DNS Zone `contoso.xyz`, in resource group `MyResourceGroup`. The fully qualified name of the record set is `www.contoso.xyz`. The record type is `A`, with IP address `10.10.10.10`, and the TTL is 3600 seconds.
 
 ```powershell
 New-AzDnsRecordSet -Name www -RecordType A -ZoneName contoso.xyz -ResourceGroupName MyResourceGroup -Ttl 3600 -DnsRecords (New-AzDnsRecordConfig -IPv4Address "10.10.10.10")
@@ -105,7 +105,7 @@ Remove-AzResourceGroup -Name MyResourceGroup
 
 ## Next steps
 
-Now that you've created your first DNS zone and record using Azure PowerShell, you can create records for a web app in a custom domain.
+Now that your first DNS zone and record is created using Azure PowerShell, you can create records for a web app in a custom domain.
 
 > [!div class="nextstepaction"]
 > [Create DNS records for a web app in a custom domain](./dns-web-sites-custom-domain.md)
diff --git a/articles/dns/dns-reverse-dns-for-azure-services.md b/articles/dns/dns-reverse-dns-for-azure-services.md
@@ -35,7 +35,7 @@ A third party shouldn't have access to create reverse DNS records for Azure serv
 
 This validation is only done when the reverse DNS record is set or modified. Periodic revalidation isn't done.
 
-For example, suppose the Public Ip address resource has the DNS name `contosoapp1.northus.cloudapp.azure.com` and IP address `23.96.52.53`. The reverse FQDN for the Public IP address can be specified as:
+For example, suppose the Public IP address resource has the DNS name `contosoapp1.northus.cloudapp.azure.com` and IP address `23.96.52.53`. The reverse FQDN for the Public IP address can be specified as:
 
 * The DNS name for the Public IP address: `contosoapp1.northus.cloudapp.azure.com`.
 * The DNS name for a different PublicIpAddress in the same subscription, such as: `contosoapp2.westus.cloudapp.azure.com`.
diff --git a/articles/dns/dns-troubleshoot.md b/articles/dns/dns-troubleshoot.md
@@ -47,12 +47,12 @@ To resolve common issues, try one or more of the following steps:
 
 DNS name resolution is a multi-step process, which can fail for many reasons. The following steps help you investigate why DNS resolution is failing for a DNS record in a zone hosted in Azure DNS.
 
-1.	Confirm that the DNS records have been configured correctly in Azure DNS. Review the DNS records in the Azure portal, checking that the zone name, record name, and record type are correct.
+1.	Confirm that the DNS records are configured correctly in Azure DNS. Review the DNS records in the Azure portal, checking that the zone name, record name, and record type are correct.
 2.	Confirm that the DNS records resolve correctly on the Azure DNS name servers.
     - If you make DNS queries from your local PC, you may see cached results that don’t reflect the current state of the name servers.  Also, corporate networks often use DNS proxy servers, which prevent DNS queries from being directed to specific name servers.  To avoid these problems, use a web-based name resolution service such as [digwebinterface](https://digwebinterface.com).
     - Be sure to specify the correct name servers for your DNS zone, as shown in the Azure portal.
     - Check that the DNS name is correct (you have to specify the fully qualified name, including the zone name) and the record type is correct
-3.	Confirm that the DNS domain name has been correctly [delegated to the Azure DNS name servers](dns-domain-delegation.md). There are a [many 3rd-party web sites that offer DNS delegation validation](https://www.bing.com/search?q=dns+check+tool). This test is a *zone* delegation test, so you should only enter the DNS zone name and not the fully qualified record name.
+3.	Confirm that the DNS domain name is correctly [delegated to the Azure DNS name servers](dns-domain-delegation.md). There are a [many 3rd-party web sites that offer DNS delegation validation](https://www.bing.com/search?q=dns+check+tool). This test is a *zone* delegation test, so you should only enter the DNS zone name and not the fully qualified record name.
 4.	Having completed the above, your DNS record should now resolve correctly. To verify, you can again use [digwebinterface](https://digwebinterface.com), this time using the default name server settings.
 
 ### Recommended articles
@@ -97,7 +97,7 @@ The following scenario demonstrates where a configuration error has led to the u
 
 **Unhealthy Delegation**
 
-A primary zone contains NS delegation records, which help delegate traffic from the primary to the child zones. If any NS delegation record is present in the parent zone, the DNS server is supposed to mask all other records below the NS delegation record, except glue records, and direct traffic to the respective child zone based on the user query. If a parent zone contains other records meant for the child zones (delegated zones) below the NS delegation record, the zone will be marked unhealthy, and its status is **Degraded**.
+A primary zone contains NS delegation records, which help delegate traffic from the primary to the child zones. If any NS delegation record is present in the parent zone, the DNS server is supposed to mask all other records below the NS delegation record (except glue records) and direct traffic to the respective child zone based on the user query. If a parent zone contains other records meant for the child zones (delegated zones) below the NS delegation record, the zone will be marked unhealthy and its status is **Degraded**.
 
 **What are glue records?** - These are records under the delegation record, which help direct traffic to the delegated/child zones using their IP addresses and are configured as seen in the following.
 
@@ -137,7 +137,7 @@ In the preceding example, **child** is the NS delegation records. The records _*
 
 **How can you fix it?** - To resolve, locate and remove all records except glue records under NS delegation records in your parent zone.
 
-**How to locate unhealthy delegation records?** - A script has been created to find the unhealthy delegation records in your zone.  The script will report records, which are unhealthy.
+**How to locate unhealthy delegation records?** - A script is provided to find the unhealthy delegation records in your zone.  The script will report records, which are unhealthy.
 
 1. Save the script located at: [Find unhealthy DNS records in Azure DNS - PowerShell script sample](./scripts/find-unhealthy-dns-records.md)
 
