GeezerVison is showing github.com — doc: fix occurences of "the the" · nodejs/node@0acebb9
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/child_process.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -193,7 +193,7 @@ the process is spawned. The default options are: |
193 | 193 | } |
194 | 194 | ``` |
195 | 195 |
|
196 | | -If `timeout` is greater than `0`, the parent will send the the signal |
| 196 | +If `timeout` is greater than `0`, the parent will send the signal |
197 | 197 | identified by the `killSignal` property (the default is `'SIGTERM'`) if the |
198 | 198 | child runs longer than `timeout` milliseconds. |
199 | 199 |
|
|
Collapse file
Copy file name to clipboardExpand all lines: doc/api/stream.md +1-1Lines changed: 1 addition & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -471,7 +471,7 @@ If the data to be written can be generated or fetched on demand, it is |
471 | 471 | recommended to encapsulate the logic into a [Readable][] and use |
472 | 472 | [`stream.pipe()`][]. However, if calling `write()` is preferred, it is |
473 | 473 | possible to respect backpressure and avoid memory issues using the |
474 | | -the [`'drain'`][] event: |
| 474 | +[`'drain'`][] event: |
475 | 475 |
|
476 | 476 | ```js |
477 | 477 | function write (data, cb) { |
|
Collapse file
Copy file name to clipboardExpand all lines: src/cares_wrap.cc +2-2Lines changed: 2 additions & 2 deletions | Original file line number | Diff line number | Diff line change |
|---|
@@ -221,8 +221,8 @@ static void ares_sockstate_cb(void* data, |
221 | 221 | task = ares_task_create(env, sock); |
222 | 222 | if (task == nullptr) { |
223 | 223 | /* This should never happen unless we're out of memory or something */ |
224 | | - /* is seriously wrong. The socket won't be polled, but the the query */ |
225 | | - /* will eventually time out. */ |
| 224 | + /* is seriously wrong. The socket won't be polled, but the query will */ |
| 225 | + /* eventually time out. */ |
226 | 226 | return; |
227 | 227 | } |
228 | 228 |
|
|