docs: improve readability

- Fix Alpha duration from 5 to 6 months (Oct-Mar)
- Correct LTS duration from 29 to 30 months
- Update total support from 35 to 36 months
- Update all EOL dates from March to April
- Add alpha versioning format example (27.0.0-alpha.1)
- Clarify version number alignment wording
- Clarify "from first Current release" for total support
- Fix grammar: "to not be" → "not to be"
- Fix grammar: "may be not included" → "may not be included"
- Improve readability by breaking long lines

Co-authored-by: Richard Lau <5445507+richardlau@users.noreply.github.com>
Co-authored-by: Nick Schonning <1297909+nschonni@users.noreply.github.com>

Author: 3 people

apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md

@@ -52,33 +52,35 @@ As of October 2026:
 - **One major release per year** (April), with LTS promotion in October.
 - **Every release becomes LTS**. No more odd/even distinction - Node.js 27 will become LTS.
 - **Alpha channel for early testing** with semver-major changes allowed.
-- **Version numbers align with the year of the first Current release and transition to LTS**: 27.0.0 in 2027, 28.0.0 in 2028.
+- **Alpha versioning** follows semver prerelease format (e.g., `27.0.0-alpha.1`).
+- **Version numbers align with the calendar year of their initial Current release**: 27.0.0 in 2027, 28.0.0 in 2028.
 - **Reduced Releasers' burden**.
 
 ### New Schedule
 
 | Phase   | Duration  | Description                                     |
 | ------- | --------- | ----------------------------------------------- |
-| Alpha   | 5 months  | Oct to Mar. Early testing, semver-major allowed |
+| Alpha   | 6 months  | Oct to Mar. Early testing, semver-major allowed |
 | Current | 6 months  | Apr to Oct. Stabilization                       |
-| LTS     | 29 months | Long-term support with security fixes           |
+| LTS     | 30 months | Long-term support with security fixes           |
 | EOL     | Infinity  | The project no longer provides any support      |
 
-Total support: 35 months from release to [End of Life (EOL)](https://nodejs.org/en/about/eol).
+Total support: 36 months from first Current release to [End of Life (EOL)](https://nodejs.org/en/about/eol).
 
 ### About the Alpha Channel
 
-The Alpha channel fills the early-testing role that odd-numbered releases once served, but with a key difference: semver-major changes are allowed during Alpha. Alpha releases are signed,
-tagged, and tested through [CITGM](https://github.com/nodejs/citgm). CITGM (Canary in the Goldmine) is a tool we
+The Alpha channel fills the early-testing role that odd-numbered releases once served,
+but with a key difference: semver-major changes are allowed during Alpha.
+Alpha releases are signed, tagged, and tested through [CITGM](https://github.com/nodejs/citgm). CITGM (Canary in the Goldmine) is a tool we
 maintain that runs the test suite of major open-source packages on the upcoming
 version of Node.js, which can let us detect ecosystem breakage and notify the
 package authors ahead of the release.
 
 This is different from [Nightly builds](https://nodejs.org/download/nightly/), which remain
 available as automated untested builds from `main` – Alpha releases may not contain all changes from
-`main`, a change may be not included in an Alpha release if:
+`main`, a change may not be included in an Alpha release if:
 
-- during Pull Request review, reviewers add a label requesting the change to not be backported
+- during Pull Request review, reviewers add a label requesting the change not to be backported
   (e.g. if an API is getting runtime deprecated in an Alpha release, the change actually removing
   that API should not land until the next release line).
 - during the Alpha release preparation, the releaser ultimately decides which commits actually make the
@@ -89,7 +91,6 @@ upcoming breaking changes. Not intended for production use.
 
 **What to expect:**
 
-- Semver-major changes may land during this phase.
 - Releases are signed and tagged (unlike nightly).
 - API may change between releases.
 - The release cadence is flexible; the Release Team will determine the timing
@@ -103,7 +104,7 @@ the Release Team and documented in the [Release repository](https://github.com/n
 
 ## What's NOT Changing
 
-- **Long-Term Support duration** remains similar (29 months).
+- **Long-Term Support duration** remains similar (30 months).
 - **Migration windows preserved**. Overlap between LTS versions remains.
 - **Quality standards unchanged**. Same testing, same CITGM, same security process.
 - **Predictable schedule**. April releases, October LTS promotion.
@@ -132,24 +133,24 @@ Node.js 26 follows the existing schedule. This is the last release line under th
 | Alpha begins | October 2026 |
 | 27.0.0       | April 2027   |
 | Enters LTS   | October 2027 |
-| End of Life  | March 2030   |
+| End of Life  | April 2030   |
 
 Node.js 27 is the first release line under the new schedule.
 
 ### The Next 10 Years
 
 | Version | Alpha    | Current  | LTS      | End of Life |
 | ------- | -------- | -------- | -------- | ----------- |
-| 27.x    | Oct 2026 | Apr 2027 | Oct 2027 | Mar 2030    |
-| 28.x    | Oct 2027 | Apr 2028 | Oct 2028 | Mar 2031    |
-| 29.x    | Oct 2028 | Apr 2029 | Oct 2029 | Mar 2032    |
-| 30.x    | Oct 2029 | Apr 2030 | Oct 2030 | Mar 2033    |
-| 31.x    | Oct 2030 | Apr 2031 | Oct 2031 | Mar 2034    |
-| 32.x    | Oct 2031 | Apr 2032 | Oct 2032 | Mar 2035    |
-| 33.x    | Oct 2032 | Apr 2033 | Oct 2033 | Mar 2036    |
-| 34.x    | Oct 2033 | Apr 2034 | Oct 2034 | Mar 2037    |
-| 35.x    | Oct 2034 | Apr 2035 | Oct 2035 | Mar 2038    |
-| 36.x    | Oct 2035 | Apr 2036 | Oct 2036 | Mar 2039    |
+| 27.x    | Oct 2026 | Apr 2027 | Oct 2027 | Apr 2030    |
+| 28.x    | Oct 2027 | Apr 2028 | Oct 2028 | Apr 2031    |
+| 29.x    | Oct 2028 | Apr 2029 | Oct 2029 | Apr 2032    |
+| 30.x    | Oct 2029 | Apr 2030 | Oct 2030 | Apr 2033    |
+| 31.x    | Oct 2030 | Apr 2031 | Oct 2031 | Apr 2034    |
+| 32.x    | Oct 2031 | Apr 2032 | Oct 2032 | Apr 2035    |
+| 33.x    | Oct 2032 | Apr 2033 | Oct 2033 | Apr 2036    |
+| 34.x    | Oct 2033 | Apr 2034 | Oct 2034 | Apr 2037    |
+| 35.x    | Oct 2034 | Apr 2035 | Oct 2035 | Apr 2038    |
+| 36.x    | Oct 2035 | Apr 2036 | Oct 2036 | Apr 2039    |
 
 This schedule is not final and may be amended. Refer to the
 [`schedule.json`](https://github.com/nodejs/Release/blob/HEAD/schedule.json) for an up-to-date