NaCl docs: fix TCP link

R= binji@chromium.org
BUG=none

Review URL: https://codereview.chromium.org/910983002

Cr-Commit-Position: refs/heads/master@{#315431}

native_client_sdk/doc_generated/faq.html

@@ -419,7 +419,7 @@ generally straightforward, with large libraries often requiring no
 source change.</p>
 <p>The following kinds of code may be more challenging to port:</p>
 <ul class="small-gap">
-<li>Code that does direct <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">TCP</a> or
+<li>Code that does direct <a class="reference external" href="pepper_stable/cpp/classpp_1_1_t_c_p_socket">TCP</a> or
 <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">UDP</a> networking. For security
 reasons these APIs are only available to <a class="reference external" href="/apps/about_apps">packaged applications</a> after asking for the appropriate permissions, not on the
 open web. Native Client is otherwise restricted to the networking APIs

native_client_sdk/doc_generated/sdk/examples.html

@@ -171,7 +171,7 @@ Web Store. This file contains all of the application parts: A Chrome Web Store
 manifest file (<code>manifest.json</code>), an icon, and all of the regular Native Client
 application files. Refer to <a class="reference external" href="/apps/about_apps">What are Chrome Apps</a> for more
 information about creating a packaged application.</p>
-<p>Some Pepper features, such as <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">TCP</a> or <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">UDP</a> socket access, are only allowed
+<p>Some Pepper features, such as <a class="reference external" href="pepper_stable/cpp/classpp_1_1_t_c_p_socket">TCP</a> or <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">UDP</a> socket access, are only allowed
 in <a class="reference external" href="/apps/about_apps">packaged applications</a>. The examples that use these
 features must be run as <a class="reference external" href="/apps/about_apps">packaged applications</a>, by using
 the following command:</p>

native_client_sdk/src/doc/faq.rst

@@ -493,7 +493,7 @@ source change.
 
 The following kinds of code may be more challenging to port:
 
-* Code that does direct `TCP <pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or
+* Code that does direct `TCP <pepper_stable/cpp/classpp_1_1_t_c_p_socket>`_ or
   `UDP <pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ networking. For security
   reasons these APIs are only available to `packaged applications
   </apps/about_apps>`_ after asking for the appropriate permissions, not on the

native_client_sdk/src/doc/sdk/examples.rst

@@ -213,7 +213,7 @@ 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