doc: remove confusing note about child process stdio

It’s not obvious what the paragraph is supposed to say.
In particular, whether and what kind of buffering mechanism
a process uses for its stdio streams does not affect that,
in general, no guarantees can be made about when it consumes data
that was sent to it.

PR-URL: https://github.com/nodejs/node/pull/19552
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

1 files changed, 0 insertions, 4 deletions

diff --git a/doc/api/child_process.md b/doc/api/child_process.md
index cf0ba5a75b..4873d4681a 100755
--- a/doc/api/child_process.md
+++ b/doc/api/child_process.md
@@ -32,10 +32,6 @@ stdout in excess of that limit without the output being captured, the child
 process will block waiting for the pipe buffer to accept more data. This is
 identical to the behavior of pipes in the shell. Use the `{ stdio: 'ignore' }`
 option if the output will not be consumed.
-It is possible to stream data through these pipes in a non-blocking way. Note,
-however, that some programs use line-buffered I/O internally. While that does
-not affect Node.js, it can mean that data sent to the child process may not be
-immediately consumed.
 
 The [`child_process.spawn()`][] method spawns the child process asynchronously,
 without blocking the Node.js event loop. The [`child_process.spawnSync()`][]