diff --git a/webrtc.html b/webrtc.html index 644530128..0d0316706 100644 --- a/webrtc.html +++ b/webrtc.html @@ -1667,7 +1667,7 @@

  • - In parallel, start the process to apply + [=In parallel=], start the process to apply description as described in [[!RFC9429]], with these additional restrictions: @@ -3613,7 +3613,7 @@

  • - In parallel, begin the [= in-parallel steps to create + [=In parallel=], begin the [= in-parallel steps to create an offer =] given connection and p.

    @@ -3675,7 +3675,7 @@

    If connection 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 connection and p, and abort these steps. @@ -3906,7 +3906,7 @@

  • - In parallel, begin the [= in-parallel steps to create + [=In parallel=], begin the [= in-parallel steps to create an answer =] given connection and p.

    @@ -3967,7 +3967,7 @@

    If connection 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 connection and p, and abort these steps. @@ -4514,7 +4514,7 @@

  • - In parallel, if the candidate is not [= + [=In parallel=], if the candidate is not [= administratively prohibited =], add the ICE candidate candidate as described in [[!RFC9429]]. @@ -7212,7 +7212,7 @@

  • - Run the following steps in parallel: + Run the following steps [=in parallel=]:

    1. @@ -9070,7 +9070,7 @@

    2. Let p be a new promise.
    3. -
    4. In parallel, configure the media stack to use +
    5. [=In parallel=], configure the media stack to use parameters to transmit sender.{{RTCRtpSender/[[SenderTrack]]}}.
        @@ -9319,7 +9319,7 @@

      1. - Run the following steps in parallel: + Run the following steps [=in parallel=]:

        1. Let p be a new promise, and run the following - steps in parallel: + steps [=in parallel=]:

          1. @@ -10340,7 +10340,7 @@

            {{RTCRtpReceiver/[[ReceiverTrack]]}}.

          2. -

            In parallel, begin executing the following steps:

            +

            [=in parallel=], begin executing the following steps:

            1. Update the underlying system about the new target, @@ -10563,7 +10563,7 @@

            2. Let p be a new promise, and run the following - steps in parallel: + steps [=in parallel=]:

              1. @@ -13472,7 +13472,7 @@

              2. Return channel and continue the following - steps in parallel. + steps [=in parallel=].

              3. @@ -14111,7 +14111,7 @@

              4. - Run the following steps in parallel: + Run the following steps [=in parallel=]:

                1. @@ -14477,7 +14477,7 @@

                  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 @@ -14768,7 +14768,7 @@

                  {{OperationError}}.

                  - 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}}. @@ -15600,7 +15600,7 @@

                2. - Run the following steps in parallel: + Run the following steps [=in parallel=]: