Commit fa7d378
doc: correct it's vs. its usage
Fix a few instances where `it's` was being used where the possessive
`its` was called for. Some additional minor copy-editing of nearby text
(adding a comma and fixing a comma splice) was also performed.
PR-URL: #10098
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent 176f680 commit fa7d378
2 files changed
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -228,7 +228,7 @@ added: v0.1.94 | |||
| 228 | 228 | --> | |
| 229 | 229 | ||
| 230 | 230 | Updates the cipher with `data`. If the `input_encoding` argument is given, | |
| 231 | - it's value must be one of `'utf8'`, `'ascii'`, or `'latin1'` and the `data` | ||
| 231 | + its value must be one of `'utf8'`, `'ascii'`, or `'latin1'` and the `data` | ||
| 232 | 232 | argument is a string using the specified encoding. If the `input_encoding` | |
| 233 | 233 | argument is not given, `data` must be a [`Buffer`][]. If `data` is a | |
| 234 | 234 | [`Buffer`][] then `input_encoding` is ignored. | |
@@ -361,7 +361,7 @@ added: v0.1.94 | |||
| 361 | 361 | --> | |
| 362 | 362 | ||
| 363 | 363 | Updates the decipher with `data`. If the `input_encoding` argument is given, | |
| 364 | - it's value must be one of `'latin1'`, `'base64'`, or `'hex'` and the `data` | ||
| 364 | + its value must be one of `'latin1'`, `'base64'`, or `'hex'` and the `data` | ||
| 365 | 365 | argument is a string using the specified encoding. If the `input_encoding` | |
| 366 | 366 | argument is not given, `data` must be a [`Buffer`][]. If `data` is a | |
| 367 | 367 | [`Buffer`][] then `input_encoding` is ignored. | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -878,7 +878,7 @@ pending* that have not yet completed fully, *including* I/O operations to | |||
| 878 | 878 | `process.stdout` and `process.stderr`. | |
| 879 | 879 | ||
| 880 | 880 | In most situations, it is not actually necessary to call `process.exit()` | |
| 881 | - explicitly. The Node.js process will exit on it's own *if there is no additional | ||
| 881 | + explicitly. The Node.js process will exit on its own *if there is no additional | ||
| 882 | 882 | work pending* in the event loop. The `process.exitCode` property can be set to | |
| 883 | 883 | tell the process which exit code to use when the process exits gracefully. | |
| 884 | 884 | ||
@@ -1119,7 +1119,7 @@ added: v0.1.17 | |||
| 1119 | 1119 | The `process.mainModule` property provides an alternative way of retrieving | |
| 1120 | 1120 | [`require.main`][]. The difference is that if the main module changes at | |
| 1121 | 1121 | runtime, [`require.main`][] may still refer to the original main module in | |
| 1122 | - modules that were required before the change occurred. Generally it's | ||
| 1122 | + modules that were required before the change occurred. Generally, it's | ||
| 1123 | 1123 | safe to assume that the two refer to the same module. | |
| 1124 | 1124 | ||
| 1125 | 1125 | As with [`require.main`][], `process.mainModule` will be `undefined` if there | |
@@ -1163,7 +1163,7 @@ The `process.nextTick()` method adds the `callback` to the "next tick queue". | |||
| 1163 | 1163 | Once the current turn of the event loop turn runs to completion, all callbacks | |
| 1164 | 1164 | currently in the next tick queue will be called. | |
| 1165 | 1165 | ||
| 1166 | - This is *not* a simple alias to [`setTimeout(fn, 0)`][], it's much more | ||
| 1166 | + This is *not* a simple alias to [`setTimeout(fn, 0)`][]. It is much more | ||
| 1167 | 1167 | efficient. It runs before any additional I/O events (including | |
| 1168 | 1168 | timers) fire in subsequent ticks of the event loop. | |
| 1169 | 1169 | ||
0 commit comments