Line edits2

Author: lootle1

learn-pr/azure/intro-to-azure-dns/5-knowledge-check.yml

@@ -25,26 +25,26 @@ quiz:
     - content: "Azure DNS Private zone."
       isCorrect: true
       explanation: "Correct. Azure DNS private zones allow you to configure automatically assigned selectively resolvable FQDNs to virtual machines on select Azure virtual networks."
-  - content: "In which of the following scenarios would you choose Azure DNS to host your organizations internet resolvable DNS zones?"
+  - content: "In which of the following scenarios would you choose Azure DNS to host your organization's internet resolvable DNS zones?"
     choices:
     - content: "You need to secure DNS records using DNSSEC."
       isCorrect: false
       explanation: "Incorrect. Azure DNS doesn't support DNSSEC."
-    - content: "You need to manage and update MX, TXT and CNAME IPv6 records for a DNS zone."
+    - content: "You need to manage and update MX, TXT, and CNAME IPv6 records for a DNS zone."
       isCorrect: true
-      explanation: "Correct. Azure DNS supports hosting MX, TXT and CNAME records."
+      explanation: "Correct. Azure DNS supports hosting MX, TXT, and CNAME records."
     - content: "You need to provide an Active Directory Integrated DNS zone for IaaS VM hosts."
       isCorrect: false
       explanation: "Incorrect. Azure DNS doesn't support Active Directory Integrated DNS zones."
   - content: "Which of the following tools can you use to manage Azure DNS zone records?"
     choices:
     - content: "Azure CLI."
       isCorrect: true
-      explanation: "Correct. You can manage Azure DNS zone records using Azure CLI"
+      explanation: "Correct. You can manage Azure DNS zone records using Azure CLI."
     - content: "Windows Admin Center."
       isCorrect: false
-      explanation: "Incorrect. You can't manage Azure DNS records using Windows Admin Center. You can use Windows Admin Center to manage Windows Server DNS server records"
+      explanation: "Incorrect. You can't manage Azure DNS records using Windows Admin Center. You can use Windows Admin Center to manage Windows Server DNS server records."
     - content: "Dnscmd.exe utility."
       isCorrect: false
-      explanation: "Incorrect. You can't use dnscmd.exe to manage Azure DNS records. You can use dnscmd.exe to manage Windows Server DNS server records"
+      explanation: "Incorrect. You can't use dnscmd.exe to manage Azure DNS records. You can use dnscmd.exe to manage Windows Server DNS server records."
 

learn-pr/azure/intro-to-azure-dns/includes/2-what-is-azure-dns.md

@@ -4,6 +4,6 @@ Azure DNS allows you to manage DNS zone data using the Azure portal, Azure Power
 
 Since Azure DNS is hosted on Microsoft's Azure infrastructure, the service is more resilient to network failures than DNS services hosted on individual servers managed by your organization or third parties. If a DNS service hosting important DNS zone data such as the records for your organization's website or email server becomes unavailable, those services will likely not function correctly. For example, a DNS server outage not only can stop people from being able to navigate to your organization's website, but it can also stop people from being able to email others in your organization!
 
-You can fully integrate Azure DNS with Azure resources. Azure DNS provides functionality allowing you to automatically update records based on when you deploy or modify resources in Azure. For example, if you weren't using Azure DNS and you choose to deploy a web application that you want to associate with the custom FQDN app.tailwindtraders.com, you'll need to create or update the host record for app.tailwindtraders.com in the tailwindtraders.com DNS zone to point to the web app's IP address on a DNS server that you manage separately. With Azure DNS, you can automate the process of configuring and updating DNS records. If you move the web app to a new location, the Azure DNS record associated with that web app will automatically be updated.
+You can fully integrate Azure DNS with Azure resources. Azure DNS provides functionality allowing you to automatically update records based on when you deploy or modify resources in Azure. For example, say you aren't using Azure DNS and you choose to deploy a web application that you want to associate with the custom FQDN app.tailwindtraders.com. You'll need to create or update the host record for app.tailwindtraders.com in the tailwindtraders.com DNS zone to point to the web app's IP address on a DNS server that you manage separately. With Azure DNS, you can automate the process of configuring and updating DNS records. If you move the web app to a new location, the Azure DNS record associated with that web app will automatically be updated.
 
 Azure DNS supports all common DNS record types including A, AAAA, CNAME, MX, PTR, SOA, SRV, and TXT records. Azure DNS supports records that map to both IPv4 and IPv6 addresses, and Azure DNS servers can be reached by clients using both IPv4 and IPv6 addresses.

learn-pr/azure/intro-to-azure-dns/includes/3-how-azure-dns-works.md

