doc: improve stream documentation

PR-URL: #18375 Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
nodejs · Feb 21, 2018 · 74a823c788d77f22a97ce54d8e95a9ba9c99d82c · 74a823c
1 parent d469a06
commit 74a823c788d77f22a97ce54d8e95a9ba9c99d82c
Showing with 3 additions and 3 deletions.

+3 −3 doc/api/stream.md
diff --git a/doc/api/stream.md b/doc/api/stream.md
@@ -580,8 +580,8 @@ The Readable can switch back to paused mode using one of the following:
 
 * If there are no pipe destinations, by calling the
   [`stream.pause()`][stream-pause] method.
-* If there are pipe destinations, by removing any [`'data'`][] event
-  handlers, and removing all pipe destinations by calling the
+* If there are pipe destinations, by removing all pipe destinations.
+  Multiple pipe destinations may be removed by calling the
   [`stream.unpipe()`][] method.
 
 The important concept to remember is that a Readable will not generate data
@@ -1428,7 +1428,7 @@ write succeeded.
 
 All calls to `writable.write()` that occur between the time `writable._write()`
 is called and the `callback` is called will cause the written data to be
-buffered. Once the `callback` is invoked, the stream will emit a [`'drain'`][]
+buffered. When the `callback` is invoked, the stream might emit a [`'drain'`][]
 event. If a stream implementation is capable of processing multiple chunks of
 data at once, the `writable._writev()` method should be implemented.