doc: clarify timing of socket.connecting

Fixes: #25328 PR-URL: #25333 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
nodejs · May 16, 2019 · ce3cf0dffdc83069298632ed03fc1f2761074b35 · ce3cf0d
1 parent 858a42e
commit ce3cf0dffdc83069298632ed03fc1f2761074b35
Showing with 5 additions and 4 deletions.

+5 −4 doc/api/net.md
diff --git a/doc/api/net.md b/doc/api/net.md
@@ -659,11 +659,12 @@ added: v6.1.0
 -->
 
 If `true`,
+[`socket.connect(options[, connectListener])`][`socket.connect(options)`] was
+called and has not yet finished. It will stay `true` until the socket becomes
+connected, then it is set to `false` and the `'connect'` event is emitted.  Note
+that the
 [`socket.connect(options[, connectListener])`][`socket.connect(options)`]
-was called and has not yet finished. Will be set to `true` before emitting
-`'connect'` event and/or calling
-[`socket.connect(options[, connectListener])`][`socket.connect(options)`]'s
-callback.
+callback is a listener for the `'connect'` event.
 
 ### socket.destroy([exception])
 <!-- YAML