doc: use Node.js instead of Node

Per branding guidelines from the Foundation, use Node.js and not Node.

PR-URL: #23967
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

Author: Trott

doc/api/cli.md

@@ -553,7 +553,7 @@ if they had been specified on the command line before the actual command line
 (so they can be overridden). Node.js will exit with an error if an option
 that is not allowed in the environment is used, such as `-p` or a script file.
 
-Node options that are allowed are:
+Node.js options that are allowed are:
 - `--enable-fips`
 - `--experimental-modules`
 - `--experimental-repl-await`

doc/api/documentation.md

@@ -82,7 +82,7 @@ pages (short for manual pages) which describe how the syscalls work.
 
 Most Unix syscalls have Windows equivalents, but behavior may differ on Windows
 relative to Linux and macOS. For an example of the subtle ways in which it's
-sometimes impossible to replace Unix syscall semantics on Windows, see [Node
+sometimes impossible to replace Unix syscall semantics on Windows, see [Node.js
 issue 4760](https://github.com/nodejs/node/issues/4760).
 
 [`'warning'`]: process.html#process_event_warning

doc/api/inspector.md

@@ -144,7 +144,7 @@ session.post('Runtime.evaluate', { expression: '2 + 2' },
 The latest version of the V8 inspector protocol is published on the
 [Chrome DevTools Protocol Viewer][].
 
-Node inspector supports all the Chrome DevTools Protocol domains declared
+Node.js inspector supports all the Chrome DevTools Protocol domains declared
 by V8. Chrome DevTools Protocol domain provides an interface for interacting
 with one of the runtime agents used to inspect the application state and listen
 to the run-time events.

doc/api/modules.md

@@ -376,8 +376,9 @@ Error: Cannot find module 'some-library'
 If the module identifier passed to `require()` is not a
 [core](#modules_core_modules) module, and does not begin with `'/'`, `'../'`, or
 `'./'`, then Node.js starts at the parent directory of the current module, and
-adds `/node_modules`, and attempts to load the module from that location. Node
-will not append `node_modules` to a path already ending in `node_modules`.
+adds `/node_modules`, and attempts to load the module from that location.
+Node.js will not append `node_modules` to a path already ending in
+`node_modules`.
 
 If it is not found there, then it moves to the parent directory, and so
 on, until the root of the file system is reached.

doc/guides/node-postmortem-support.md

@@ -15,8 +15,8 @@ Node.js always includes these constants in the final build.
 
 ### Node.js Debug Symbols
 
-Node prefixes all postmortem constants with `nodedbg_`, and they complement V8
-constants by providing ways to inspect Node-specific structures, like
+Node.js prefixes all postmortem constants with `nodedbg_`, and they complement
+V8 constants by providing ways to inspect Node.js-specific structures, like
 `node::Environment`, `node::BaseObject` and its descendants, classes from
 `src/utils.h` and others. Those constants are declared in
 `src/node_postmortem_metadata.cc`, and most of them are calculated at compile
@@ -63,7 +63,7 @@ class ReqWrap : public AsyncWrap {
 ```
 
 There are also tests on `test/cctest/test_node_postmortem_metadata.cc` to make
-sure all Node postmortem metadata are calculated correctly.
+sure all Node.js postmortem metadata are calculated correctly.
 
 ## Tools and References
 

doc/node.1

@@ -246,7 +246,7 @@ Evaluate
 as JavaScript.
 .
 .It Fl h , Fl -help
-Print node command line options.
+Print Node.js command line options.
 The output of this option is less detailed than this document.
 .
 .It Fl i , Fl -interactive
@@ -263,7 +263,7 @@ Preload the specified
 at startup.
 Follows `require()`'s module resolution rules.
 .Ar module
-may be either a path to a file, or a node module name.
+may be either a path to a file, or a Node.js module name.
 .
 .It Fl v , Fl -version
 Print node's version.
@@ -309,7 +309,7 @@ process warnings are silenced.
 A space-separated list of command-line
 .Ar options ,
 which are interpreted as if they had been specified on the command-line before the actual command (so they can be overridden).
-Node will exit with an error if an option that is not allowed in the environment is used, such as
+Node.js will exit with an error if an option that is not allowed in the environment is used, such as
 .Fl -print
 or a script file.
 .