@@ -1,4 +1,4 @@
-Azure DNS hosts DNS zones and provides a name resolution service using Microsoft's Azure infrastructure. Traditionally when a DNS service is hosted on a server running Windows Server or Linux and a DNS zone gets delegated to that server. A client making a DNS query for a host in that zone will have their query answered by that DNS server service. When a host on the internet queries for a DNS record in a DNS zone that has been delegated to Azure DNS, Azure DNS responds to that host with the result of that query.
+Azure DNS hosts DNS zones and provides a name resolution service using Microsoft's Azure infrastructure. Traditionally when a DNS service is hosted on a server running Windows Server or Linux and a DNS zone gets delegated to that server, a client making a DNS query for a host in that zone will have their query answered by that DNS server service. When a host on the internet queries for a DNS record in a DNS zone that has been delegated to Azure DNS, Azure DNS responds to that host with the result of that query.
 
 DNS zones in Azure DNS are hosted across Azure's global network of DNS name servers. These servers use Anycast networking so that queries for DNS zone data will be answered by the DNS server closest to the querying client. For example, if a person in Australia is performing a DNS query against a DNS record in a DNS zone hosted in Azure DNS, a DNS server in an Australian Azure datacenter will respond to that query. The same query performed by someone in Europe will have a DNS server in a European Azure region respond to the query.
 
@@ -8,19 +8,21 @@ Azure DNS public zones host domain name zone data for records that you intend to
 
 ## Azure DNS private zones
 
-Many organizations use internal DNS names that are separate from public DNS names for hosts on their internal on-premises networks. Azure Private DNS zones allow you to replicate this functionality by configuring a private DNS zone namespace that can be used to map FQDNs with private Azure resources. For example, you might have several virtual networks that host virtual machines in your organization's Azure subscription that are inaccessible to the internet but accessible through a virtual private network. In the future, Tailwind Traders will deploy several multi-tier applications running across IaaS virtual machines. In this configuration, each virtual machine performs different application tasks including manipulation and processing of sales data. The application architects want each virtual machine to be able to access other resources on these private virtual networks using FQDNs. You also want to ensure that those FQDNs aren't resolvable to hosts outside on the Internet. This task can be accomplished using Azure DNS private zones. If you want to configure some records in the tailwindtraders.com DNS zone to be public whilst others remain private, you can also use Azure DNS private zones to accomplish this goal. Another term for this segmenting of public and private DNS records in a zone is split-horizon DNS.
+Many organizations use internal DNS names that are separate from public DNS names for hosts on their internal on-premises networks. Azure Private DNS zones allow you to replicate this functionality by configuring a private DNS zone namespace that can be used to map FQDNs with private Azure resources. For example, you might have several virtual networks that host virtual machines in your organization's Azure subscription that are inaccessible to the internet but accessible through a virtual private network.
+
+In the future, Tailwind Traders will deploy several multi-tier applications running across IaaS virtual machines. In this configuration, each virtual machine performs different application tasks including manipulation and processing of sales data. The application architects want each virtual machine to be able to access other resources on these private virtual networks using FQDNs. You also want to ensure that those FQDNs aren't resolvable to hosts outside on the Internet. This task can be accomplished using Azure DNS private zones. If you want to configure some records in the tailwindtraders.com DNS zone to be public whilst others remain private, you can also use Azure DNS private zones to accomplish this goal. Another term for this segmenting of public and private DNS records in a zone is split-horizon DNS.
 
 Like Azure DNS public zones, Azure DNS private zones support all common DNS record types including A, AAAA, CNAME, MX, PTR, SOA, SRV, and TXT records.
 
 Azure DNS private zones support the following features:
 
-- **Automatic hostname record management.** Along with hosting your custom DNS records, Azure automatically maintains hostname records for the VMs in the specified virtual networks. In this scenario, you can optimize the domain names you use without needing to create custom DNS solutions or modify applications.
+- **Automatic hostname record management**: Along with hosting your custom DNS records, Azure automatically maintains hostname records for the VMs in the specified virtual networks. In this scenario, you can optimize the domain names you use without needing to create custom DNS solutions or modify applications.
 
-- **Hostname resolution between virtual networks.** Unlike Azure-provided host names, private DNS zones can be shared between virtual networks. This capability simplifies cross-network and service-discovery scenarios, such as virtual network peering.
+- **Hostname resolution between virtual networks**: Unlike Azure-provided host names, private DNS zones can be shared between virtual networks. This capability simplifies cross-network and service-discovery scenarios, such as virtual network peering.
 
-- **Split-horizon DNS support.** With Azure DNS, you can create zones with the same name that resolve to different answers from within a virtual network and from the public internet. A typical scenario for split-horizon DNS is to provide a dedicated version of a service for use inside your virtual network.
+- **Split-horizon DNS support**: With Azure DNS, you can create zones with the same name that resolves to different answers from within a virtual network and from the public internet. A typical scenario for split-horizon DNS is to provide a dedicated version of a service for use inside your virtual network.
 
-- **Support for Azure Private Endpoint DNS.** Azure DNS private zones support FQDN records in a private DNS zone mapping to an Azure Private Endpoint. An Azure Private Endpoint is a network interface with a private IP address on a virtual network that maps to an Azure service such as Azure Storage, Azure Cosmos DB, Azure SQL Database or your own Azure Private Link Service.
+- **Support for Azure Private Endpoint DNS**: Azure DNS private zones support FQDN records in a private DNS zone mapping to an Azure Private Endpoint. An Azure Private Endpoint is a network interface with a private IP address on a virtual network that maps to an Azure service such as Azure Storage, Azure Cosmos DB, Azure SQL Database or your own Azure Private Link Service.
 
 A diagram shows the integration of the Azure DNS public zone tailwindtraders.com with the Azure DNS private zone tailwindtraders.com in split-horizon configuration.
 

