Update src/content/docs/reference-architecture/design-guides/streamlined-waf-deployment-across-zones-and-applications.mdx

OK

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: Vortexmind

src/content/docs/reference-architecture/design-guides/streamlined-waf-deployment-across-zones-and-applications.mdx

@@ -64,7 +64,7 @@ The Cloudflare WAF operates at both the zone and the account level. There are di
 
 For the purposes of this guide, we will build on the example scenario and WAF Requirements provided above. You have a single Cloudflare Account (or Enterprise Organization), and two 2nd level domains onboarded on it.
 
-Let's imagine that there are six applications behind six FQDNs across two domains. For these applications, you want to apply apply a baseline WAF security posture. However, of these six applications, two will require a more special treatment:
+Let's imagine that there are six applications behind six FQDNs across two domains. For these applications, you want to apply a baseline WAF security posture. However, of these six applications, two will require a more special treatment:
 
 * One is implemented on a legacy application server, prone to false positives.
 * Another is implemented by a third party on their own infrastrcuture.