doc: standardize on End-of-Life capitalization

Use "End-of-Life" everywhere and not "End-of-life" or "End-Of-Life". PR-URL: nodejs#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>
BridgeAR · Mar 12, 2019 · bd7e243 · bd7e243
1 parent 4b1c1dc
commit bd7e243
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/BUILDING.md b/BUILDING.md
@@ -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                         |

diff --git a/COLLABORATOR_GUIDE.md b/COLLABORATOR_GUIDE.md
@@ -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.