Commit b0c9b1f
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 2e5994d commit b0c9b1f
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -96,7 +96,7 @@ The character encodings currently supported by Node.js are the following: | |||
| 96 | 96 | Converting a `Buffer` into a string using one of the above is referred to as | |
| 97 | 97 | decoding, and converting a string into a `Buffer` is referred to as encoding. | |
| 98 | 98 | ||
| 99 | - Node.js also supports the following two binary-to-text encodings. For | ||
| 99 | + Node.js also supports the following binary-to-text encodings. For | ||
| 100 | 100 | binary-to-text encodings, the naming convention is reversed: Converting a | |
| 101 | 101 | `Buffer` into a string is typically referred to as encoding, and converting a | |
| 102 | 102 | string into a `Buffer` as decoding. | |
0 commit comments