Merge pull request #293022 from vhorne/waf-policy

freshness review

Author: prmerger-automator[bot]

articles/web-application-firewall/ag/policy-overview.md

@@ -3,9 +3,9 @@ title: Azure Web Application Firewall (WAF) policy overview
 description: This article is an overview of Web Application Firewall (WAF) global, per-site, and per-URI policies.
 services: web-application-firewall
 ms.topic: concept-article
-author: winthrop28
+author: vhorne
 ms.service: azure-web-application-firewall
-ms.date: 10/06/2023
+ms.date: 01/14/2025
 ms.author: victorh
 ---
 
@@ -42,15 +42,15 @@ Say you have three sites: contoso.com, fabrikam.com, and adatum.com all behind t
 
 You can apply a global policy to the WAF, with some basic settings, exclusions, or custom rules if necessary to stop some false positives from blocking traffic. In this case, there's no need to have global SQL injection rules running because fabrikam.com and contoso.com are static pages with no SQL backend. So you can disable those rules in the global policy.
 
-This global policy is suitable for contoso.com and fabrikam.com, but you need to be more careful with adatum.com where sign-in information and payments are handled. You can apply a per-site policy to the adatum listener and leave the SQL rules running. Also assume there's a cookie blocking some traffic, so you can create an exclusion for that cookie to stop the false positive. 
+This global policy is suitable for contoso.com and fabrikam.com, but you need to be more careful with adatum.com where sign-in information and payments are handled. You can apply a per-site policy to the Adatum listener and leave the SQL rules running. Also assume there's a cookie blocking some traffic, so you can create an exclusion for that cookie to stop the false positive. 
 
 The adatum.com/payments URI is where you need to be careful. So apply another policy on that URI and leave all rules enabled, and also remove all exclusions.
 
 In this example, you have a global policy that applies to two sites. You have a per-site policy that applies to one site, and then a per-URI policy that applies to one specific path-based rule. See [Configure per-site WAF policies using Azure PowerShell](per-site-policies.md) for the corresponding PowerShell for this example.
 
 ## Existing WAF configurations
 
-All new Web Application Firewall's WAF settings (custom rules, managed rule set configurations, exclusions, and so on.) exist in a WAF policy. If you have an existing WAF, these settings may still exist in your WAF configuration. For more information about moving to the new WAF policy, [Migrate WAF Config to a WAF Policy](./migrate-policy.md). 
+All new Web Application Firewall's WAF settings (custom rules, managed rule set configurations, exclusions, and so on) exist in a WAF policy. If you have an existing WAF, these settings might still exist in your WAF configuration. For more information about moving to the new WAF policy, [Migrate WAF Config to a WAF Policy](./migrate-policy.md). 
 
 
 ## Next steps