OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2026-01-15 12:15:26 +00:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

doc: fix typos in buffer doc

Browse Source 
* pluralize "strings" in hex encoding description.
* fix typo in ascii encoding description
* remove double "array"

PR-URL: https://github.com/nodejs/node/pull/34981
Reviewed-By: Derek Lewis <DerekNonGeneric@inf.is>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
This commit is contained in:
Robert Williams
2020-08-29 20:46:23 -05:00
committed by Rich Trott
parent 492c34fa4b
commit 59cad32b51
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/api/buffer.md
View File

@@ -107,14 +107,14 @@ string into a `Buffer` as decoding.
tabs, and new lines contained within the base64-encoded string are ignored.
* `'hex'`: Encode each byte as two hexadecimal characters. Data truncation
may occur when decoding string that do exclusively contain valid hexadecimal
may occur when decoding strings that do exclusively contain valid hexadecimal
characters. See below for an example.
The following legacy character encodings are also supported:
* `'ascii'`: For 7-bit [ASCII][] data only. When encoding a string into a
`Buffer`, this is equivalent to using `'latin1'`. When decoding a `Buffer`
into a string, using encoding this will additionally unset the highest bit of
into a string, using this encoding will additionally unset the highest bit of
each byte before decoding as `'latin1'`.
Generally, there should be no reason to use this encoding, as `'utf8'`
(or, if the data is known to always be ASCII-only, `'latin1'`) will be a
@@ -176,7 +176,7 @@ In particular:
There are two ways to create new [`TypedArray`][] instances from a `Buffer`:
* Passing a `Buffer` to a [`TypedArray`][] constructor will copy the `Buffer`s
contents, interpreted an array array of integers, and not as a byte sequence
contents, interpreted as an array of integers, and not as a byte sequence
of the target type.
```js