Editorial: fix references to Fetch and Web Sockets

Author: marcoscaceres

index.html

@@ -115,11 +115,10 @@ <h2>
         Push messaging is best suited to occasions where there is not already an active
         communications channel established between <a>user agent</a> and web application. Sending
         <a>push messages</a> requires considerably more resources when compared with more direct
-        methods of communication such as [[[fetch]]] or <a data-cite=
-        "html/web-sockets.html#network">websockets</a>. <a>Push messages</a> usually have higher
-        latency than direct communications and they can also be subject to restrictions on use.
-        Most <a>push services</a> limit the size and quantity of <a>push messages</a> that can be
-        sent.
+        methods of communication such as the [[Fetch|Fetch API]] or [[Websockets|Web Sockets]].
+        <a>Push messages</a> usually have higher latency than direct communications and they can
+        also be subject to restrictions on use. Most <a>push services</a> limit the size and
+        quantity of <a>push messages</a> that can be sent.
       </p>
     </section>
     <section>