Fix broken links on NaCl pages of developer.chrome.com.

BUG=none
R=
TEST=none
NOTRY=true
(documentation only change)

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

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

native_client_sdk/doc_generated/community/middleware.html

@@ -17,7 +17,7 @@ to Native Client. For an example of some applications that were produced using t
     <tr class="col3">
       <td><a href="http://www.unity3d.com" target="_blank"><img src="/native-client/images/unity_logo.jpg"></a></td>
       <td><a href="http://www.mono-project.com/" target="_blank"><img src="/native-client/images/mp_mono_logo.png"></a></td>
-      <td><a href="http:havok.com/" target="_blank"><img src="/native-client/images/havok_logo.jpg"></a></td>
+      <td><a href="http://havok.com/" target="_blank"><img src="/native-client/images/havok_logo.jpg"></a></td>
     </tr>
 
     <tr class="col3">

native_client_sdk/doc_generated/devguide/devcycle/vs-addin.html

@@ -417,7 +417,7 @@ while running the program.</p>
 <p>NaCl32 and NaClARM executables (.nexe files) cannot be run or debugged from
 Visual Studio.</p>
 <p>NaCl64 executables (.nexe files) are compiled using one of the Native Client
-toolchains in the SDK, which create an <a class="reference external" href="`http://en.wikipedia.org/wiki/Executable_and_Linkable_Format">ELF-formatted</a> executable. To
+toolchains in the SDK, which create an <a class="reference external" href="http://en.wikipedia.org/wiki/Executable_and_Linkable_Format">ELF-formatted</a> executable. To
 debug a running .nexe you must use nacl-gdb, which is a command line debugger
 that is not directly integrated with Visual Studio. When you start a debugging
 session running from a NaCl64 platform, Visual Studio automatically launches

native_client_sdk/doc_generated/io2014.html

@@ -211,7 +211,7 @@ $ make serve
 <p>Thanks for checking out our environment.
 Things are rapidly changing and in the coming months you can expect to see
 further improvements and filling out of our platform and library support.</p>
-<p>Follow the status of the NaCl Dev Environment at <a class="reference external" href="naclenv">this page</a>.</p>
+<p>Follow the status of the NaCl Dev Environment at <a class="reference internal" href="/native-client/nacldev.html"><em>this page</em></a>.</p>
 </section>
 
 {{/partials.standard_nacl_article}}

native_client_sdk/doc_generated/publications-and-presentations.html

@@ -52,11 +52,7 @@ Porting Your C++ Game to Native Client</td>
 <td>&#8212;</td>
 <td><a class="reference external" href="https://www.youtube.com/watch?v=g3aBfkFbPWk">Native Client Update and Showcase</a></td>
 </tr>
-<tr class="row-odd"><td>2011/05/11</td>
-<td><a class="reference external" href="https://www.google.com/events/io/2011/index-live.html">Google I/O 2011</a></td>
-<td><a class="reference external" href="https://www.google.com/events/io/2011/sessions/beyond-javascript-programming-the-web-with-native-client.html">Beyond JavaScript: Programming the Web with Native Client</a></td>
-</tr>
-<tr class="row-even"><td>2010/11/04</td>
+<tr class="row-odd"><td>2010/11/04</td>
 <td><a class="reference external" href="http://llvm.org/devmtg/2010-11/">2010 LLVM Developers&#8217; Meeting</a></td>
 <td><a class="reference external" href="http://llvm.org/devmtg/2010-11/videos/Sehr_NativeClient-desktop.mp4">Portable Native Client</a></td>
 </tr>

native_client_sdk/doc_generated/reference/pnacl-bitcode-abi.html

@@ -148,8 +148,8 @@ distributed pexes.</p>
 <a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html"><em>PNaCl C/C++ Language Support</em></a> for more details.</p>
 <h3 id="memory-model-for-concurrent-operations">Memory Model for Concurrent Operations</h3>
 <p><a class="reference external" href="http://llvm.org/releases/3.3/docs/LangRef.html#memmodel">LLVM LangRef: Memory Model for Concurrent Operations</a></p>
