| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent df76c89 commit 514a538
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -107,14 +107,14 @@ string into a `Buffer` as decoding. | |||
| 107 | 107 | tabs, and new lines contained within the base64-encoded string are ignored. | |
| 108 | 108 | ||
| 109 | 109 | * `'hex'`: Encode each byte as two hexadecimal characters. Data truncation | |
| 110 | - may occur when decoding string that do exclusively contain valid hexadecimal | ||
| 110 | + may occur when decoding strings that do exclusively contain valid hexadecimal | ||
| 111 | 111 | characters. See below for an example. | |
| 112 | 112 | ||
| 113 | 113 | The following legacy character encodings are also supported: | |
| 114 | 114 | ||
| 115 | 115 | * `'ascii'`: For 7-bit [ASCII][] data only. When encoding a string into a | |
| 116 | 116 | `Buffer`, this is equivalent to using `'latin1'`. When decoding a `Buffer` | |
| 117 | - into a string, using encoding this will additionally unset the highest bit of | ||
| 117 | + into a string, using this encoding will additionally unset the highest bit of | ||
| 118 | 118 | each byte before decoding as `'latin1'`. | |
| 119 | 119 | Generally, there should be no reason to use this encoding, as `'utf8'` | |
| 120 | 120 | (or, if the data is known to always be ASCII-only, `'latin1'`) will be a | |
@@ -176,7 +176,7 @@ In particular: | |||
| 176 | 176 | There are two ways to create new [`TypedArray`][] instances from a `Buffer`: | |
| 177 | 177 | ||
| 178 | 178 | * Passing a `Buffer` to a [`TypedArray`][] constructor will copy the `Buffer`s | |
| 179 | - contents, interpreted an array array of integers, and not as a byte sequence | ||
| 179 | + contents, interpreted as an array of integers, and not as a byte sequence | ||
| 180 | 180 | of the target type. | |
| 181 | 181 | ||
| 182 | 182 | ```js | |
| Back | FazBrowse Home | New Git URL |
0 commit comments