diff options
Diffstat (limited to 'doc/guides')
| -rw-r--r-- | doc/guides/backporting-to-release-lines.md | 2 | ||||
| -rw-r--r-- | doc/guides/maintaining-V8.md | 2 | ||||
| -rw-r--r-- | doc/guides/maintaining-the-build-files.md | 2 | ||||
| -rw-r--r-- | doc/guides/using-internal-errors.md | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/guides/backporting-to-release-lines.md b/doc/guides/backporting-to-release-lines.md index 150a1248b1..5b531639e7 100644 --- a/doc/guides/backporting-to-release-lines.md +++ b/doc/guides/backporting-to-release-lines.md @@ -6,7 +6,7 @@ Each release line has a staging branch that the releaser will use as a scratch pad while preparing a release. The branch name is formatted as follows: `vN.x-staging` where `N` is the major release number. -*Note*: For the active staging branches see the [Release Schedule][]. +For the active staging branches see the [Release Schedule][]. ## What needs to be backported? diff --git a/doc/guides/maintaining-V8.md b/doc/guides/maintaining-V8.md index 4606b1897a..ccc3257c7a 100644 --- a/doc/guides/maintaining-V8.md +++ b/doc/guides/maintaining-V8.md @@ -228,7 +228,7 @@ to be cherry-picked in the Node.js repository and V8-CI must test the change. * Open a cherry-pick PR on `nodejs/node` targeting the *vY.x-staging* branch and notify the `@nodejs/v8` team. * Run the Node.js [V8 CI] in addition to the [Node.js CI]. - Note: The CI uses the `test-v8` target in the `Makefile`, which uses + The CI uses the `test-v8` target in the `Makefile`, which uses `tools/make-v8.sh` to reconstruct a git tree in the `deps/v8` directory to run V8 tests. diff --git a/doc/guides/maintaining-the-build-files.md b/doc/guides/maintaining-the-build-files.md index f3f7bbf5e2..2f89362b8f 100644 --- a/doc/guides/maintaining-the-build-files.md +++ b/doc/guides/maintaining-the-build-files.md @@ -11,7 +11,7 @@ There are three main build files that may be directly run when building Node.js: - `configure`: A Python 2 script that detects system capabilities and runs [GYP][]. It generates `config.gypi` which includes parameters used by GYP to create platform-dependent build files. Its output is usually in one of these - formats: Makefile, MSbuild, ninja, or XCode project files. (Note: the main + formats: Makefile, MSbuild, ninja, or XCode project files (the main Makefile mentioned below is maintained separately by humans). For a detailed guide on this script, see [configure](#configure). - `vcbuild.bat`: A Windows Batch Script that locates build tools, provides a diff --git a/doc/guides/using-internal-errors.md b/doc/guides/using-internal-errors.md index d22fc68e0f..77eabb4ad4 100644 --- a/doc/guides/using-internal-errors.md +++ b/doc/guides/using-internal-errors.md @@ -14,7 +14,7 @@ in the ecosystem. For that reason, Node.js has considered error message changes to be breaking changes. By providing a permanent identifier for a specific error, we reduce the need for userland code to inspect error messages. -*Note*: Switching an existing error to use the `internal/errors` module must be +Switching an existing error to use the `internal/errors` module must be considered a `semver-major` change. ## Using internal/errors.js |