From b809a8c68d85bd26666363d8b7f28e34ec647e13 Mon Sep 17 00:00:00 2001 From: cjihrig <cjihrig@gmail.com> Date: Thu, 16 Jan 2020 20:14:18 -0500 Subject: [PATCH] doc: fix several child_process doc typos PR-URL: https://github.com/nodejs/node/pull/31393 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com> --- doc/api/child_process.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/api/child_process.md b/doc/api/child_process.md index 8e2b9a45a19aee..cd47fec7982b3e 100644 --- a/doc/api/child_process.md +++ b/doc/api/child_process.md @@ -983,7 +983,7 @@ added: v0.1.90 The `'exit'` event is emitted after the child process ends. If the process exited, `code` is the final exit code of the process, otherwise `null`. If the process terminated due to receipt of a signal, `signal` is the string name of -the signal, otherwise `null`. One of the two will always be non-null. +the signal, otherwise `null`. One of the two will always be non-`null`. When the `'exit'` event is triggered, child process stdio streams might still be open. @@ -1059,8 +1059,8 @@ within the child process to close the IPC channel as well. * {integer} -The `subprocess.exitcode` property indicates the exit code of the child process. -If the child process is still running, the field will be null. +The `subprocess.exitCode` property indicates the exit code of the child process. +If the child process is still running, the field will be `null`. ### `subprocess.kill([signal])` <!-- YAML @@ -1360,7 +1360,7 @@ time it takes to send the connection to the child. * {integer} The `subprocess.signalCode` property indicates the signal number received by -the child process if any, else null. +the child process if any, else `null`. ### `subprocess.spawnargs`