doc: revise socket.connect() note

Trott · addaleax · commit 87136c9bde8e · 2019-11-30T03:58:00.000+01:00
Edit note in about `onread` option to `socket.connect()` for clarity. PR-URL: #30691 Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
diff --git a/doc/api/net.md b/doc/api/net.md
@@ -650,9 +650,9 @@ For both types, available `options` include:
 
 * `onread` {Object} If specified, incoming data is stored in a single `buffer`
   and passed to the supplied `callback` when data arrives on the socket.
-  Note: this will cause the streaming functionality to not provide any data,
-  however events like `'error'`, `'end'`, and `'close'` will still be emitted
-  as normal and methods like `pause()` and `resume()` will also behave as
+  This will cause the streaming functionality to not provide any data.
+  The socket will emit events like `'error'`, `'end'`, and `'close'`
+  as usual. Methods like `pause()` and `resume()` will also behave as
   expected.
   * `buffer` {Buffer|Uint8Array|Function} Either a reusable chunk of memory to
     use for storing incoming data or a function that returns such.
