Skip to content

Commit 3dabb44

Browse files
daeyeonRafaelGSS
authored andcommitted
doc: use serial comma in report docs
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>
1 parent b9cfb71 commit 3dabb44

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/api/report.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010

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

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

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

0 commit comments

Comments
 (0)