Commit 171cbb1
doc: fix net.Socket link inconsistencies
PR-URL: #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>1 parent 6bf816f commit 171cbb1
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -77,8 +77,8 @@ Note that `CTRL`+`C` will no longer cause a `SIGINT` when in this mode. | |||
| 77 | 77 | added: v0.5.8 | |
| 78 | 78 | --> | |
| 79 | 79 | ||
| 80 | - The `tty.WriteStream` class is a subclass of `net.Socket` that represents the | ||
| 81 | - writable side of a TTY. In normal circumstances, [`process.stdout`][] and | ||
| 80 | + The `tty.WriteStream` class is a subclass of [`net.Socket`][] that represents | ||
| 81 | + the writable side of a TTY. In normal circumstances, [`process.stdout`][] and | ||
| 82 | 82 | [`process.stderr`][] will be the only `tty.WriteStream` instances created for a | |
| 83 | 83 | Node.js process and there should be no reason to create additional instances. | |
| 84 | 84 | ||
0 commit comments