Commit f623d5d
doc: use _code name_ rather than _codename_
This is excrutiatingly minor, but every authoritative resource I've
checked (which is to say, a few dictionaries) uses "code name" primarily
or exclusively. Let's follow suit.
PR-URL: #36611
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>1 parent 6e338da commit f623d5d
3 files changed
Lines changed: 6 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -53,7 +53,7 @@ Looking for help? Check out the | |||
| 53 | 53 | * **LTS**: Releases that receive Long-term Support, with a focus on stability | |
| 54 | 54 | and security. Every even-numbered major version will become an LTS release. | |
| 55 | 55 | LTS releases receive 12 months of _Active LTS_ support and a further 18 months | |
| 56 | - of _Maintenance_. LTS release lines have alphabetically-ordered codenames, | ||
| 56 | + of _Maintenance_. LTS release lines have alphabetically-ordered code names, | ||
| 57 | 57 | beginning with v4 Argon. There are no breaking changes or feature additions, | |
| 58 | 58 | except in some special circumstances. | |
| 59 | 59 | * **Nightly**: Code from the Current branch built every 24-hours when there are | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1782,12 +1782,11 @@ tarball. | |||
| 1782 | 1782 | * `lts` {string} a string label identifying the [LTS][] label for this release. | |
| 1783 | 1783 | This property only exists for LTS releases and is `undefined` for all other | |
| 1784 | 1784 | release types, including _Current_ releases. | |
| 1785 | - Valid values include the LTS Release Codenames (including those | ||
| 1786 | - that are no longer supported). A non-exhaustive example of | ||
| 1787 | - these codenames includes: | ||
| 1785 | + Valid values include the LTS Release code names (including those | ||
| 1786 | + that are no longer supported). | ||
| 1788 | 1787 | * `'Dubnium'` for the 10.x LTS line beginning with 10.13.0. | |
| 1789 | 1788 | * `'Erbium'` for the 12.x LTS line beginning with 12.13.0. | |
| 1790 | - For other LTS Release Codenames, see [Node.js Changelog Archive](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_ARCHIVE.md) | ||
| 1789 | + For other LTS Release code names, see [Node.js Changelog Archive](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_ARCHIVE.md) | ||
| 1791 | 1790 | ||
| 1792 | 1791 | <!-- eslint-skip --> | |
| 1793 | 1792 | ```js | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -497,7 +497,7 @@ $ git secure-tag <vx.y.z> <commit-sha> -sm "YYYY-MM-DD Node.js vx.y.z (<release- | |||
| 497 | 497 | ``` | |
| 498 | 498 | ||
| 499 | 499 | `release-type` is either "Current" or "LTS". For LTS releases, you should also | |
| 500 | - include the release codename, for example: | ||
| 500 | + include the release code name. | ||
| 501 | 501 | ||
| 502 | 502 | ```text | |
| 503 | 503 | 2019-10-22 Node.js v10.17.0 'Dubnium' (LTS) Release | |
@@ -740,7 +740,7 @@ To mark a release line as LTS, the following changes must be made to | |||
| 740 | 740 | * The `NODE_MINOR_VERSION` macro must be incremented by one | |
| 741 | 741 | * The `NODE_PATCH_VERSION` macro must be set to `0` | |
| 742 | 742 | * The `NODE_VERSION_IS_LTS` macro must be set to `1` | |
| 743 | - * The `NODE_VERSION_LTS_CODENAME` macro must be set to the codename selected | ||
| 743 | + * The `NODE_VERSION_LTS_CODENAME` macro must be set to the code name selected | ||
| 744 | 744 | for the LTS release. | |
| 745 | 745 | ||
| 746 | 746 | For example: | |
0 commit comments