doc: fix net.Socket link inconsistencies
PR-URL: https://github.com/nodejs/node/pull/20271 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
This commit is contained in:
parent
d3edf2fcde
commit
214fd404b9
@ -77,8 +77,8 @@ Note that `CTRL`+`C` will no longer cause a `SIGINT` when in this mode.
|
|||||||
added: v0.5.8
|
added: v0.5.8
|
||||||
-->
|
-->
|
||||||
|
|
||||||
The `tty.WriteStream` class is a subclass of `net.Socket` that represents the
|
The `tty.WriteStream` class is a subclass of [`net.Socket`][] that represents
|
||||||
writable side of a TTY. In normal circumstances, [`process.stdout`][] and
|
the writable side of a TTY. In normal circumstances, [`process.stdout`][] and
|
||||||
[`process.stderr`][] will be the only `tty.WriteStream` instances created for a
|
[`process.stderr`][] will be the only `tty.WriteStream` instances created for a
|
||||||
Node.js process and there should be no reason to create additional instances.
|
Node.js process and there should be no reason to create additional instances.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user