From b0c9b1fdfb268e8396fd6cc1fa2cc51582cad51b Mon Sep 17 00:00:00 2001 From: Dave Cardwell Date: Wed, 27 Jan 2021 08:40:45 -0500 Subject: [PATCH] doc: update Buffer encoding option count MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/nodejs/node/pull/36952 added the `base64url` encoding option. Easier to just remove the count of options so it doesn’t need to be updated to four, five, etc. in the future. PR-URL: https://github.com/nodejs/node/pull/37102 Reviewed-By: Darshan Sen Reviewed-By: Filip Skokan Reviewed-By: Antoine du Hamel Reviewed-By: James M Snell Reviewed-By: Zijian Liu Reviewed-By: Juan José Arboleda Reviewed-By: Harshitha K P Reviewed-By: Luigi Pinca --- doc/api/buffer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/buffer.md b/doc/api/buffer.md index d54e8e3ab8dacd..154f05ae3a39ef 100644 --- a/doc/api/buffer.md +++ b/doc/api/buffer.md @@ -96,7 +96,7 @@ The character encodings currently supported by Node.js are the following: Converting a `Buffer` into a string using one of the above is referred to as decoding, and converting a string into a `Buffer` is referred to as encoding. -Node.js also supports the following two binary-to-text encodings. For +Node.js also supports the following binary-to-text encodings. For binary-to-text encodings, the naming convention is reversed: Converting a `Buffer` into a string is typically referred to as encoding, and converting a string into a `Buffer` as decoding.