Skip to content

Commit 9945c28

Browse files
TrottBridgeAR
authored andcommitted
doc: standardize on End-of-Life capitalization
Use "End-of-Life" everywhere and not "End-of-life" or "End-Of-Life". PR-URL: #26442 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
1 parent 6cc559f commit 9945c28

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

BUILDING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ There are three support tiers:
7272
For production applications, run Node.js on supported platforms only.
7373

7474
Node.js does not support a platform version if a vendor has expired support
75-
for it. In other words, Node.js does not support running on End-of-life (EoL)
75+
for it. In other words, Node.js does not support running on End-of-Life (EoL)
7676
platforms. This is true regardless of entries in the table below.
7777

7878
| System | Support type | Version | Architectures | Notes |

COLLABORATOR_GUIDE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -359,7 +359,7 @@ the three Deprecation levels. Documentation-Only Deprecations may land in a
359359
minor release. They may not change to a Runtime Deprecation until the next major
360360
release.
361361

362-
No API can change to End-of-life without going through a Runtime Deprecation
362+
No API can change to End-of-Life without going through a Runtime Deprecation
363363
cycle. There is no rule that deprecated code must progress to End-of-Life.
364364
Documentation-Only and Runtime Deprecations may remain in place for an unlimited
365365
duration.

0 commit comments

Comments
 (0)