doc: fix several child_process doc typos

PR-URL: #31393 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anto Aravinth <[email protected]>
nodejs · Mar 17, 2020 · c7f03ad · c7f03ad
1 parent 8f88d62
commit c7f03ad
Showing 1 changed file with 4 additions and 4 deletions.
diff --git 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`