modify exclusion article

Author: teresayao

articles/web-application-firewall/afds/waf-front-door-exclusion.md

@@ -13,16 +13,17 @@ ms.topic: conceptual
 
 Sometimes Web Application Firewall (WAF) might block a request that you want to allow for your application. For example, Active Directory inserts tokens that are used for authentication. These tokens can contain special characters that may trigger a false positive from the WAF rules. WAF exclusion lists allow you to omit certain request attributes from a WAF evaluation.  An exclusion list can be configured using  [PowserShell](https://docs.microsoft.com/powershell/module/az.frontdoor/New-AzFrontDoorWafManagedRuleExclusionObject?view=azps-3.5.0), [Azure CLI](https://docs.microsoft.com/cli/azure/ext/front-door/network/front-door/waf-policy/managed-rules/exclusion?view=azure-cli-latest#ext-front-door-az-network-front-door-waf-policy-managed-rules-exclusion-add), [Rest API](https://docs.microsoft.com/rest/api/frontdoorservice/webapplicationfirewall/policies/createorupdate), or the Azure portal. The following example shows the Azure portal configuration. 
 ## Configure exclusion lists using the Azure portal
-**Manage exclusion** is accessible from WAF managed rules portal: 
+**Manage exclusions** is accessible from WAF portal under **Managed rules**
+
 ![Manage exclusion](../media/waf-front-door-exclusion/exclusion1.png)
 ![Manage exclusion_add](../media/waf-front-door-exclusion/exclusion2.png)
 
  An example exclusion list:
 ![Manage exclusion_define](../media/waf-front-door-exclusion/exclusion3.png)
 
-This example excludes the value in the *user* header field. A valid request may include the *user* field that contains a string which triggers a SQL injection rule. You can exclude the *user* parameter in this case so that the WAF rule doesn't evaluate anything in the field.
+This example excludes the value in the *user* header field. A valid request may include the *user* field that contains a string that triggers a SQL injection rule. You can exclude the *user* parameter in this case so that the WAF rule doesn't evaluate anything in the field.
 
-The following attributes can be added to exclusion lists by name. The values of the fields you use  aren't evaluated against WAF rules, but their names are evaluated. The exclusion lists removes inspection of the field's value.
+The following attributes can be added to exclusion lists by name. The values of the fields you use  aren't evaluated against WAF rules, but their names are evaluated. The exclusion lists remove inspection of the field's value.
 
 * Request header name
 * Request cookie name