@@ -429,7 +429,7 @@ process.on('SIGTERM', handle);
429429 removed (Node.js will no longer exit).
430430* `'SIGPIPE'` is ignored by default. It can have a listener installed.
431431* `'SIGHUP'` is generated on Windows when the console window is closed, and on
432- other platforms under various similar conditions, see signal(7). It can have a
432+ other platforms under various similar conditions. See signal(7). It can have a
433433 listener installed, however Node.js will be unconditionally terminated by
434434 Windows about 10 seconds later. On non-Windows platforms, the default
435435 behavior of `SIGHUP` is to terminate Node.js, but once a listener has been
@@ -1382,7 +1382,7 @@ process.kill(process.pid, 'SIGHUP');
13821382```
13831383
13841384When `SIGUSR1` is received by a Node.js process, Node.js will start the
1385- debugger, see [Signal Events][].
1385+ debugger. See [Signal Events][].
13861386
13871387## process.mainModule
13881388<!-- YAML
@@ -1840,7 +1840,7 @@ The `process.stderr` property returns a stream connected to
18401840stream) unless fd `2` refers to a file, in which case it is
18411841a [Writable][] stream.
18421842
1843- `process.stderr` differs from other Node.js streams in important ways, see
1843+ `process.stderr` differs from other Node.js streams in important ways. See
18441844[note on process I/O][] for more information.
18451845
18461846## process.stdin
@@ -1890,7 +1890,7 @@ For example, to copy `process.stdin` to `process.stdout`:
18901890process.stdin.pipe(process.stdout);
18911891```
18921892
1893- `process.stdout` differs from other Node.js streams in important ways, see
1893+ `process.stdout` differs from other Node.js streams in important ways. See
18941894[note on process I/O][] for more information.
18951895
18961896### A note on process I/O
0 commit comments