Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: fix several child_process doc typos #31393

Merged
merged 1 commit into from
Jan 19, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/api/child_process.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -1079,8 +1079,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
Expand Down Expand Up @@ -1380,7 +1380,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`

Expand Down