acrolinx

Author: greg-lindsay

articles/dns/dns-security-policy.md

@@ -22,7 +22,7 @@ This article provides an overview of DNS security policy. Also see the following
 ## What DNS security policy?
 
 DNS security policy offers the ability to filter and log DNS queries at the virtual network (VNet) level. With DNS security policy you can:
-- Create rules to protect against DNS-based attacks by blocking block name resolution of known or malicious domains. 
+- Create rules to protect against DNS-based attacks by blocking name resolution of known or malicious domains. 
 - Save and view detailed DNS logs to gain inside into your DNS traffic.
 
 DNS logs can be sent to a storage account, log analytics workspace, or event hubs. You can choose to allow, alert, or block DNS queries.
@@ -37,7 +37,7 @@ DNS Security Policy can be configured using Azure PowerShell or the Azure portal
 
 ### Location
 
-A security policy can only apply to VNets in the same region. You can create any number of security policies in the same region. In the following example, two polices are created in each of two different regions (East US and Central US). 
+A security policy can only apply to VNets in the same region. You can create any number of security policies in the same region. In the following example, two policies are created in each of two different regions (East US and Central US). 
 
 ![Screenshot of the list of DNS security policies.](./media/dns-security-policy/policy-list.png)
 
@@ -79,7 +79,7 @@ You can associate a domain list to multiple DNS traffic rules in different secur
 
 ![Screenshot of domains inside a domain list.](./media/dns-security-policy/domain-list-detailed.png)
 
-When viewing a DNS domain list in the Azure portal, you can also select **Settings** > **Associated DNS Traffic Rules** to see a list of all traffic rules and thye associated DNS security policies that reference the DNS domain list.
+When viewing a DNS domain list in the Azure portal, you can also select **Settings** > **Associated DNS Traffic Rules** to see a list of all traffic rules and the associated DNS security policies that reference the DNS domain list.
 
 ![Screenshot of associated domain list traffic rules.](./media/dns-security-policy/domain-list-traffic-rules.png)
 

articles/dns/dns-traffic-log-how-to.md

@@ -41,7 +41,7 @@ To create a DNS security policy using the Azure portal:
     ![Screenshot of the Basics tab for security policy.](./media/dns-traffic-log-how-to/secpol-basics.png)
 
 5. Select **Next: Virtual Networks Link** and then select **+ Add**.  
-6. VNets in the same region as the security policy are displayed. Select one or more available VNets and then select **Add**. You can't choose a VNet that is already associated with another security policy. In the following example, two VNets have already been associated with a security policy, leaving two VNets available to select.
+6. VNets in the same region as the security policy are displayed. Select one or more available VNets and then select **Add**. You can't choose a VNet that is already associated with another security policy. In the following example, two VNets are associated with a security policy, leaving two VNets available to select.
 
     ![Screenshot of the Virtual Network Links tab for security policy.](./media/dns-traffic-log-how-to/secpol-vnet-links.png)
 
@@ -52,7 +52,7 @@ To create a DNS security policy using the Azure portal:
      > [!NOTE]
      > Virtual network links are created for all VNets displayed in the list, whether or not they are *selected*. Use checkboxes to select VNets for removal from the list.
 
-8. Select **Review + create** and then select **Create**. Choosing **Next: DNS Traffic Rules** is skipped here, but you also have the option to create traffic rules now. In this guide, traffic rules and DNS domain lists are created and applied to DNS security policy later.
+8. Select **Review + create** and then select **Create**. Choosing **Next: DNS Traffic Rules** is skipped here, but you can also create traffic rules now. In this guide, traffic rules and DNS domain lists are created and applied to DNS security policy later.
 
 ## Create a log analytics workspace
 
@@ -102,9 +102,9 @@ To create a DNS domain list using the Azure portal:
 
     ![Screenshot of creating a DNS Domain List.](./media/dns-traffic-log-how-to/create-domain-list.png)
 
-7. When you have completed entering domain names, select **Review + create** and then select **Create**.
+7. When you complete entering domain names, select **Review + create** and then select **Create**.
 
-Repeat this section to create additional domain lists if desired. Each domain list can be associated to a traffic rule that has one of three actions:
+Repeat this section to create more domain lists if desired. Each domain list can be associated to a traffic rule that has one of three actions:
 
 - **Allow**: Permit the DNS query and log it.
 - **Block**: Block the DNS query and log the block action.
@@ -150,7 +150,7 @@ See the following example:
 
 [ ![Screenshot of an example log analytics query.](./media/dns-traffic-log-how-to/test-query.png) ](./media/dns-traffic-log-how-to/test-query.png#lightbox)
 
-Recall that the traffic rule containing contoso.com was set to **Allow** queries. The query from the VM results in a successful response:
+Recall that the traffic rule containing contoso.com was set to **Allow** queries. The query from the virtual machine results in a successful response:
 
 ```cmd
 C:\>dig db.sec.contoso.com +short
@@ -165,7 +165,7 @@ Expanding the query details in log analytics displays data such as:
 * ResolutionPath: PrivateDnsResolution
 * ResolverPolicyRuleAction: Allow
 
-If the traffic rule is edited and set to **Block** contoso.com queries, the query from the VM results in a failed response. Be sure to select **Save** when you change the components of a rule.
+If the traffic rule is edited and set to **Block** contoso.com queries, the query from the virtual machine results in a failed response. Be sure to select **Save** when you change the components of a rule.
 
 ![Screenshot of editing a traffic rule.](./media/dns-traffic-log-how-to/edit-rule.png)