mirror of
https://github.com/zebrajr/node.git
synced 2025-12-06 12:20:27 +01:00
doc: use "Long Term Support" in README
"Long-Term Support" should have a capital "T" according to most style guides if we're making it a proper noun as we are here. It's obviously not super important in the grand scope of the project, but it makes things appear more formal and correct. PR-URL: https://github.com/nodejs/node/pull/38839 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This commit is contained in:
parent
1dc71da302
commit
dfe9698db0
|
|
@ -50,7 +50,7 @@ Looking for help? Check out the
|
||||||
April and October every year. Releases appearing each October have a support
|
April and October every year. Releases appearing each October have a support
|
||||||
life of 8 months. Releases appearing each April convert to LTS (see below)
|
life of 8 months. Releases appearing each April convert to LTS (see below)
|
||||||
each October.
|
each October.
|
||||||
* **LTS**: Releases that receive Long-term Support, with a focus on stability
|
* **LTS**: Releases that receive Long Term Support, with a focus on stability
|
||||||
and security. Every even-numbered major version will become an LTS release.
|
and security. Every even-numbered major version will become an LTS release.
|
||||||
LTS releases receive 12 months of _Active LTS_ support and a further 18 months
|
LTS releases receive 12 months of _Active LTS_ support and a further 18 months
|
||||||
of _Maintenance_. LTS release lines have alphabetically-ordered code names,
|
of _Maintenance_. LTS release lines have alphabetically-ordered code names,
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user