summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuigi Pinca <luigipinca@gmail.com>2019-03-06 10:26:33 +0100
committerRuben Bridgewater <ruben@bridgewater.de>2019-03-14 17:15:31 +0100
commitb9cfaa3c65d5b59b8a6d2907ff9a34baeea0ec97 (patch)
treebe5d213f581bc3ac7b728015846328d17595276a
parent143dbb3db885d258ee4f5086e40871cde2fa78d7 (diff)
downloadnode-new-b9cfaa3c65d5b59b8a6d2907ff9a34baeea0ec97.tar.gz
doc: fix misleading sentence in http.md
Calling `response.end(data)` is not 100% equivalent to calling `response.write(data)` followed by `response.end()`. PR-URL: https://github.com/nodejs/node/pull/26465 Fixes: https://github.com/nodejs/node/issues/26005 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
-rw-r--r--doc/api/http.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/api/http.md b/doc/api/http.md
index a9441a44bb..ebc00fdf3a 100644
--- a/doc/api/http.md
+++ b/doc/api/http.md
@@ -1140,7 +1140,7 @@ This method signals to the server that all of the response headers and body
have been sent; that server should consider this message complete.
The method, `response.end()`, MUST be called on each response.
-If `data` is specified, it is equivalent to calling
+If `data` is specified, it is similar in effect to calling
[`response.write(data, encoding)`][] followed by `response.end(callback)`.
If `callback` is specified, it will be called when the response stream