doc: fix occurences of "the the"

I identified a number of files where it said "the the" in the comments
of the source code and in general documentation texts. I replaced
these occurences with a single instance of "the".

PR-URL: https://github.com/nodejs/node/pull/11711
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
This commit is contained in:
Jeroen Mandersloot 2017-03-06 11:32:45 +01:00 коммит произвёл Franziska Hinkelmann
Родитель 28584dbf29
Коммит 0c10ec9183
4 изменённых файлов: 5 добавлений и 5 удалений

Просмотреть файл

@ -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.

Просмотреть файл

@ -480,7 +480,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) {

Просмотреть файл

@ -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;
}

Просмотреть файл

@ -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' });
}