From 2ceecce725929239d9b4525ac0c812cfcd4350b8 Mon Sep 17 00:00:00 2001 From: Matthew Leon Date: Mon, 27 Nov 2017 15:33:36 -0500 Subject: [PATCH] doc: fix typo in stream.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/17357 Reviewed-By: Vse Mozhet Byt Reviewed-By: Jon Moss Reviewed-By: Tobias Nießen Reviewed-By: Colin Ihrig Reviewed-By: Gireesh Punathil --- doc/api/stream.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/stream.md b/doc/api/stream.md index ef47a93252f653..8a60eefdbf72f8 100644 --- a/doc/api/stream.md +++ b/doc/api/stream.md @@ -2213,7 +2213,7 @@ object mode has an interesting side effect. Because it *is* a call to However, because the argument is an empty string, no data is added to the readable buffer so there is nothing for a user to consume. -### `highWaterMark` discrepency after calling `readable.setEncoding()` +### `highWaterMark` discrepancy after calling `readable.setEncoding()` The use of `readable.setEncoding()` will change the behavior of how the `highWaterMark` operates in non-object mode. @@ -2264,7 +2264,7 @@ contain multi-byte characters. [fs write streams]: fs.html#fs_class_fs_writestream [http-incoming-message]: http.html#http_class_http_incomingmessage [zlib]: zlib.html -[hwm-gotcha]: #stream_highwatermark_discrepency_after_calling_readable_setencoding +[hwm-gotcha]: #stream_highwatermark_discrepancy_after_calling_readable_setencoding [stream-_flush]: #stream_transform_flush_callback [stream-_read]: #stream_readable_read_size_1 [stream-_transform]: #stream_transform_transform_chunk_encoding_callback