daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: standardize on End-of-Life capitalization 

Use "End-of-Life" everywhere and not "End-of-life" or "End-Of-Life".

PR-URL: https://github.com/nodejs/node/pull/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>
pull/26465/head
Rich Trott 2019-03-04 15:32:34 -08:00
parent d50fc510a8
commit 7ffbb4606f
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
BUILDING.md
View File

@ -72,7 +72,7 @@ There are three support tiers:
For production applications, run Node.js on supported platforms only.
Node.js does not support a platform version if a vendor has expired support
for it. In other words, Node.js does not support running on End-of-life (EoL)
for it. In other words, Node.js does not support running on End-of-Life (EoL)
platforms. This is true regardless of entries in the table below.
| System | Support type | Version | Architectures | Notes |

2
COLLABORATOR_GUIDE.md
View File

@ -359,7 +359,7 @@ the three Deprecation levels. Documentation-Only Deprecations may land in a
minor release. They may not change to a Runtime Deprecation until the next major
release.
No API can change to End-of-life without going through a Runtime Deprecation
No API can change to End-of-Life without going through a Runtime Deprecation
cycle. There is no rule that deprecated code must progress to End-of-Life.
Documentation-Only and Runtime Deprecations may remain in place for an unlimited
duration.