GeezerVison is showing github.com — doc: clarify socket destroyed behavior · nodejs/node@96b91dc
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/net.md +3-3Lines changed: 3 additions & 3 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -1408,15 +1408,15 @@ added: v0.1.90 |
1408 | 1408 | * `error` {Object} |
1409 | 1409 | * Returns: {net.Socket} |
1410 | 1410 |
|
1411 | | -Ensures that no more I/O activity happens on this socket. |
| 1411 | +Ensures that no more I/O activity happens on the current connection. |
1412 | 1412 | Destroys the stream and closes the connection. |
1413 | 1413 |
|
1414 | 1414 | See [`writable.destroy()`][] for further details. |
1415 | 1415 |
|
1416 | 1416 | ### `socket.destroyed` |
1417 | 1417 |
|
1418 | | -* Type: {boolean} Indicates if the connection is destroyed or not. Once a |
1419 | | - connection is destroyed no further data can be transferred using it. |
| 1418 | +* Type: {boolean} Indicates if the connection is destroyed or not. No further |
| 1419 | + data can be transferred using a destroyed connection. |
1420 | 1420 |
|
1421 | 1421 | See [`writable.destroyed`][] for further details. |
1422 | 1422 |
|
|