Update apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md

Co-authored-by: Joyee Cheung <[email protected]>
Signed-off-by: Matteo Collina <[email protected]>

Author: mcollina

apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md

@@ -296,7 +296,7 @@ The error originated in **user code** (the recursive pattern), but because it ma
 
 While this issue has significant practical impact, we want to be clear about why Node.js is treating this fix as a mere mitigation of security vulnerability risks at large:
 
-### Stack Overflow Is Not Specified Behavior
+### Stack Space Exhaustion Is Not Specified Behavior
 
 The "Maximum call stack size exceeded" error is not part of the ECMAScript specification. The specification assumes infinite stack space; imposing a limit and throwing an error is simply behavior that JavaScript engines implement on a best-effort basis. Building a security model on top of an undocumented, unspecified feature that isn't guaranteed to work consistently would be unreliable.