diff --git a/doc/api/child_processes.markdown b/doc/api/child_processes.markdown
index e3262117af3c..eec9f4f0024e 100644
--- a/doc/api/child_processes.markdown
+++ b/doc/api/child_processes.markdown
@@ -229,8 +229,9 @@ And then the child script, `'sub.js'` might look like this:
 In the child the `process` object will have a `send()` method, and `process`
 will emit objects each time it receives a message on its channel.
 
-By default the spawned Node process will have the stdin, stdout, stderr
-associated with the parent's.
+By default the spawned Node process will have the stdout, stderr associated
+with the parent's. To change this behavior set the `silent` property in the
+`options` object to `true`.
 
 These child Nodes are still whole new instances of V8. Assume at least 30ms
 startup and 10mb memory for each new Node. That is, you cannot create many
diff --git a/doc/api/cluster.markdown b/doc/api/cluster.markdown
index b3559f3dbee8..be42571a0e4b 100644
--- a/doc/api/cluster.markdown
+++ b/doc/api/cluster.markdown
@@ -188,17 +188,17 @@ Example:
     cluster.setupMaster({
         exec : "worker.js",
         args : ["--use", "https"],
-        workers : 2
+        workers : 2,
+        silent : true
     });
     cluster.autoFork();
 
 The options argument can contain 3 different properties.
 
-`exec` and `args` are used when forking a new worker.
-
 - `exec` are the file path to the worker file, by default this is the same file as the master.
 - `args` are a array of arguments send along with the worker, by default this is `process.argv.slice(2)`.
 - `workers` are the number of worker there will be created when using `autoFork()`
+- `silent`, if this option is true the output of a worker won't propagate to the master, by default this is false.
 
 ## Worker