doc: debugger, dns, http: fix grammar

diff --git a/doc/api/debugger.markdown b/doc/api/debugger.markdown
index 63f2d49c8b3040f5e738f3af9a64456f6f73b006..2c68c1d49e5acb5fadb55da8ebe06594245e3d14 100644 (file)
--- a/doc/api/debugger.markdown
+++ b/doc/api/debugger.markdown
@@ -97,7 +97,7 @@ prints the active watchers. To remove a watcher, type
 * `next`, `n` - Step next
 * `step`, `s` - Step in
 * `out`, `o` - Step out
-* `pause` - Pause running code (like pause button in Developer TOols)
+* `pause` - Pause running code (like pause button in Developer Tools)
 
 ### Breakpoints
 

diff --git a/doc/api/dns.markdown b/doc/api/dns.markdown
index f6cec4cd038b7641f13045683e8f002b82afe69a..1ad6e6574c6ebc645a891177e804633e046f8527 100644 (file)
--- a/doc/api/dns.markdown
+++ b/doc/api/dns.markdown
@@ -7,7 +7,7 @@ use C-Ares except for `dns.lookup` which uses `getaddrinfo(3)` in a thread
 pool. C-Ares is much faster than `getaddrinfo` but the system resolver is
 more constant with how other programs operate. When a user does
 `net.connect(80, 'google.com')` or `http.get({ host: 'google.com' })` the
-`dns.lookup` method is used. Users who need to do a large number of look ups
+`dns.lookup` method is used. Users who need to do a large number of lookups
 quickly should use the methods that go through C-Ares.
 
 Here is an example which resolves `'www.google.com'` then reverse

diff --git a/doc/api/http.markdown b/doc/api/http.markdown
index c17c6b2ea28162f9543112370324457ece9f0d50..a6f0641d019d0e160940e3599cfb4c41e3d47e98 100644 (file)
--- a/doc/api/http.markdown
+++ b/doc/api/http.markdown
@@ -230,7 +230,7 @@ The response implements the [Writable Stream][] interface. This is an
 
 `function () { }`
 
-Indicates that the underlaying connection was terminated before
+Indicates that the underlying connection was terminated before
 `response.end()` was called or able to flush.
 
 ### response.writeContinue()