Skip to content

Commit b79b82d

Browse files
davecardwelltargos
authored andcommitted
doc: update Buffer encoding option count
#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: #37102 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com> Reviewed-By: Harshitha K P <harshitha014@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent 0346043 commit b79b82d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/api/buffer.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ The character encodings currently supported by Node.js are the following:
9999
Converting a `Buffer` into a string using one of the above is referred to as
100100
decoding, and converting a string into a `Buffer` is referred to as encoding.
101101

102-
Node.js also supports the following two binary-to-text encodings. For
102+
Node.js also supports the following binary-to-text encodings. For
103103
binary-to-text encodings, the naming convention is reversed: Converting a
104104
`Buffer` into a string is typically referred to as encoding, and converting a
105105
string into a `Buffer` as decoding.

0 commit comments

Comments
 (0)