diff --git a/src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx b/src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx
index e11db0f131b..2f1ed47038e 100644
--- a/src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx
+++ b/src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx
@@ -21,3 +21,4 @@ While loading a Challenge Page, the visitor's browser may attempt to retrieve a
 This `401` is expected and does **not** mean the visitor is blocked. The Private Access Token flow is an optimization used to reduce challenge steps. When a token is unavailable, Cloudflare falls back to a standard challenge and the visitor continues through the Challenge Page as usual.
 
 If you are inspecting network requests in your browser's developer tools and notice a `401` on a `/cdn-cgi/challenge-platform/.../pat/...` request, you can safely disregard it. It is part of normal challenge processing and is not the cause of a block.
+control+shift+m alternar el tap