diff --git a/apps/site/pages/en/about/previous-releases.mdx b/apps/site/pages/en/about/previous-releases.mdx
index 01aa12d5e4a59..325109eb8b351 100644
--- a/apps/site/pages/en/about/previous-releases.mdx
+++ b/apps/site/pages/en/about/previous-releases.mdx
@@ -10,11 +10,11 @@ layout: about
Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them.
After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
-Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.
+Production applications should only use LTS releases.
## Release Schedule
-
+
Full details regarding the Node.js release schedule are available [on GitHub](https://github.com/nodejs/release#release-schedule).
diff --git a/packages/i18n/src/locales/en.json b/packages/i18n/src/locales/en.json
index d177c91c3a4ef..d1459849d1060 100644
--- a/packages/i18n/src/locales/en.json
+++ b/packages/i18n/src/locales/en.json
@@ -93,7 +93,7 @@
"ltsVersionFeaturesNotice": "Want new features sooner? Get the latest Node.js version instead and try the latest improvements!"
},
"eolAlert": {
- "message": "Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partners"
+ "message": "Commercial support for versions past the LTS phase is available through our OpenJS Ecosystem Sustainability Program partners"
},
"eolChip": {
"severity": {