doc: for style, remove "isn't" contraction

PR-URL: #10981
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>

doc/api/console.md

@@ -79,7 +79,7 @@ const Console = console.Console;
 
 Creates a new `Console` by passing one or two writable stream instances.
 `stdout` is a writable stream to print log or info output. `stderr`
-is used for warning or error output. If `stderr` isn't passed, warning and error
+is used for warning or error output. If `stderr` is not passed, warning and error
 output will be sent to `stdout`.
 
 ```js

doc/api/debugger.md

@@ -117,7 +117,7 @@ script.js
 on line 1
 
 It is also possible to set a breakpoint in a file (module) that
-isn't loaded yet:
+is not loaded yet:
 
 ```txt
 $ node debug test/fixtures/break-in-module/main.js

doc/api/domain.md

@@ -153,7 +153,7 @@ if (cluster.isMaster) {
   server.listen(PORT);
 }
 
-// This part isn't important.  Just an example routing thing.
+// This part is not important.  Just an example routing thing.
 // You'd put your fancy application logic here.
 function handleRequest(req, res) {
   switch(req.url) {

doc/api/globals.md

@@ -32,7 +32,7 @@ added: v0.1.27
 The directory name of the current module. This the same as the
 [`path.dirname()`][] of the [`__filename`][].
 
-`__dirname` isn't actually a global but rather local to each module.
+`__dirname` is not actually a global but rather local to each module.
 
 Example: running `node example.js` from `/Users/mjr`
 
@@ -60,7 +60,7 @@ command line.
 
 See [`__dirname`][] for the directory name of the current module.
 
-`__filename` isn't actually a global but rather local to each module.
+`__filename` is not actually a global but rather local to each module.
 
 Examples:
 
@@ -132,7 +132,7 @@ A reference to the `module.exports` that is shorter to type.
 See [module system documentation][] for details on when to use `exports` and
 when to use `module.exports`.
 
-`exports` isn't actually a global but rather local to each module.
+`exports` is not actually a global but rather local to each module.
 
 See the [module system documentation][] for more information.
 
@@ -163,7 +163,7 @@ A reference to the current module. In particular
 `module.exports` is used for defining what a module exports and makes
 available through `require()`.
 
-`module` isn't actually a global but rather local to each module.
+`module` is not actually a global but rather local to each module.
 
 See the [module system documentation][] for more information.
 
@@ -187,7 +187,7 @@ added: v0.1.13
 
 * {Function}
 
-To require modules. See the [Modules][] section.  `require` isn't actually a
+To require modules. See the [Modules][] section.  `require` is not actually a
 global but rather local to each module.
 
 ### require.cache

doc/api/http.md

@@ -298,7 +298,7 @@ added: v0.7.0
 * `head` {Buffer}
 
 Emitted each time a server responds to a request with a `CONNECT` method. If this
-event isn't being listened for, clients receiving a `CONNECT` method will have
+event is not being listened for, clients receiving a `CONNECT` method will have
 their connections closed.
 
 A client and server pair that shows you how to listen for the `'connect'` event:
@@ -396,7 +396,7 @@ added: v0.1.94
 * `head` {Buffer}
 
 Emitted each time a server responds to a request with an upgrade. If this
-event isn't being listened for, clients receiving an upgrade header will have
+event is not being listened for, clients receiving an upgrade header will have
 their connections closed.
 
 A client server pair that show you how to listen for the `'upgrade'` event.
@@ -481,7 +481,7 @@ call `request.end()` or write the first chunk of request data.  It then tries
 hard to pack the request headers and data into a single TCP packet.
 
 That's usually what you want (it saves a TCP round-trip) but not when the first
-data isn't sent until possibly much later.  `request.flushHeaders()` lets you bypass
+data is not sent until possibly much later.  `request.flushHeaders()` lets you bypass
 the optimization and kickstart the request.
 
 ### request.setNoDelay([noDelay])
@@ -557,7 +557,7 @@ added: v0.3.0
 * `response` {http.ServerResponse}
 
 Emitted each time a request with an HTTP `Expect: 100-continue` is received.
-If this event isn't listened for, the server will automatically respond
+If this event is not listened for, the server will automatically respond
 with a `100 Continue` as appropriate.
 
 Handling this event involves calling [`response.writeContinue()`][] if the client
@@ -577,7 +577,7 @@ added: v5.5.0
 * `response` {http.ServerResponse}
 
 Emitted each time a request with an HTTP `Expect` header is received, where the
-value is not `100-continue`. If this event isn't listened for, the server will
+value is not `100-continue`. If this event is not listened for, the server will
 automatically respond with a `417 Expectation Failed` as appropriate.
 
 Note that when this event is emitted and handled, the [`'request'`][] event will
@@ -634,8 +634,8 @@ added: v0.7.0
 * `socket` {net.Socket} Network socket between the server and client
 * `head` {Buffer} The first packet of the tunneling stream (may be empty)
 
-Emitted each time a client requests an HTTP `CONNECT` method. If this event isn't
-listened for, then clients requesting a `CONNECT` method will have their
+Emitted each time a client requests an HTTP `CONNECT` method. If this event is
+not listened for, then clients requesting a `CONNECT` method will have their
 connections closed.
 
 After this event is emitted, the request's socket will not have a `'data'`
@@ -676,7 +676,7 @@ added: v0.1.94
 * `socket` {net.Socket} Network socket between the server and client
 * `head` {Buffer} The first packet of the upgraded stream (may be empty)
 
-Emitted each time a client requests an HTTP upgrade. If this event isn't
+Emitted each time a client requests an HTTP upgrade. If this event is not
 listened for, then clients requesting an upgrade will have their connections
 closed.
 

doc/api/modules.md

@@ -463,7 +463,7 @@ added: v0.1.16
 
 In each module, the `module` free variable is a reference to the object
 representing the current module.  For convenience, `module.exports` is
-also accessible via the `exports` module-global. `module` isn't actually
+also accessible via the `exports` module-global. `module` is not actually
 a global but rather local to each module.
 
 ### module.children