From ebe2c22c73cab877fef69020b3b0626f5bfc47a9 Mon Sep 17 00:00:00 2001
From: Pedro Sousa <680496+pedrosousa@users.noreply.github.com>
Date: Thu, 24 Jul 2025 12:03:47 +0100
Subject: [PATCH] [WAF] Fix page title

---
 src/content/docs/waf/rate-limiting-rules/best-practices.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/docs/waf/rate-limiting-rules/best-practices.mdx b/src/content/docs/waf/rate-limiting-rules/best-practices.mdx
index c78ff6ae98cb2c1..3edf0e190c16a01 100644
--- a/src/content/docs/waf/rate-limiting-rules/best-practices.mdx
+++ b/src/content/docs/waf/rate-limiting-rules/best-practices.mdx
@@ -1,5 +1,5 @@
 ---
-title: Rate limiting practices
+title: Rate limiting best practices
 pcx_content_type: configuration
 sidebar:
   order: 21
@@ -415,4 +415,4 @@ When the origin server processes a request, it adds a `score` HTTP header to the
 
 API Shield customers can use GraphQL malicious query protection to protect their GraphQL APIs. GraphQL malicious query protection scans your GraphQL traffic for queries that could overload your origin and result in a denial of service. You can build rules that limit the query depth and size of incoming GraphQL queries in order to block suspiciously large or complex queries.
 
-Refer to [API Shield documentation](https://developers.cloudflare.com/api-shield/security/graphql-protection/) for more information on GraphQL malicious query protection.
\ No newline at end of file
+Refer to [API Shield documentation](https://developers.cloudflare.com/api-shield/security/graphql-protection/) for more information on GraphQL malicious query protection.