Acrolinx and validation

Author: ShawnJackson

articles/web-application-firewall/afds/waf-faq.yml

@@ -66,7 +66,7 @@ sections:
         answer: |
           When you enable the WAF on an existing application, it's common to have false-positive detections in which the WAF rules detect legitimate traffic as a threat. To minimize the risk of an impact to your users, we recommend the following process:
           
-          1. Enable the WAF in [**Detection** mode](./waf-front-door-create-portal.md#change-mode) to ensure that the WAF doesn't block requests while you're working through this process. We recommend this step for testing purposes on the WAF.
+          1. Enable the WAF in [detection mode](./waf-front-door-create-portal.md#change-mode) to ensure that the WAF doesn't block requests while you're working through this process. We recommend this step for testing purposes on the WAF.
           
              > [!IMPORTANT]
              > This process describes how to enable the WAF on a new or existing solution when your priority is to minimize the disturbance to your application's users. If you're under attack or imminent threat, you might want to instead deploy the WAF in **Prevention** mode immediately. You can then use the tuning process to monitor and tune the WAF over time. This approach will probably cause some of your legitimate traffic to be blocked, which is why we recommend using it only when you're under threat.
@@ -79,7 +79,7 @@ sections:
       - question: |
           Do you support the same WAF features in all integrated platforms?
         answer: |
-          Currently, ModSecurity CRS 3.0, CRS 3.1, and CRS 3.2 rules are supported only with Azure Web Application Firewall on Application Gateway. Rate limiting and Azure-managed DRS rules are supported only with Azure Web Application Firewall on Azure Front Door.
+          Currently, Core Rule Set (CRS) 3.0, CRS 3.1, and CRS 3.2 rules are supported only with Azure Web Application Firewall on Application Gateway. Rate limiting and Azure-managed DRS rules are supported only with Azure Web Application Firewall on Azure Front Door.
 
       - question: |
           Is DDoS protection integrated with Azure Front Door? 

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

@@ -73,7 +73,7 @@ For more information, see the following resources:
 
 - [What is rate limiting for Azure Front Door?](waf-front-door-rate-limit.md).
 - [Configure an Azure Web Application Firewall rate limit rule by using Azure PowerShell](waf-front-door-rate-limit-configure.md).
-- [Why do additional requests above the threshold configured for my rate limit rule get passed to my back-end server?](waf-faq.yml#why-do-additional-requests-above-the-threshold-configured-for-my-rate-limit-rule-get-passed-to-my-backend-server-)
+- [Why do additional requests above the threshold configured for my rate limit rule get passed to my back-end server?](waf-faq.yml#why-do-additional-requests-above-the-threshold-configured-for-my-rate-limit-rule-get-passed-to-my-back-end-server-)
 
 ### Use a high threshold for rate limits
 

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

@@ -67,7 +67,7 @@ A single *Critical* rule match is enough for the WAF to block a request when in
 
 When your WAF uses an older version of the Default Rule Set (before DRS 2.0), your WAF runs in the traditional mode. Traffic that matches any rule is considered independently of any other rule matches. In traditional mode, you don't have visibility into the complete set of rules that a specific request matched.
 
-The version of the DRS that you use also determines which content types are supported for request body inspection. For more information, see [What content types does WAF support](waf-faq.yml#what-content-types-does-waf-support-) in the FAQ.
+The version of the DRS that you use also determines which content types are supported for request body inspection. For more information, see [What content types does WAF support](waf-faq.yml#what-content-types-does-the-waf-support-) in the FAQ.
 
 ## Paranoia level
 

articles/web-application-firewall/ag/application-gateway-waf-faq.yml

@@ -24,7 +24,7 @@ sections:
       - question: |
           What features does the WAF product tier support?
         answer: |
-          The WAF tier of Applicaton Gateway supports all the features available in the Standard tier.
+          The WAF tier of Application Gateway supports all the features available in the Standard tier.
 
       - question: |
           How do I monitor the Application Gateway WAF?

articles/web-application-firewall/ag/waf-application-gateway-for-containers-overview.md

@@ -12,7 +12,7 @@ ms.date: 07/22/2025
 
 # What is Azure Web Application Firewall on Application Gateway for Containers (preview)?
 
-Azure Web Application Firewall on [Azure Application Gateway for Containers](../../application-gateway/for-containers/overview.md) provides comprehensive protection for your Kubernetes workloads against common web vulnerabilities and attacks, including SQL injection, cross-site scripting (XSS), and other Open Web Application Security Project (OWASP) top 10 threats.
+Azure Web Application Firewall on [Azure Application Gateway for Containers](../../application-gateway/for-containers/overview.md) provides comprehensive protection for your Kubernetes workloads against common web vulnerabilities and attacks. For example, it addresses SQL injection, cross-site scripting (XSS), and other Open Web Application Security Project (OWASP) top 10 threats.
 
 Application Gateway for Containers is an application-layer (Layer 7) solution for [load balancing](/azure/architecture/guide/technology-choices/load-balancing-overview) and dynamic traffic management. It's designed specifically for workloads running in Kubernetes clusters. It represents the evolution of the [Application Gateway Ingress Controller (AGIC)](../../application-gateway/ingress-controller-overview.md).
 
@@ -58,7 +58,7 @@ The following functionality isn't supported on a WAF policy that's associated wi
 
 ## Pricing
 
-Azure Web Application Firewall usage is billed separately from Application Gateway for Containers usage. When you enable Azure Web Application Firewall on your Application Gateway for Containers resource, two additional WAF-specific meters are added to your bill:
+Azure Web Application Firewall usage is billed separately from Application Gateway for Containers usage. When you enable Azure Web Application Firewall on your Application Gateway for Containers resource, two WAF-specific meters are added to your bill:
 
 - **1 AGC WAF Hour**: A fixed cost charged for the duration that a security policy references a WAF policy.
 - **1M WAF Requests**: A consumption-based meter that bills per 1 million requests processed by the WAF and charges for each enabled rule set. For example, if you enable both the Default Rule Set (DRS) and the Bot Manager Rule Set, you're billed for two rule sets.