From 8a254058f581b868309585bd6aafbf4fc6b6f1cc Mon Sep 17 00:00:00 2001 From: cjihrig Date: Thu, 4 Feb 2021 12:07:27 -0500 Subject: [PATCH] doc: fix accommodate typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/37229 Reviewed-By: Antoine du Hamel Reviewed-By: Richard Lau Reviewed-By: Michael Dawson Reviewed-By: Juan José Arboleda Reviewed-By: Pooja D P Reviewed-By: Trivikram Kamat Reviewed-By: Darshan Sen --- doc/api/cli.md | 2 +- doc/changelogs/CHANGELOG_V15.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/cli.md b/doc/api/cli.md index 044e8caf5882a2..70cb69cd54a451 100644 --- a/doc/api/cli.md +++ b/doc/api/cli.md @@ -355,7 +355,7 @@ Node.js instance runs out of memory when `max_count` is greater than `0`. Generating V8 snapshots takes time and memory (both memory managed by the V8 heap and native memory outside the V8 heap). The bigger the heap is, -the more resources it needs. Node.js will adjust the V8 heap to accommondate +the more resources it needs. Node.js will adjust the V8 heap to accommodate the additional V8 heap memory overhead, and try its best to avoid using up all the memory available to the process. When the process uses more memory than the system deems appropriate, the process may be terminated diff --git a/doc/changelogs/CHANGELOG_V15.md b/doc/changelogs/CHANGELOG_V15.md index f8bd62ce317045..5ddb5d7544a3b5 100644 --- a/doc/changelogs/CHANGELOG_V15.md +++ b/doc/changelogs/CHANGELOG_V15.md @@ -1097,7 +1097,7 @@ With the new `--heapsnapshot-near-heap-limit=max_count` experimental command lin When generating snapshots, garbage collection may be triggered and bring the heap usage down, therefore multiple snapshots may be written to disk before the Node.js instance finally runs out of memory. These heap snapshots can be compared to determine what objects are being allocated during the time consecutive snapshots are taken. -Generating V8 snapshots takes time and memory (both memory managed by the V8 heap and native memory outside the V8 heap). The bigger the heap is, the more resources it needs. Node.js will adjust the V8 heap to accommondate the additional V8 heap memory overhead, and try its best to avoid using up all the memory avialable to the process. +Generating V8 snapshots takes time and memory (both memory managed by the V8 heap and native memory outside the V8 heap). The bigger the heap is, the more resources it needs. Node.js will adjust the V8 heap to accommodate the additional V8 heap memory overhead, and try its best to avoid using up all the memory avialable to the process. ```console $ node --max-old-space-size=100 --heapsnapshot-near-heap-limit=3 index.js