Skip to content

Commit

Permalink
doc: use "Long Term Support" in README
Browse files Browse the repository at this point in the history
"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: #38839
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
  • Loading branch information
phershbe authored and Trott committed May 30, 2021
1 parent 4c508f5 commit 16ae378
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Looking for help? Check out the
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)
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.
LTS releases receive 12 months of _Active LTS_ support and a further 18 months
of _Maintenance_. LTS release lines have alphabetically-ordered code names,
Expand Down

0 comments on commit 16ae378

Please sign in to comment.