From 6f5ba92e61de87dbc3b0b52e90f6b711fd91c9f2 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 11 May 2023 16:09:17 -0700 Subject: [PATCH] doc: remove broken link MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Closes: https://github.com/nodejs/node/issues/47940 PR-URL: https://github.com/nodejs/node/pull/47942 Fixes: https://github.com/nodejs/node/issues/47940 Reviewed-By: Tobias Nießen Reviewed-By: James M Snell Reviewed-By: Luigi Pinca --- doc/api/buffer.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/api/buffer.md b/doc/api/buffer.md index 2faf00cf74bb41..d457df43775874 100644 --- a/doc/api/buffer.md +++ b/doc/api/buffer.md @@ -189,8 +189,8 @@ The following legacy character encodings are also supported: better choice when encoding or decoding ASCII-only text. It is only provided for legacy compatibility. -* `'binary'`: Alias for `'latin1'`. See [binary strings][] for more background - on this topic. The name of this encoding can be very misleading, as all of the +* `'binary'`: Alias for `'latin1'`. + The name of this encoding can be very misleading, as all of the encodings listed here convert between strings and binary data. For converting between strings and `Buffer`s, typically `'utf8'` is the right choice. @@ -5526,6 +5526,5 @@ introducing security vulnerabilities into an application. [`util.inspect()`]: util.md#utilinspectobject-options [`v8::TypedArray::kMaxLength`]: https://v8.github.io/api/head/classv8_1_1TypedArray.html#a54a48f4373da0850663c4393d843b9b0 [base64url]: https://tools.ietf.org/html/rfc4648#section-5 -[binary strings]: https://developer.mozilla.org/en-US/docs/Web/API/DOMString/Binary [endianness]: https://en.wikipedia.org/wiki/Endianness [iterator]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols