1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: fix run-on sentence in buffer.md

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/19567
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This commit is contained in:
Rich Trott 2018-03-23 15:02:35 -07:00
parent 400faf5a3a
commit ae120dbfd5
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/api/buffer.md
View File

@ -68,11 +68,10 @@ differently based on what arguments are provided:
* Passing an [`ArrayBuffer`] or a [`SharedArrayBuffer`] returns a `Buffer` that * Passing an [`ArrayBuffer`] or a [`SharedArrayBuffer`] returns a `Buffer` that
shares allocated memory with the given array buffer. shares allocated memory with the given array buffer.
Because the behavior of `new Buffer()` changes significantly based on the type Because the behavior of `new Buffer()` is different depending on the type of the
of value passed as the first argument, applications that do not properly first argument, security and reliability issues can be inadvertantly introduced
validate the input arguments passed to `new Buffer()`, or that fail to into applications when argument validation or `Buffer` initialization are not
appropriately initialize newly allocated `Buffer` content, can inadvertently performed.
introduce security and reliability issues into their code.
To make the creation of `Buffer` instances more reliable and less error prone, To make the creation of `Buffer` instances more reliable and less error prone,
the various forms of the `new Buffer()` constructor have been **deprecated** the various forms of the `new Buffer()` constructor have been **deprecated**