From 80268851284e86ff13f49e6fb2dd36248c746180 Mon Sep 17 00:00:00 2001
From: Benjamin Cabanes <3447705+bcabanes@users.noreply.github.com>
Date: Fri, 20 Jun 2025 16:59:15 -0400
Subject: [PATCH] docs(nx-dev): fix typo (#31677)

Update callout type from 'warn' to 'warning' in CVE blog post.
---
 ...e-2025-36852-critical-cache-poisoning-vulnerability-creep.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/blog/2025-06-12-cve-2025-36852-critical-cache-poisoning-vulnerability-creep.md b/docs/blog/2025-06-12-cve-2025-36852-critical-cache-poisoning-vulnerability-creep.md
index de6d2ed790..3f530ebc3f 100644
--- a/docs/blog/2025-06-12-cve-2025-36852-critical-cache-poisoning-vulnerability-creep.md
+++ b/docs/blog/2025-06-12-cve-2025-36852-critical-cache-poisoning-vulnerability-creep.md
@@ -18,7 +18,7 @@ The CREEP vulnerability allows any contributor with pull request privileges to i
 - Nx Cloud is **NOT** affected due to its security architecture
 - Review this post to determine if your self-hosted cache solution is vulnerable
 
-{% callout type="warn" title="DIY implementations are vulnerable" %}
+{% callout type="warning" title="DIY implementations are vulnerable" %}
 DIY remote caches are likely vulnerable. Scanners won't catch all affected implementations, so understanding the vulnerability is crucial.
 {% /callout %}