Update apps/site/pages/en/about/eol.mdx

Co-authored-by: Jordan Harband <ljharb@gmail.com>
Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

Author: bjohansebas

apps/site/pages/en/about/eol.mdx

@@ -37,7 +37,7 @@ When a version reaches End-Of-Life, it means that it will no longer receive upda
 
 ## Commercial Support
 
-Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. Through the [OpenJS Foundation Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program), Node.js is supported by HeroDevs, NodeSource and TuxCare to provide commercial services for security fixes.
+Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. Through the [OpenJS Foundation Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program), Node.js is supported by HeroDevs, NodeSource, and TuxCare to provide commercial services for security fixes.
 
 HeroDevs provides [Never-Ending Support (NES)](https://nodejs.org/esp/herodevs) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy.