Skip to content

doc: fix typos in Web Streams API documentation #39351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

doc: fix typos in Web Streams API documentation #39351

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions doc/api/webstreams.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -352,7 +352,7 @@ method to acquire the async iterator and set the `preventCancel` option to
The {ReadableStream} must not be locked (that is, it must not have an existing
active reader). During the async iteration, the {ReadableStream} will be locked.

#### Transfering with `postMessage()`
#### Transferring with `postMessage()`

A {ReadableStream} instance can be transferred using a {MessagePort}.

Expand Down Expand Up @@ -554,7 +554,7 @@ the pooled `Buffer` instances. When a `Buffer`, {TypedArray},
or {DataView} is passed in to `readableStreamBYOBReader.read()`,
the view's underlying `ArrayBuffer` is *detached*, invalidating
all existing views that may exist on that `ArrayBuffer`. This
can have disasterous consequences for your application.
can have disastrous consequences for your application.

#### `readableStreamBYOBReader.releaseLock()`
<!-- YAML
Expand Down Expand Up @@ -795,7 +795,7 @@ The `writableStream.locked` property is `false` by default, and is
switched to `true` while there is an active writer attached to this
`WritableStream`.

#### Transfering with postMessage()
#### Transferring with postMessage()

A {WritableStream} instance can be transferred using a {MessagePort}.

Expand Down Expand Up @@ -998,7 +998,7 @@ added: REPLACEME

* Type: {WritableStream}

#### Transfering with postMessage()
#### Transferring with postMessage()

A {TransformStream} instance can be transferred using a {MessagePort}.

Expand Down Expand Up @@ -1048,7 +1048,7 @@ added: REPLACEME

* `reason` {any}

Signals to both the readable and writable side that an error has occured
Signals to both the readable and writable side that an error has occurred
while processing the transform data, causing both sides to be abruptly
closed.

Expand Down