learn-pr/azure/intro-to-azure-dns/includes/4-when-to-use-azure-dns.md

@@ -2,9 +2,9 @@ Almost every organization that has an internet presence has one or more DNS doma
 
 Your options for managing the records in public DNS zones include:
 
-- Use your DNS registrar's DNS management tools. Most DNS registrars provide basic DNS zone hosting and management functionality. You can use your DNS registrar's tools to manually create and manage records in your organizations publicly registered DNS zones. When using a DNS registrar's management functionality, it's difficult to automate changes in line with adding and modifying apps and services in Azure. DNS registrar tools are mostly aimed at organizations that need simple DNS services, not ones who are adding and modifying new services on a frequent basis.
+- **Use your DNS registrar's DNS management tools**: Most DNS registrars provide basic DNS zone hosting and management functionality. You can use your DNS registrar's tools to manually create and manage records in your organizations publicly registered DNS zones. When using a DNS registrar's management functionality, it's difficult to automate changes in line with adding and modifying apps and services in Azure. DNS registrar tools are mostly aimed at organizations that need simple DNS services, not ones who are adding and modifying new services on a frequent basis.
 
-- Manage your own DNS servers. Many organizations, especially ones with on-premises configurations involving Active Directory Domain Services already host their own DNS server infrastructure. Managing your own DNS servers is more administratively intensive. However, if your organization needs to replicate Active Directory integrated DNS zone data, zone transfer, or needs to support DNSSEC, managing your own DNS server might be a more appropriate solution. In our Tailwind Traders example, you don't need this extra functionality, so the extra administrative effort required to manage your own DNS server isn't justified.
+- **Manage your own DNS servers**: Many organizations, especially ones with on-premises configurations involving Active Directory Domain Services, already host their own DNS server infrastructure. Managing your own DNS servers is more administratively intensive. However, if your organization needs to replicate Active Directory integrated DNS zone data, zone transfer, or needs to support DNSSEC, managing your own DNS server might be a more appropriate solution. In our Tailwind Traders example, you don't need this extra functionality, so the extra administrative effort required to manage your own DNS server isn't justified.
 
 Azure DNS provides an alternative to these commonly used options. You should use Azure DNS:
 
@@ -16,7 +16,7 @@ Azure DNS provides an alternative to these commonly used options. You should use
 
 - You don't need access to features such as DNSSEC, Active Directory Integrated DNS Zones, or zone transfer.
 
-Azure DNS provides you with a good solution because you don't currently require features such as DNSSEC and you don't want to manage a DNS server. Azure DNS also allows you to manage Azure and DNS resources using a single set of tools.
+Azure DNS provides you with a good solution because you don't currently require features such as DNSSEC, and you don't want to manage a DNS server. Azure DNS also allows you to manage Azure and DNS resources using a single set of tools.
 
 When your application developers deploy a multi-tier VM application in a private Azure virtual network for which DNS resource records shouldn't be publicly resolvable, you can implement Azure DNS private zones. You should use Azure DNS private zones:
 

learn-pr/azure/intro-to-azure-dns/includes/6-summary.md

@@ -1,13 +1,11 @@
-In this module you learned about Azure DNS, a cloud hosted service that allows you to host and manage public DNS zones and data. You learned about the type of scenarios where Azure DNS is an appropriate solution for your organization and how Azure DNS is likely able to meet Tailwind Trader's needs, especially when it comes to using a single set of tools to manage DNS rather than having to use their DNS registrar's management tools each time an alteration is made to one of their Azure applications or services. You also learned about the differences between public and private Azure DNS zones and the situations in which each option is appropriate.
+In this module you learned about Azure DNS, a cloud hosted service that allows you to host and manage public DNS zones and data. You learned about the type of scenarios where Azure DNS is an appropriate solution for your organization and how Azure DNS is likely able to meet Tailwind Trader's needs. This is true especially when it comes to using a single set of tools to manage DNS rather than having to use their DNS registrar's management tools each time an alteration is made to one of their Azure applications or services. You also learned about the differences between public and private Azure DNS zones and the situations in which each option is appropriate.
 
 ## Learn more
 
-* [Create activity log alerts on service notifications using the Azure portal](/azure/service-health/alerts-activity-log-service-notifications-portal)
+* [Create Service Health alerts using the Azure portal](/azure/service-health/alerts-activity-log-service-notifications-portal)
 
 * [Overview of DNS zones and records](/azure/dns/dns-zones-records)
 
 * [Azure DNS FAQ](/azure/dns/dns-faq)
 
 * [Host your domain on Azure DNS](/training/modules/host-domain-azure-dns/)
-
-* [Configure Azure DNS](/training/modules/configure-azure-dns/)