-<p>See the <a class="reference external" href="PNaClDeveloperGuide.html">PNaCl Developer&#8217;s Guide</a> for more
-details.</p>
+<p>See the <a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html"><em>PNaCl C/C++ Language Support</em></a>
+for details.</p>
 <h3 id="fast-math-flags">Fast-Math Flags</h3>
 <p><a class="reference external" href="http://llvm.org/releases/3.3/docs/LangRef.html#fastmath">LLVM LangRef: Fast-Math Flags</a></p>
 <p>Fast-math mode is not currently supported by the PNaCl bitcode.</p>

native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html

@@ -64,7 +64,7 @@ with other NaCl toolchains.</p>
 <h3 id="memory-model-for-concurrent-operations">Memory Model for Concurrent Operations</h3>
 <p>The memory model offered by PNaCl relies on the same coding guidelines
 as the C11/C++11 one: concurrent accesses must always occur through
-atomic primitives (offered by <a class="reference external" href="PNaClLangRef.html#atomicintrinsics">atomic intrinsics</a>), and these accesses must always
+atomic primitives (offered by <a class="reference internal" href="/native-client/reference/pnacl-bitcode-abi.html#bitcode-atomicintrinsics"><em>atomic intrinsics</em></a>), and these accesses must always
 occur with the same size for the same memory location. Visibility of
 stores is provided on a happens-before basis that relates memory
 locations to each other as the C11/C++11 standards do.</p>

native_client_sdk/src/doc/devguide/devcycle/vs-addin.rst

@@ -485,7 +485,7 @@ Visual Studio.
 
 NaCl64 executables (.nexe files) are compiled using one of the Native Client
 toolchains in the SDK, which create an `ELF-formatted
-<`http://en.wikipedia.org/wiki/Executable_and_Linkable_Format>`_ executable. To
+<http://en.wikipedia.org/wiki/Executable_and_Linkable_Format>`_ executable. To
 debug a running .nexe you must use nacl-gdb, which is a command line debugger
 that is not directly integrated with Visual Studio. When you start a debugging
 session running from a NaCl64 platform, Visual Studio automatically launches

native_client_sdk/src/doc/io2014.rst

@@ -203,4 +203,4 @@ Thanks for checking out our environment.
 Things are rapidly changing and in the coming months you can expect to see
 further improvements and filling out of our platform and library support.
 
-Follow the status of the NaCl Dev Environment at `this page <naclenv>`_.
+Follow the status of the NaCl Dev Environment at :doc:`this page <nacldev>`.

native_client_sdk/src/doc/publications-and-presentations.rst

@@ -54,11 +54,6 @@ Recent talks and demos
      - ---
      - `Native Client Update and Showcase
        <https://www.youtube.com/watch?v=g3aBfkFbPWk>`_
-   * - 2011/05/11
-     - `Google I/O 2011
-       <https://www.google.com/events/io/2011/index-live.html>`_
-     - `Beyond JavaScript: Programming the Web with Native Client
-       <https://www.google.com/events/io/2011/sessions/beyond-javascript-programming-the-web-with-native-client.html>`_
    * - 2010/11/04
      - `2010 LLVM Developers' Meeting
        <http://llvm.org/devmtg/2010-11/>`_

native_client_sdk/src/doc/reference/pnacl-bitcode-abi.rst

@@ -169,8 +169,8 @@ Memory Model for Concurrent Operations
 `LLVM LangRef: Memory Model for Concurrent Operations
 <http://llvm.org/releases/3.3/docs/LangRef.html#memmodel>`_
 
-See the `PNaCl Developer's Guide <PNaClDeveloperGuide.html>`_ for more
-details.
+See the :doc:`PNaCl C/C++ Language Support <pnacl-c-cpp-language-support>`
+for details.
 
 Fast-Math Flags
 ---------------

native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst

@@ -50,8 +50,8 @@ Memory Model for Concurrent Operations
 
 The memory model offered by PNaCl relies on the same coding guidelines
 as the C11/C++11 one: concurrent accesses must always occur through
-atomic primitives (offered by `atomic intrinsics
-<PNaClLangRef.html#atomicintrinsics>`_), and these accesses must always
+atomic primitives (offered by :ref:`atomic intrinsics 
+<bitcode_atomicintrinsics>`), and these accesses must always
 occur with the same size for the same memory location. Visibility of
 stores is provided on a happens-before basis that relates memory
 locations to each other as the C11/C++11 standards do.