Editorial: Update use of WebIDL "invoke a callback function" (#1320)

The only use which is not promise-returning is the "start" algorithm,
which should rethrow the exception (so it can in turn be rethrown from
the ReadableStream constructor.

Part of whatwg/webidl#1425.

Author: jeremyroman

index.bs

@@ -5251,8 +5251,8 @@ The following abstract operations support the implementation of the
  1. Let |abortAlgorithm| be an algorithm that returns [=a promise resolved with=] undefined.
  1. If |underlyingSinkDict|["{{UnderlyingSink/start}}"] [=map/exists=], then set |startAlgorithm| to
     an algorithm which returns the result of [=invoking=]
-    |underlyingSinkDict|["{{UnderlyingSink/start}}"] with argument list « |controller| »
-    and [=callback this value=] |underlyingSink|.
+    |underlyingSinkDict|["{{UnderlyingSink/start}}"] with argument list « |controller| »,
+    exception behavior "<code>rethrow</code>", and [=callback this value=] |underlyingSink|.
  1. If |underlyingSinkDict|["{{UnderlyingSink/write}}"] [=map/exists=], then set |writeAlgorithm| to
     an algorithm which takes an argument |chunk| and returns the result of [=invoking=]
     |underlyingSinkDict|["{{UnderlyingSink/write}}"] with argument list «&nbsp;|chunk|,