Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: do not use tilde for "about" or "approximately" #39344

Merged
merged 1 commit into from
Jul 12, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions doc/api/buffer.md
Original file line number Diff line number Diff line change
Expand Up @@ -5031,9 +5031,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.

Expand Down
4 changes: 2 additions & 2 deletions doc/guides/investigating_native_memory_leak.md
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down