Skip to content

Commit 1238886

Browse files
committed
fixup! doc: use serial comma in fs docs
1 parent 4d5bbc7 commit 1238886

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

doc/api/fs.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -704,7 +704,7 @@ changes:
704704
* Returns: {Promise}
705705
706706
Asynchronously writes data to a file, replacing the file if it already exists.
707-
`data` can be a string, a buffer, an {AsyncIterable} or {Iterable} object.
707+
`data` can be a string, a buffer, an {AsyncIterable}, or an {Iterable} object.
708708
The promise is resolved with no arguments upon success.
709709
710710
If `options` is a string, then it specifies the `encoding`.
@@ -1684,7 +1684,7 @@ access(file, constants.R_OK | constants.W_OK, (err) => {
16841684
```
16851685
16861686
Do not use `fs.access()` to check for the accessibility of a file before calling
1687-
`fs.open()`, `fs.readFile()` or `fs.writeFile()`. Doing
1687+
`fs.open()`, `fs.readFile()`, or `fs.writeFile()`. Doing
16881688
so introduces a race condition, since other processes may change the file's
16891689
state between the two calls. Instead, user code should open/read/write the
16901690
file directly and handle the error raised if the file is not accessible.
@@ -2409,7 +2409,7 @@ has only one boolean parameter. This is one reason `fs.access()` is recommended
24092409
instead of `fs.exists()`.
24102410
24112411
Using `fs.exists()` to check for the existence of a file before calling
2412-
`fs.open()`, `fs.readFile()` or `fs.writeFile()` is not recommended. Doing
2412+
`fs.open()`, `fs.readFile()`, or `fs.writeFile()` is not recommended. Doing
24132413
so introduces a race condition, since other processes may change the file's
24142414
state between the two calls. Instead, user code should open/read/write the
24152415
file directly and handle the error raised if the file does not exist.
@@ -3873,7 +3873,7 @@ Asynchronous stat(2). The callback gets two arguments `(err, stats)` where
38733873
In case of an error, the `err.code` will be one of [Common System Errors][].
38743874

38753875
Using `fs.stat()` to check for the existence of a file before calling
3876-
`fs.open()`, `fs.readFile()` or `fs.writeFile()` is not recommended.
3876+
`fs.open()`, `fs.readFile()`, or `fs.writeFile()` is not recommended.
38773877
Instead, user code should open/read/write the file directly and handle the
38783878
error raised if the file is not available.
38793879

@@ -6363,7 +6363,7 @@ changes:
63636363
63646364
A {fs.Stats} object provides information about a file.
63656365
6366-
Objects returned from [`fs.stat()`][], [`fs.lstat()`][] and [`fs.fstat()`][] and
6366+
Objects returned from [`fs.stat()`][], [`fs.lstat()`][], [`fs.fstat()`][], and
63676367
their synchronous counterparts are of this type.
63686368
If `bigint` in the `options` passed to those methods is true, the numeric values
63696369
will be `bigint` instead of `number`, and the object will contain additional
@@ -7521,7 +7521,7 @@ fs.open('<directory>', 'a+', (err, fd) => {
75217521
```
75227522
75237523
On Windows, opening an existing hidden file using the `'w'` flag (either
7524-
through `fs.open()` or `fs.writeFile()` or `fsPromises.open()`) will fail with
7524+
through `fs.open()`, `fs.writeFile()`, or `fsPromises.open()`) will fail with
75257525
`EPERM`. Existing hidden files can be opened for writing with the `'r+'` flag.
75267526
75277527
A call to `fs.ftruncate()` or `filehandle.truncate()` can be used to reset

0 commit comments

Comments
 (0)