Skip to content
This repository was archived by the owner on Apr 22, 2023. It is now read-only.

Commit a08271c

Browse files
Robin Leebnoordhuis
Robin Lee
authored andcommitted
doc: fix three typos
1 parent 96ca59f commit a08271c

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

doc/api/child_process.markdown

+1-1
Original file line numberDiff line numberDiff line change
@@ -221,7 +221,7 @@ The `child.js` could look like this:
221221

222222
process.on('message', function(m, socket) {
223223
if (m === 'socket') {
224-
socket.end('You where handled as a ' + process.argv[2] + ' person');
224+
socket.end('You were handled as a ' + process.argv[2] + ' person');
225225
}
226226
});
227227

doc/api/cluster.markdown

+1-1
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ This causes potentially surprising behavior in three edge cases:
6969
the worker to use the supplied handle, rather than talk to the master
7070
process. If the worker already has the handle, then it's presumed
7171
that you know what you are doing.
72-
3. `server.listen(0)` Normally, this will case servers to listen on a
72+
3. `server.listen(0)` Normally, this will cause servers to listen on a
7373
random port. However, in a cluster, each worker will receive the
7474
same "random" port each time they do `listen(0)`. In essence, the
7575
port is random the first time, but predictable thereafter. If you

doc/api/net.markdown

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ packet when the other end of the socket sends a FIN packet. The socket becomes
2121
non-readable, but still writable. You should call the `end()` method explicitly.
2222
See ['end'][] event for more information.
2323

24-
Here is an example of a echo server which listens for connections
24+
Here is an example of an echo server which listens for connections
2525
on port 8124:
2626

2727
var net = require('net');

0 commit comments

Comments
 (0)