Merge pull request #178 from shaseley/replace-signalabort

Editorial: Call AbortController's "signal abort" instead of AbortSignal's

Author: jan-ivar

index.bs

@@ -147,14 +147,14 @@ The `transform` setter steps are:
 5. Initialize |newPipeToController| to a new {{AbortController}}.
 6. If [=this=].`[[pipeToController]]` is not null, run the following steps:
     1. [=AbortSignal/Add=] the [$chain transform algorithm$] to [=this=].`[[pipeToController]]`.signal.
-    2. [=AbortSignal/signal abort=] [=this=].`[[pipeToController]]`.signal.
+    2. [=AbortController/signal abort=] on [=this=].`[[pipeToController]]`.
 7. Else, run the [$chain transform algorithm$] steps.
 8. Set [=this=].`[[pipeToController]]` to |newPipeToController|.
 9. Set [=this=].`[[transform]]` to |transform|.
 10. Run the steps in the set of [$association steps$] of |transform| with [=this=].
 
 The <dfn abstract-op>chain transform algorithm</dfn> steps are defined as:
-1. If |newPipeToController| is [=AbortSignal/aborted=], abort these steps.
+1. If |newPipeToController|.signal is [=AbortSignal/aborted=], abort these steps.
 2. [=ReadableStreamDefaultReader/Release=] |reader|.
 3. [=WritableStreamDefaultWriter/Release=] |writer|.
 4. Assert that |newPipeToController| is the same object as |rtcObject|.`[[pipeToController]]`.