Update 2026-04-01.md

Co-authored-by: Matt Cowley <me@mattcowley.co.uk>

Author: avivkeller

incidents/2026-04-01.md

@@ -35,8 +35,7 @@ However, no new release of 25.x has yet been made to be marked as LTS, nor has t
 
 ## Fix
 
-[nodejs/nodejs.org#8787](https://github.com/nodejs/nodejs.org/issues/8787) resolved the issue by changing the detection of a release's `status`
-to require `.lts.isLts` to be `true` before allowing a release to be marked as `Active LTS` or `Maintenance LTS`.
+[nodejs/nodejs.org#8787](https://github.com/nodejs/nodejs.org/issues/8787) resolved the issue by changing the detection of a release's `status` to require `.lts.isLts` to be `true` before allowing a release to be marked as `Active LTS` or `Maintenance LTS`, ensuring that a given major has a valid LTS release available before the website considers it an LTS release.
 
 ## Follow-up Work