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

Co-authored-by: Darshan Sen <raisinten@gmail.com>
Signed-off-by: Claudio Wunder <cwunder@gnome.org>

Author: ovflowd

apps/site/pages/en/eol.mdx

@@ -27,7 +27,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. For users who cannot upgrade immediately but needs continued security support for End-Of-Life versions of Node.js, commercial support is available through the [OpenJS Ecosystem Sustainability Program](https://openjsf.org/partners) partnership.
+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. For users who cannot upgrade immediately but needs continued security support for End-Of-Life versions of Node.js, commercial support is available through the [OpenJS Ecosystem Sustainability Program](https://openjsf.org/blog/ecosystem-sustainability-program) partnership.
 
 Node.js currently partners with HeroDevs to provide Never-Ending Support (NES) 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. For more detailed information, visit the [**HeroDevs Node.js NES page**](https://www.herodevs.com/support/node-nes?utm_source=NodeJS+&utm_medium=Link&utm_campaign=Nodejs_eol_support).