From f63ec41a3d589adba5751335e34fe4ff7a248f26 Mon Sep 17 00:00:00 2001
From: Jan-Ivar Bruaroey <jan-ivar@users.noreply.github.com>
Date: Thu, 11 Jul 2024 22:57:31 -0400
Subject: [PATCH] Editorial: Update WebRTC endpoint pair example

Closes #1317.
---
 index.bs | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 9a7de963..2266b924 100644
--- a/index.bs
+++ b/index.bs
@@ -7464,14 +7464,13 @@ web developer code insert [=transform streams=] into the middle of them.
 
  <xmp highlight="js">
  const { readable, writable } = createEndpointPair();
- readable.pipeThrough(new TransformStream(...)).pipeTo(writable);
+ await readable.pipeThrough(new TransformStream(...)).pipeTo(writable);
  </xmp>
 </div>
 
-<p class="example" id="example-endpoint-pair-webrtc"><cite>WebRTC Insertable Media using
-Streams</cite> is an example of this technique, with its `sender.createEncodedStreams()` and
-`receiver.createEncodedStreams()` methods.
-<!-- TODO cite it and cross-link to it https://github.com/tobie/specref/issues/620 -->
+<p class="example" id="example-endpoint-pair-webrtc"><cite>WebRTC Encoded Transform</cite>
+is an example of this technique, with its {{RTCRtpScriptTransformer}} interface which has
+both `readable` and `writable` attributes.
 
 Despite such endpoint pairs obeying the `readable`/`writable` property contract, it never makes
 sense to pass them to {{ReadableStream/pipeThrough()}}.