Skip to content

Commit

Permalink
Merge pull request #2981 from w3c/in-parallel
Browse files Browse the repository at this point in the history
Add link to 'in parallel' definition
  • Loading branch information
jan-ivar authored Jun 27, 2024
2 parents 65d3ae3 + 5e45edd commit 3b60cb5
Showing 1 changed file with 17 additions and 17 deletions.
34 changes: 17 additions & 17 deletions webrtc.html
Original file line number Diff line number Diff line change
Expand Up @@ -1667,7 +1667,7 @@ <h4>
</li>
<li>
<p data-tests="">
In parallel, start the process to apply
[=In parallel=], start the process to apply
<var>description</var> as described in <span data-jsep=
"processing-a-local-desc processing-a-remote-desc">[[!RFC9429]]</span>,
with these additional restrictions:
Expand Down Expand Up @@ -3613,7 +3613,7 @@ <h2>
</li>
<li>
<p>
In parallel, begin the [= in-parallel steps to create
[=In parallel=], begin the [= in-parallel steps to create
an offer =] given <var>connection</var> and
<var>p</var>.
</p>
Expand Down Expand Up @@ -3675,7 +3675,7 @@ <h2>
<p>
If <var>connection</var> was modified in such a way
that additional inspection of the [= offerer's system
state =] is necessary, then in parallel begin the [=
state =] is necessary, then [=in parallel=] begin the [=
in-parallel steps to create an offer =] again, given
<var>connection</var> and <var>p</var>, and abort these
steps.
Expand Down Expand Up @@ -3906,7 +3906,7 @@ <h2>
</li>
<li>
<p>
In parallel, begin the [= in-parallel steps to create
[=In parallel=], begin the [= in-parallel steps to create
an answer =] given <var>connection</var> and
<var>p</var>.
</p>
Expand Down Expand Up @@ -3967,7 +3967,7 @@ <h2>
<p>
If <var>connection</var> was modified in such a way
that additional inspection of the [= answerer's system
state =] is necessary, then in parallel begin the [=
state =] is necessary, then [=in parallel=] begin the [=
in-parallel steps to create an answer =] again given
<var>connection</var> and <var>p</var>, and abort these
steps.
Expand Down Expand Up @@ -4514,7 +4514,7 @@ <h2>
</li>
<li>
<p data-tests="">
In parallel, if the candidate is not [=
[=In parallel=], if the candidate is not [=
administratively prohibited =], add the ICE
candidate <var>candidate</var> as described in
<span data-jsep="addicecandidate">[[!RFC9429]]</span>.
Expand Down Expand Up @@ -7212,7 +7212,7 @@ <h2>
</li>
<li>
<p>
Run the following steps in parallel:
Run the following steps [=in parallel=]:
</p>
<ol>
<li>
Expand Down Expand Up @@ -9070,7 +9070,7 @@ <h2>
</li>
<li class="no-test-needed">Let <var>p</var> be a new promise.
</li>
<li>In parallel, configure the media stack to use
<li>[=In parallel=], configure the media stack to use
<var>parameters</var> to transmit
<var>sender</var>.{{RTCRtpSender/[[SenderTrack]]}}.
<ol>
Expand Down Expand Up @@ -9319,7 +9319,7 @@ <h2>
</li>
<li>
<p>
Run the following steps in parallel:
Run the following steps [=in parallel=]:
</p>
<ol>
<li data-tests=
Expand Down Expand Up @@ -9501,7 +9501,7 @@ <h2>
<li>
<p>
Let <var>p</var> be a new promise, and run the following
steps in parallel:
steps [=in parallel=]:
</p>
<ol>
<li>
Expand Down Expand Up @@ -10340,7 +10340,7 @@ <h2>
{{RTCRtpReceiver/[[ReceiverTrack]]}}.</p>
</li>
<li>
<p>In parallel, begin executing the following steps:</p>
<p>[=in parallel=], begin executing the following steps:</p>
<ol>
<li>
<p>Update the underlying system about the new <var>target</var>,
Expand Down Expand Up @@ -10563,7 +10563,7 @@ <h2>
<li>
<p>
Let <var>p</var> be a new promise, and run the following
steps in parallel:
steps [=in parallel=]:
</p>
<ol>
<li>
Expand Down Expand Up @@ -13472,7 +13472,7 @@ <h2>
<li>
<p>
Return <var>channel</var> and continue the following
steps in parallel.
steps [=in parallel=].
</p>
</li>
<li>
Expand Down Expand Up @@ -14111,7 +14111,7 @@ <h4>
</li>
<li>
<p>
Run the following steps in parallel:
Run the following steps [=in parallel=]:
</p>
<ol>
<li>
Expand Down Expand Up @@ -14477,7 +14477,7 @@ <h2>
exposes the number of bytes of application data (UTF-8 text
and binary data) that have been queued using
{{RTCDataChannel/send()}}. Even though the data transmission
can occur in parallel, the returned value MUST NOT be
can occur [=in parallel=], the returned value MUST NOT be
decreased before the current task yielded back to the event
loop to prevent race conditions. The value does not include
framing overhead incurred by the protocol, or buffering done
Expand Down Expand Up @@ -14768,7 +14768,7 @@ <h2>
{{OperationError}}.
</p>
<div class="note">
The actual transmission of data occurs in parallel. If
The actual transmission of data occurs [=in parallel=]. If
sending data leads to an SCTP-level error, the application
will be notified asynchronously through
{{RTCDataChannel/onerror}}.
Expand Down Expand Up @@ -15600,7 +15600,7 @@ <h2>
<!-- See [= stats selection algorithm =] for test status. -->
<li class="no-test-needed">
<p>
Run the following steps in parallel:
Run the following steps [=in parallel=]:
</p>
<ol>
<li>
Expand Down

0 comments on commit 3b60cb5

Please sign in to comment.