Update _posts/2025-05-19-journey-to-find-replacements-java-security-manager.md

Co-authored-by: Nathan Bower <[email protected]>
Signed-off-by: Gulshan <[email protected]>

Author: kumargu

_posts/2025-05-19-journey-to-find-replacements-java-security-manager.md

@@ -12,7 +12,7 @@ meta_keywords: Opensearch security, Java security manager, OpenSearch 3.0, secur
 meta_description: The Java Security Manager (JSM) has long been a foundational security mechanism in OpenSearch. With its deprecation underway, this blog post explores the alternative technologies adopted to replace JSM.
 ---
 
-[OpenSearch 3.0.0](https://opensearch.org/blog/unveiling-opensearch-3-0/) introduced many innovative features that continue to push the frontier with significant advancements in performance, data management, vector database functionality, and more. In the announcement, we shared that OpenSearch has replaced JSM (JSM) because of its upcoming deprecation. In this blog post, and we'll to share more details about the efforts that enabled this transition.
+OpenSearch 3.0.0 introduced many innovative features that provide significant advancements in performance, data management, vector database functionality, and more. In [the release announcement](https://opensearch.org/blog/unveiling-opensearch-3-0/), we shared that OpenSearch has replaced the Java Security Manager (JSM) because of its upcoming deprecation. In this blog post, we share more information about the efforts that enabled this transition.
 
 The decision to remove JSM in 3.0 was carefully considered and primarily driven by two factors: