Skip to content

Commit

Permalink
doc: use serial comma in report docs
Browse files Browse the repository at this point in the history
Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
PR-URL: #44608
Reviewed-By: theanarkh <theratliter@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
  • Loading branch information
daeyeon authored and juanarbol committed Oct 4, 2022
1 parent d3fc0f5 commit 60d9210
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/api/report.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@

Delivers a JSON-formatted diagnostic summary, written to a file.

The report is intended for development, test and production use, to capture
The report is intended for development, test, and production use, to capture
and preserve information for problem determination. It includes JavaScript
and native stack traces, heap statistics, platform information, resource
usage etc. With the report option enabled, diagnostic reports can be triggered
Expand Down Expand Up @@ -508,9 +508,9 @@ the application, in expectation of self-adjusting the resource consumption,
load balancing, monitoring etc.

The content of the report consists of a header section containing the event
type, date, time, PID and Node.js version, sections containing JavaScript and
type, date, time, PID, and Node.js version, sections containing JavaScript and
native stack traces, a section containing V8 heap information, a section
containing `libuv` handle information and an OS platform information section
containing `libuv` handle information, and an OS platform information section
showing CPU and memory usage and system limits. An example report can be
triggered using the Node.js REPL:

Expand Down

0 comments on commit 60d9210

Please sign in to comment.