to send and receive data over the network.
For more information,
see the
-<a href="sockets_udp.html">Sockets UDP</a>,
-<a href="sockets_tcp.html">Sockets TCP</a> and
-<a href="sockets_tcp_server.html">Sockets TCP Server</a> APIs.
+<a href="sockets_udp">Sockets UDP</a>,
+<a href="sockets_tcp">Sockets TCP</a> and
+<a href="sockets_tcp_server">Sockets TCP Server</a> APIs.
</p>
<p class="note">
<b>API Samples: </b>
Want to play with the code?
Check out the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/telnet">telnet</a>
-and <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/udp">udp</a> samples.
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/telnet">telnet</a>
+and <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/udp">udp</a> samples.
</p>
<h2 id="manifest">Manifest requirements</h2>
<p>
For Chrome Apps that use TCP or UDP,
-add the <a href="manifest/sockets.html">sockets</a> entry to the manifest
+add the <a href="manifest/sockets">sockets</a> entry to the manifest
and specify the IP end point permission rules.
For example:
</p>
</pre>
<p>
-See <a href="manifest/sockets.html">Sockets Manifest Key</a> for detailed
+See <a href="manifest/sockets">Sockets Manifest Key</a> for detailed
description of the syntax.
</p>