From 0b3b2695bc28ef4ca65649b7750da64211de01b6 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sat, 10 Jul 2021 11:50:40 -0700 Subject: [PATCH] doc: do not use tilde for "about" or "approximately" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Refs: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/special-characters PR-URL: https://github.com/nodejs/node/pull/39344 Reviewed-By: Luigi Pinca Reviewed-By: James M Snell Reviewed-By: Tobias Nießen Reviewed-By: Darshan Sen --- doc/api/buffer.md | 5 +++-- doc/guides/investigating_native_memory_leak.md | 4 ++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/api/buffer.md b/doc/api/buffer.md index b9a83959ccab83..a8a7635dbdc748 100644 --- a/doc/api/buffer.md +++ b/doc/api/buffer.md @@ -5027,9 +5027,10 @@ changes: * {integer} The largest size allowed for a single `Buffer` instance. -On 32-bit architectures, this value currently is 230 - 1 (~1 GB). +On 32-bit architectures, this value currently is 230 - 1 (about 1 +GB). -On 64-bit architectures, this value currently is 232 (~4 GB). +On 64-bit architectures, this value currently is 232 (about 4 GB). It reflects [`v8::TypedArray::kMaxLength`][] under the hood. diff --git a/doc/guides/investigating_native_memory_leak.md b/doc/guides/investigating_native_memory_leak.md index 3c5664a77812c1..f808675f5328bc 100644 --- a/doc/guides/investigating_native_memory_leak.md +++ b/doc/guides/investigating_native_memory_leak.md @@ -100,8 +100,8 @@ Leaks can be introduced in native addons and the following is a simple example leak based on the "Hello world" addon from [node-addon-examples](https://github.com/nodejs/node-addon-examples). -In this example, a loop which allocates ~1 MB of memory and never frees it -has been added: +In this example, a loop which allocates approximately 1 MB of memory and never +frees it has been added: ```cpp void* malloc_holder = nullptr;