@@ -430,7 +430,7 @@ It is important to take note of the following:
|
430 | 430 | called asynchronously and therefore unable to correct the underlying problem. |
431 | 431 | |
432 | 432 | *Note*: Windows does not support sending signals, but Node.js offers some |
433 | | -emulation with [`process.kill()`][], and [`ChildProcess.kill()`][]. Sending |
| 433 | +emulation with [`process.kill()`][], and [`subprocess.kill()`][]. Sending |
434 | 434 | signal `0` can be used to test for the existence of a process. Sending `SIGINT`, |
435 | 435 | `SIGTERM`, and `SIGKILL` cause the unconditional termination of the target |
436 | 436 | process. |
@@ -1779,9 +1779,9 @@ cases:
|
1779 | 1779 | [`'message'`]: child_process.html#child_process_event_message |
1780 | 1780 | [`'rejectionHandled'`]: #process_event_rejectionhandled |
1781 | 1781 | [`'uncaughtException'`]: #process_event_uncaughtexception |
1782 | | -[`ChildProcess.disconnect()`]: child_process.html#child_process_child_disconnect |
1783 | | -[`ChildProcess.kill()`]: child_process.html#child_process_child_kill_signal |
1784 | | -[`ChildProcess.send()`]: child_process.html#child_process_child_send_message_sendhandle_options_callback |
| 1782 | +[`ChildProcess.disconnect()`]: child_process.html#child_process_subprocess_disconnect |
| 1783 | +[`subprocess.kill()`]: child_process.html#child_process_subprocess_kill_signal |
| 1784 | +[`ChildProcess.send()`]: child_process.html#child_process_subprocess_send_message_sendhandle_options_callback |
1785 | 1785 | [`ChildProcess`]: child_process.html#child_process_class_childprocess |
1786 | 1786 | [`end()`]: stream.html#stream_writable_end_chunk_encoding_callback |
1787 | 1787 | [`Error`]: errors.html#errors_class_error |
|