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

Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com>
Signed-off-by: Brian Muenzenmeyer <brian.muenzenmeyer@gmail.com>

Author: bmuenzenmeyer

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

@@ -41,6 +41,6 @@ Despite the obvious downsides of using EOL releases, in practice, organizations
 
 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.
 
-TuxCare’s Endless Lifecycle Support (ELS) gives you continued security patching for end-of-life Node.js versions. Security fixes are backported from upstream, tested for integrity and regression, signed, SLA-backed, and delivered through your existing package managers.
+TuxCare’s [Endless Lifecycle Support (ELS)](https://tuxcare.com/endless-lifecycle-support/) gives you continued security patching for end-of-life Node.js versions. Security fixes are backported from upstream, tested for integrity and regression, signed, SLA-backed, and delivered through your existing package managers.
 
 Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions.