From a08271c7a8e0a07034c61028b69db993c0f61145 Mon Sep 17 00:00:00 2001
From: Robin Lee <cheeselee@fedoraproject.org>
Date: Sun, 2 Sep 2012 15:36:21 +0800
Subject: [PATCH] doc: fix three typos

---
 doc/api/child_process.markdown | 2 +-
 doc/api/cluster.markdown       | 2 +-
 doc/api/net.markdown           | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown
index 092cb31e29..d4616e63c2 100644
--- a/doc/api/child_process.markdown
+++ b/doc/api/child_process.markdown
@@ -221,7 +221,7 @@ The `child.js` could look like this:
 
     process.on('message', function(m, socket) {
       if (m === 'socket') {
-        socket.end('You where handled as a ' + process.argv[2] + ' person');
+        socket.end('You were handled as a ' + process.argv[2] + ' person');
       }
     });
 
diff --git a/doc/api/cluster.markdown b/doc/api/cluster.markdown
index 032e38138e..79aa79044f 100644
--- a/doc/api/cluster.markdown
+++ b/doc/api/cluster.markdown
@@ -69,7 +69,7 @@ This causes potentially surprising behavior in three edge cases:
    the worker to use the supplied handle, rather than talk to the master
    process.  If the worker already has the handle, then it's presumed
    that you know what you are doing.
-3. `server.listen(0)` Normally, this will case servers to listen on a
+3. `server.listen(0)` Normally, this will cause servers to listen on a
    random port.  However, in a cluster, each worker will receive the
    same "random" port each time they do `listen(0)`.  In essence, the
    port is random the first time, but predictable thereafter.  If you
diff --git a/doc/api/net.markdown b/doc/api/net.markdown
index 6d4e2382ae..c9b45bd488 100644
--- a/doc/api/net.markdown
+++ b/doc/api/net.markdown
@@ -21,7 +21,7 @@ packet when the other end of the socket sends a FIN packet. The socket becomes
 non-readable, but still writable. You should call the `end()` method explicitly.
 See ['end'][] event for more information.
 
-Here is an example of a echo server which listens for connections
+Here is an example of an echo server which listens for connections
 on port 8124:
 
     var net = require('net');