From be30fe0e7a5c2d3d001a9bdd625ce3efde9b6bb3 Mon Sep 17 00:00:00 2001
From: sainadh777 <31940823+sainadh777@users.noreply.github.com>
Date: Mon, 27 Jul 2026 07:43:56 -0700
Subject: [PATCH] Fix typo in 2025 Next Steps

---
 2025/docs/en/X01_2025-Next_Steps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/2025/docs/en/X01_2025-Next_Steps.md b/2025/docs/en/X01_2025-Next_Steps.md
index 6c4ca6cf4..126080b8e 100644
--- a/2025/docs/en/X01_2025-Next_Steps.md
+++ b/2025/docs/en/X01_2025-Next_Steps.md
@@ -153,7 +153,7 @@ In order to prevent this type of vulnerability you must design for failure and r
 
 ### Background. 
 
-Languagess like Java, C#, JavaScript/TypeScript (node.js), Go, and "safe" Rust are memory safe. Memory management problems tend to happen in non-memory safe languages such as C and C++. This category scored the lowest on the community survey and low in the data despite having the third most related CVEs. We believe this is due to the predominance of web applications over more traditional desktop applications. Memory management vulnerabilities frequently have the highest CVSS scores. 
+Languages like Java, C#, JavaScript/TypeScript (node.js), Go, and "safe" Rust are memory safe. Memory management problems tend to happen in non-memory safe languages such as C and C++. This category scored the lowest on the community survey and low in the data despite having the third most related CVEs. We believe this is due to the predominance of web applications over more traditional desktop applications. Memory management vulnerabilities frequently have the highest CVSS scores.
 
 
 ### Score table.