doc: fixed occurences of "the the"

doc/api/child_process.md

@@ -193,7 +193,7 @@ the process is spawned. The default options are:
 }
 ```
 
-If `timeout` is greater than `0`, the parent will send the the signal
+If `timeout` is greater than `0`, the parent will send the signal
 identified by the `killSignal` property (the default is `'SIGTERM'`) if the
 child runs longer than `timeout` milliseconds.
 

doc/api/stream.md

@@ -471,7 +471,7 @@ If the data to be written can be generated or fetched on demand, it is
 recommended to encapsulate the logic into a [Readable][] and use
 [`stream.pipe()`][]. However, if calling `write()` is preferred, it is
 possible to respect backpressure and avoid memory issues using the
-the [`'drain'`][] event:
+[`'drain'`][] event:
 
 ```js
 function write (data, cb) {

src/cares_wrap.cc

@@ -220,8 +220,8 @@ static void ares_sockstate_cb(void* data,
       task = ares_task_create(env, sock);
       if (task == nullptr) {
         /* This should never happen unless we're out of memory or something */
-        /* is seriously wrong. The socket won't be polled, but the the query */
-        /* will eventually time out. */
+        /* is seriously wrong. The socket won't be polled, but the query will */
+        /* eventually time out. */
         return;
       }
 

test/parallel/test-env-var-no-warnings.js

@@ -36,6 +36,6 @@ if (process.argv[2] === 'child') {
   test({ NODE_NO_WARNINGS: '01' });
   test({ NODE_NO_WARNINGS: '2' });
   // Don't test the number 1 because it will come through as a string in the
-  // the child process environment.
+  // child process environment.
   test({ NODE_NO_WARNINGS: '1' });
 }