doc: fix wrong response.end() at request.socket

PR-URL: nodejs#19507 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Shigeki Ohtsu <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
Hailong · Apr 13, 2018 · 019a2c4 · 019a2c4
1 parent 7101107
commit 019a2c4
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/doc/api/http.md b/doc/api/http.md
@@ -676,9 +676,8 @@ added: v0.3.0
 
 Reference to the underlying socket. Usually users will not want to access
 this property. In particular, the socket will not emit `'readable'` events
-because of how the protocol parser attaches to the socket. After
-`response.end()`, the property is nulled. The `socket` may also be accessed
-via `request.connection`.
+because of how the protocol parser attaches to the socket. The `socket`
+may also be accessed via `request.connection`.
 
 Example: