Some link fixes

docs/index.bs

@@ -647,11 +647,11 @@ spec: webappsec-referrer-policy; urlPrefix: https://w3c.github.io/webappsec-refe
         <tbody>
           <tr>
             <td><dfn attribute for="ServiceWorkerContainer"><code>oncontrollerchange</code></dfn></td>
-            <td><code><a for="ServiceWorkerContainer" event>controllerchange</a></code></td>
+            <td>{{ServiceWorkerContainer/controllerchange!!event}}</td>
           </tr>
           <tr>
             <td><dfn attribute for="ServiceWorkerContainer"><code>onmessage</code></dfn></td>
-            <td><code><a>message</a></code></td>
+            <td>{{ServiceWorkerContainer/message!!event}}</td>
           </tr>
         </tbody>
       </table>
@@ -1598,12 +1598,12 @@ spec: webappsec-referrer-policy; urlPrefix: https://w3c.github.io/webappsec-refe
         <tr>
           <td><dfn event id="service-worker-global-scope-fetch-event"><code>fetch</code></dfn></td>
           <td>{{FetchEvent}}</td>
-          <td>[<a>Functional event</a>] The <a>http fetch</a> invokes <a>Handle Fetch</a> with |request|. As a result of performing <a>Handle Fetch</a>, the <a for="ServiceWorkerGlobalScope">service worker</a> returns a <a for="/">response</a> to the <a>http fetch</a>. The <a for="/">response</a>, represented by a {{Response}} object, can be retrieved from a {{Cache}} object or directly from network using {{WindowOrWorkerGlobalScope/fetch(input, init)|self.fetch(input, init)}} method. (A custom {{Response}} object can be another option.)</td>
+          <td>[<a>Functional event</a>] The <a for="/">http fetch</a> invokes <a>Handle Fetch</a> with |request|. As a result of performing <a>Handle Fetch</a>, the <a for="ServiceWorkerGlobalScope">service worker</a> returns a <a for="/">response</a> to the <a for="/">http fetch</a>. The <a for="/">response</a>, represented by a {{Response}} object, can be retrieved from a {{Cache}} object or directly from network using {{WindowOrWorkerGlobalScope/fetch(input, init)|self.fetch(input, init)}} method. (A custom {{Response}} object can be another option.)</td>
         </tr>
         <tr>
           <td><dfn event id="service-worker-global-scope-foreignfetch-event"><code>foreignfetch</code></dfn></td>
           <td>{{FetchEvent}}</td>
-          <td>[<a>Functional event</a>] The <a>http fetch</a> invokes [[#on-foreign-fetch-request-algorithm]] with |request|. As a result of performing [[#on-foreign-fetch-request-algorithm]], the <a for="ServiceWorkerGlobalScope">service worker</a> returns a <a for="/">response</a> to the <a>http fetch</a>. The <a for="/">response</a>, represented by a {{Response}} object, can be retrieved from a {{Cache}} object or directly from network using {{WindowOrWorkerGlobalScope/fetch(input, init)|self.fetch(input, init)}} method. (A custom {{Response}} object can be another option.)</td>
+          <td>[<a>Functional event</a>] The <a for="/">http fetch</a> invokes [[#on-foreign-fetch-request-algorithm]] with |request|. As a result of performing [[#on-foreign-fetch-request-algorithm]], the <a for="ServiceWorkerGlobalScope">service worker</a> returns a <a for="/">response</a> to the <a for="/">http fetch</a>. The <a for="/">response</a>, represented by a {{Response}} object, can be retrieved from a {{Cache}} object or directly from network using {{WindowOrWorkerGlobalScope/fetch(input, init)|self.fetch(input, init)}} method. (A custom {{Response}} object can be another option.)</td>
         </tr>
         <tr>
           <td><dfn event><code>message</code></dfn></td>
@@ -2161,7 +2161,7 @@ spec: webappsec-referrer-policy; urlPrefix: https://w3c.github.io/webappsec-refe
 
     The implementers are encouraged to note:
 
-      * Plug-ins should not load via <a for="/">service workers</a>. As plug-ins may get their security origins from their own urls, the embedding <a for="/">service worker</a> cannot handle it. For this reason, the <a>Handle Fetch</a> algorithm makes the <a>potential-navigation-or-subresource request</a> (whose context is either <code>&lt;embed&gt;</code> or <code>&lt;object&gt;</code>) immediately fallback to the network without dispatching <a for="/">fetch</a> event.
+      * Plug-ins should not load via <a for="/">service workers</a>. As plug-ins may get their security origins from their own urls, the embedding <a for="/">service worker</a> cannot handle it. For this reason, the <a>Handle Fetch</a> algorithm makes the <a>potential-navigation-or-subresource request</a> (whose context is either <code>&lt;embed&gt;</code> or <code>&lt;object&gt;</code>) immediately fallback to the network without dispatching {{fetch!!event}} event.
       * Some of the legacy networking stack code may need to be carefully audited to understand the ramifications of interactions with <a for="/">service workers</a>.
   </section>