Commit ff9ef61
doc: use serial comma in stream docs
Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
PR-URL: #44609
Reviewed-By: theanarkh <theratliter@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Harshitha K P <harshitha014@gmail.com>1 parent bbbb446 commit ff9ef61
1 file changed
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -584,7 +584,7 @@ added: v11.4.0 | |||
| 584 | 584 | * {boolean} | |
| 585 | 585 | ||
| 586 | 586 | Is `true` if it is safe to call [`writable.write()`][stream-write], which means | |
| 587 | - the stream has not been destroyed, errored or ended. | ||
| 587 | + the stream has not been destroyed, errored, or ended. | ||
| 588 | 588 | ||
| 589 | 589 | ##### `writable.writableAborted` | |
| 590 | 590 | ||
@@ -1499,7 +1499,7 @@ changes: | |||
| 1499 | 1499 | ||
| 1500 | 1500 | * `chunk` {Buffer|Uint8Array|string|null|any} Chunk of data to unshift onto the | |
| 1501 | 1501 | read queue. For streams not operating in object mode, `chunk` must be a | |
| 1502 | - string, `Buffer`, `Uint8Array` or `null`. For object mode streams, `chunk` | ||
| 1502 | + string, `Buffer`, `Uint8Array`, or `null`. For object mode streams, `chunk` | ||
| 1503 | 1503 | may be any JavaScript value. | |
| 1504 | 1504 | * `encoding` {string} Encoding of string chunks. Must be a valid | |
| 1505 | 1505 | `Buffer` encoding, such as `'utf8'` or `'ascii'`. | |
@@ -2896,7 +2896,7 @@ added: v1.2.0 | |||
| 2896 | 2896 | ||
| 2897 | 2897 | For many simple cases, it is possible to create a stream without relying on | |
| 2898 | 2898 | inheritance. This can be accomplished by directly creating instances of the | |
| 2899 | - `stream.Writable`, `stream.Readable`, `stream.Duplex` or `stream.Transform` | ||
| 2899 | + `stream.Writable`, `stream.Readable`, `stream.Duplex`, or `stream.Transform` | ||
| 2900 | 2900 | objects and passing appropriate methods as constructor options. | |
| 2901 | 2901 | ||
| 2902 | 2902 | ```js | |
@@ -3524,7 +3524,7 @@ changes: | |||
| 3524 | 3524 | * Returns: {boolean} `true` if additional chunks of data may continue to be | |
| 3525 | 3525 | pushed; `false` otherwise. | |
| 3526 | 3526 | ||
| 3527 | - When `chunk` is a `Buffer`, `Uint8Array` or `string`, the `chunk` of data will | ||
| 3527 | + When `chunk` is a `Buffer`, `Uint8Array`, or `string`, the `chunk` of data will | ||
| 3528 | 3528 | be added to the internal queue for users of the stream to consume. | |
| 3529 | 3529 | Passing `chunk` as `null` signals the end of the stream (EOF), after which no | |
| 3530 | 3530 | more data can be written. | |
@@ -4199,7 +4199,7 @@ situations within Node.js where this is done, particularly in the | |||
| 4199 | 4199 | ||
| 4200 | 4200 | Use of `readable.push('')` is not recommended. | |
| 4201 | 4201 | ||
| 4202 | - Pushing a zero-byte string, `Buffer` or `Uint8Array` to a stream that is not in | ||
| 4202 | + Pushing a zero-byte string, `Buffer`, or `Uint8Array` to a stream that is not in | ||
| 4203 | 4203 | object mode has an interesting side effect. Because it _is_ a call to | |
| 4204 | 4204 | [`readable.push()`][stream-push], the call will end the reading process. | |
| 4205 | 4205 | However, because the argument is an empty string, no data is added to the | |
0 commit comments