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 2<sup>30</sup> - 1 (~1 GB). +On 32-bit architectures, this value currently is 2<sup>30</sup> - 1 (about 1 +GB). -On 64-bit architectures, this value currently is 2<sup>32</sup> (~4 GB). +On 64-bit architectures, this value currently is 2<sup>32</sup> (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;