Skip to content

Commit 74a823c

Browse files
陈刚MylesBorins
陈刚
authored andcommitted
doc: improve stream documentation
PR-URL: #18375 Reviewed-By: Jon Moss <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
1 parent d469a06 commit 74a823c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/api/stream.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -580,8 +580,8 @@ The Readable can switch back to paused mode using one of the following:
580580

581581
* If there are no pipe destinations, by calling the
582582
[`stream.pause()`][stream-pause] method.
583-
* If there are pipe destinations, by removing any [`'data'`][] event
584-
handlers, and removing all pipe destinations by calling the
583+
* If there are pipe destinations, by removing all pipe destinations.
584+
Multiple pipe destinations may be removed by calling the
585585
[`stream.unpipe()`][] method.
586586

587587
The important concept to remember is that a Readable will not generate data
@@ -1428,7 +1428,7 @@ write succeeded.
14281428

14291429
All calls to `writable.write()` that occur between the time `writable._write()`
14301430
is called and the `callback` is called will cause the written data to be
1431-
buffered. Once the `callback` is invoked, the stream will emit a [`'drain'`][]
1431+
buffered. When the `callback` is invoked, the stream might emit a [`'drain'`][]
14321432
event. If a stream implementation is capable of processing multiple chunks of
14331433
data at once, the `writable._writev()` method should be implemented.
14341434

0 commit comments

Comments
 (0)