Commit 9d1b7ac
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -384,7 +384,7 @@ an [`fs.Dirent`][], or `null` if there are no more directory entries to read. | |||
| 384 | 384 | ||
| 385 | 385 | Directory entries returned by this function are in no particular order as | |
| 386 | 386 | provided by the operating system's underlying directory mechanisms. | |
| 387 | - Entries added or removed while iterating over the directory may or may not be | ||
| 387 | + Entries added or removed while iterating over the directory might not be | ||
| 388 | 388 | included in the iteration results. | |
| 389 | 389 | ||
| 390 | 390 | ### `dir.read(callback)` | |
@@ -404,7 +404,7 @@ After the read is completed, the `callback` will be called with an | |||
| 404 | 404 | ||
| 405 | 405 | Directory entries returned by this function are in no particular order as | |
| 406 | 406 | provided by the operating system's underlying directory mechanisms. | |
| 407 | - Entries added or removed while iterating over the directory may or may not be | ||
| 407 | + Entries added or removed while iterating over the directory might not be | ||
| 408 | 408 | included in the iteration results. | |
| 409 | 409 | ||
| 410 | 410 | ### `dir.readSync()` | |
@@ -421,7 +421,7 @@ If there are no more directory entries to read, `null` will be returned. | |||
| 421 | 421 | ||
| 422 | 422 | Directory entries returned by this function are in no particular order as | |
| 423 | 423 | provided by the operating system's underlying directory mechanisms. | |
| 424 | - Entries added or removed while iterating over the directory may or may not be | ||
| 424 | + Entries added or removed while iterating over the directory might not be | ||
| 425 | 425 | included in the iteration results. | |
| 426 | 426 | ||
| 427 | 427 | ### `dir[Symbol.asyncIterator]()` | |
@@ -441,7 +441,7 @@ See [`fs.Dir`][] for an example. | |||
| 441 | 441 | ||
| 442 | 442 | Directory entries returned by this iterator are in no particular order as | |
| 443 | 443 | provided by the operating system's underlying directory mechanisms. | |
| 444 | - Entries added or removed while iterating over the directory may or may not be | ||
| 444 | + Entries added or removed while iterating over the directory might not be | ||
| 445 | 445 | included in the iteration results. | |
| 446 | 446 | ||
| 447 | 447 | ## Class: `fs.Dirent` | |
@@ -3508,7 +3508,7 @@ changes: | |||
| 3508 | 3508 | * `path` {string|Buffer|URL} | |
| 3509 | 3509 | * `options` {Object} | |
| 3510 | 3510 | * `maxRetries` {integer} If an `EBUSY`, `EMFILE`, `ENFILE`, `ENOTEMPTY`, or | |
| 3511 | - `EPERM` error is encountered, Node.js will retry the operation with a linear | ||
| 3511 | + `EPERM` error is encountered, Node.js retries the operation with a linear | ||
| 3512 | 3512 | backoff wait of `retryDelay` milliseconds longer on each try. This option | |
| 3513 | 3513 | represents the number of retries. This option is ignored if the `recursive` | |
| 3514 | 3514 | option is not `true`. **Default:** `0`. | |
@@ -3559,7 +3559,7 @@ changes: | |||
| 3559 | 3559 | * `path` {string|Buffer|URL} | |
| 3560 | 3560 | * `options` {Object} | |
| 3561 | 3561 | * `maxRetries` {integer} If an `EBUSY`, `EMFILE`, `ENFILE`, `ENOTEMPTY`, or | |
| 3562 | - `EPERM` error is encountered, Node.js will retry the operation with a linear | ||
| 3562 | + `EPERM` error is encountered, Node.js retries the operation with a linear | ||
| 3563 | 3563 | backoff wait of `retryDelay` milliseconds longer on each try. This option | |
| 3564 | 3564 | represents the number of retries. This option is ignored if the `recursive` | |
| 3565 | 3565 | option is not `true`. **Default:** `0`. | |
@@ -4411,8 +4411,8 @@ fs.write(fd, Buffer.from(data, options.encoding), callback); | |||
| 4411 | 4411 | ``` | |
| 4412 | 4412 | ||
| 4413 | 4413 | The difference from directly calling `fs.write()` is that under some unusual | |
| 4414 | - conditions, `fs.write()` may write only part of the buffer and will need to be | ||
| 4415 | - retried to write the remaining data, whereas `fs.writeFile()` will retry until | ||
| 4414 | + conditions, `fs.write()` might write only part of the buffer and need to be | ||
| 4415 | + retried to write the remaining data, whereas `fs.writeFile()` retries until | ||
| 4416 | 4416 | the data is entirely written (or an error occurs). | |
| 4417 | 4417 | ||
| 4418 | 4418 | The implications of this are a common source of confusion. In | |
@@ -5495,7 +5495,7 @@ changes: | |||
| 5495 | 5495 | * `path` {string|Buffer|URL} | |
| 5496 | 5496 | * `options` {Object} | |
| 5497 | 5497 | * `maxRetries` {integer} If an `EBUSY`, `EMFILE`, `ENFILE`, `ENOTEMPTY`, or | |
| 5498 | - `EPERM` error is encountered, Node.js will retry the operation with a linear | ||
| 5498 | + `EPERM` error is encountered, Node.js retries the operation with a linear | ||
| 5499 | 5499 | backoff wait of `retryDelay` milliseconds longer on each try. This option | |
| 5500 | 5500 | represents the number of retries. This option is ignored if the `recursive` | |
| 5501 | 5501 | option is not `true`. **Default:** `0`. | |
@@ -5995,7 +5995,7 @@ or `O_EXCL|O_CREAT` to `CREATE_NEW`, as accepted by `CreateFileW`. | |||
| 5995 | 5995 | The exclusive flag `'x'` (`O_EXCL` flag in open(2)) causes the operation to | |
| 5996 | 5996 | return an error if the path already exists. On POSIX, if the path is a symbolic | |
| 5997 | 5997 | link, using `O_EXCL` returns an error even if the link is to a path that does | |
| 5998 | - not exist. The exclusive flag may or may not work with network file systems. | ||
| 5998 | + not exist. The exclusive flag might not work with network file systems. | ||
| 5999 | 5999 | ||
| 6000 | 6000 | On Linux, positional writes don't work when the file is opened in append mode. | |
| 6001 | 6001 | The kernel ignores the position argument and always appends the data to | |
0 commit comments