NaCl docs: fix TCP link

native_client_sdk/src/doc/sdk/examples.rst

 .. _sdk-examples-2:
 
 .. TODO: After default toolchain is changed to pnacl, recreate the make examples.
 
 Examples
 ========
 
 Every Native Client SDK bundle comes with a folder of example applications.
 Each example demonstrates one or two key Native Client programming concepts.
 After you've :doc:`downloaded the SDK <download>`, follow the instructions
@@ skipping 195 matching lines @@
 -------------------------------------
 
 Each example can also be launched as a packaged application. A packaged
 application is a special zip file (with a .crx extension) hosted in the Chrome
 Web Store. This file contains all of the application parts: A Chrome Web Store
 manifest file (``manifest.json``), an icon, and all of the regular Native Client
 application files. Refer to `What are Chrome Apps </apps/about_apps>`_ for more
 information about creating a packaged application.
 
 Some Pepper features, such as `TCP
-<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP
+<pepper_stable/cpp/classpp_1_1_t_c_p_socket>`_ or `UDP
 <pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ socket access, are only allowed
 in `packaged applications </apps/about_apps>`_. The examples that use these
 features must be run as `packaged applications </apps/about_apps>`_, by using
 the following command::
 
   $ make run_package
 
 You can use ``TOOLCHAIN`` and ``CONFIG`` parameters as described above to run
 with a different toolchain or configuration.
 
@@ skipping 23 matching lines @@
 
 At this point, you can use the standard GDB commands to debug your NaCl module.
 The most common commands you will use to debug are ``continue``, ``step``,
 ``next``, ``break`` and ``backtrace``. See 
 :doc:`Debugging <../devguide/devcycle/debugging>` for more information about
 debugging a Native Client application.
 
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |gear-icon| image:: /images/gear-icon.png