With my editor's hat on, there's evidence "enqueuing an operation" is confusing. Readers confuse it with queue a task, a wildly different concept.

It's understandable, because our operations queue is a misnomer, as is the verb "enqueuing"—especially when the word "operation" is absent, which it always is:

Return the result of enqueuing the following steps to connection's operation queue:

Critically, an operation is not a task. It is an asynchronous operation that begins in a task, but ends in a later different task.

What RTCPeerConnection implements is wholly a main-thread concept for serializing such operations. It is not a concept to get to main thread. It operates only on main thread.

Established terminology says such serialized asynchronous operations are chained, not queued, e.g. into promise chains:

doSomething().then(doSomethingElse)

I'll add a PR to use the terms "chain" and "operations chain" instead.

Return the result of chaining the following steps to connection's operations chain: