Removing nav where it clashes with tables, and removing some links.

I spent many cycles tweaking these RST tables to no avail.

We shouldn't assume that people will have a site running, so we should de-link these.

BUG=374811

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272358 0039d316-1c4b-4281-b951-d872f2087c98

native_client_sdk/doc_generated/devguide/coding/progress-events.html

-{{+bindTo:partials.standard_nacl_article}}
+{{+bindTo:partials.standard_nacl_api}}
 
 <section id="progress-events">
-<span id="devcycle-progress-events"></span><h1 id="progress-events"><span id="devcycle-progress-events"></span>Progress Events</h1>
+<h1 id="progress-events">Progress Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#module-loading-and-progress-events" id="id3">Module loading and progress events</a></li>
@@ -431,4 +431,4 @@ may nevertheless be useful for temporary debugging.</li>
 </ul>
 </section></section>
 
-{{/partials.standard_nacl_article}}
+{{/partials.standard_nacl_api}}

native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html

-{{+bindTo:partials.standard_nacl_article}}
+{{+bindTo:partials.standard_nacl_api}}
 
 <section id="view-change-focus-and-input-events">
-<span id="view-focus-input-events"></span><h1 id="view-change-focus-and-input-events"><span id="view-focus-input-events"></span>View Change, Focus, and Input Events</h1>
+<h1 id="view-change-focus-and-input-events">View Change, Focus, and Input Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id2">Overview</a></li>
@@ -340,4 +340,4 @@ the <code>event_queue_</code> and the worker thread takes events from the
 thread, so as not to slow down the browser.</p>
 </section></section></section>
 
-{{/partials.standard_nacl_article}}
+{{/partials.standard_nacl_api}}

native_client_sdk/doc_generated/devguide/devcycle/running.html

-{{+bindTo:partials.standard_nacl_article}}
+{{+bindTo:partials.standard_nacl_api}}
 
 <section id="running">
-<span id="devcycle-running"></span><h1 id="running"><span id="devcycle-running"></span>Running</h1>
+<h1 id="running">Running</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id5">Introduction</a></li>
@@ -198,7 +198,7 @@ $ make serve
 <p>By default, the server listens for requests on port 5103. You can use the server
 to run most applications under the <code>examples</code> directory where you started the
 server. For example, to run the <code>flock</code> example in the SDK, start the server
-and point your browser to <a class="reference external" href="http://localhost:5103/demo/flock/">http://localhost:5103/demo/flock/</a>.</p>
+and point your browser to <code>http://localhost:5103/demo/flock/</code>.</p>
 <p>Some of the applications need special flags to Chrome, and must be run with the
 <code>make run</code> command. See <a class="reference internal" href="/native-client/sdk/examples.html#id1"><em>Run the SDK examples</em></a> for more details.</p>
 <section id="chrome-web-store-metadata">
@@ -438,4 +438,4 @@ you must first unpublish the application. For additional information see
 to test accounts</a>.</p>
 </section></section>
 
-{{/partials.standard_nacl_article}}
+{{/partials.standard_nacl_api}}

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

-{{+bindTo:partials.standard_nacl_article}}
+{{+bindTo:partials.standard_nacl_api}}
 
 <section id="debugging-with-visual-studio">
 <h1 id="debugging-with-visual-studio">Debugging With Visual Studio</h1>
@@ -189,12 +189,12 @@ example):</p>
 </thead>
 <tbody valign="top">
 <tr class="row-even"><td>NACL_SDK_ROOT</td>
-<td>The path to the pepper directory in the SDK. Example:
-<code>C:\nacl_sdk\pepper_23</code></td>
+<td>The path to the pepper directory in the SDK.
+For example: <code>C:\nacl_sdk\pepper_23</code></td>
 </tr>
 <tr class="row-odd"><td>CHROME_PATH</td>
-<td>The path to the .exe file for the version of Chrome you are
-testing with. Example:
+<td>The path to the .exe file for the version of Chrome you
+are testing with.  For example:
 <code>C:\Users\fred\AppData\Local\Google\Chrome
 SxS\Application\chrome.exe</code></td>
 </tr>
@@ -545,4 +545,4 @@ than a Pepper plugin.</dd>
 </dl>
 </section></section></section></section>
 
-{{/partials.standard_nacl_article}}
+{{/partials.standard_nacl_api}}

native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html

@@ -74,7 +74,7 @@ one labeled <code>(stable)</code> by <code>naclsdk list</code>. See <a class="re
 Client SDK</em></a> for more details.
 </aside>
 <p>If no port number is specified, the server defaults to port 5103, and can be
-accessed at <a class="reference external" href="http://localhost:5103">http://localhost:5103</a>.</p>
+accessed at <code>http://localhost:5103</code>.</p>
 <p>Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.</p>
 </section><section id="step-3-set-up-the-chrome-browser">
@@ -138,7 +138,7 @@ building applications outside the NaCl SDK tree, you should set the
 Modules</em></a> for more details.</p>
 <p>Assuming the local server was started according to the instructions in
 <a class="reference internal" href="#tutorial-step-2"><em>Step 2</em></a>, you can now load the sample by pointing Chrome
-to <a class="reference external" href="http://localhost:5103/part1">http://localhost:5103/part1</a>. Chrome should load the Native Client module
+to <code>http://localhost:5103/part1</code>. Chrome should load the Native Client module
 successfully and the Status text should change from &#8220;LOADING...&#8221; to &#8220;SUCCESS&#8221;.
 If you run into problems, check out the <a class="reference internal" href="#tutorial-troubleshooting"><em>Troubleshooting section</em></a> below.</p>
 </section><section id="step-6-modify-the-javascript-code-to-send-a-message-to-the-native-client-module">
@@ -203,7 +203,7 @@ member functions.</p>
 </section><section id="step-8-compile-the-native-client-module-and-run-the-application-again">
 <h2 id="step-8-compile-the-native-client-module-and-run-the-application-again">Step 8: Compile the Native Client module and run the application again</h2>
 <p>Compile the Native Client module by running the <code>make</code> command again.</p>
-<p>Re-run the application by reloading <a class="reference external" href="http://localhost:5103/part1">http://localhost:5103/part1</a> in Chrome.</p>
+<p>Re-run the application by reloading <code>http://localhost:5103/part1</code> in Chrome.</p>
 <p>After Chrome loads the Native Client module, you should see an alert panel
 appear with the message sent from the module.</p>
 </section><section id="troubleshooting">

native_client_sdk/doc_generated/sdk/examples.html

@@ -163,7 +163,7 @@ $ make run
 </pre>
 <p>This will launch a local HTTP server which will serve the data for the
 example. It then launches Chrome with the address of this server, usually
-<a class="reference external" href="http://localhost:5103">http://localhost:5103</a>. After you close Chrome, the local HTTP server is
+<code>http://localhost:5103</code>. After you close Chrome, the local HTTP server is
 automatically shutdown.</p>
 <p>This command will try to find an executable named <code>google-chrome</code> in your
 <code>PATH</code> environment variable. If it can&#8217;t, you&#8217;ll get an error message like
@@ -236,7 +236,7 @@ console, type:</p>
 <pre class="prettyprint">
 (gdb) target remote :4014
 </pre>
-<p>This tells GDB to connect to a TCP port on localhost:4014&#8211;the port that
+<p>This tells GDB to connect to a TCP port on <code>localhost:4014</code>&#8211;the port that
 Chrome is listening on. GDB will respond:</p>
 <pre class="prettyprint">
 Remote debugging using :4014

native_client_sdk/src/doc/devguide/coding/progress-events.rst

 .. _devcycle-progress-events:
 
+:template: standard_nacl_api
+
 ###############
 Progress Events
 ###############

native_client_sdk/src/doc/devguide/coding/view-focus-input-events.rst

 .. _view_focus_input_events:
 
+:template: standard_nacl_api
+
 ####################################
 View Change, Focus, and Input Events
 ####################################

native_client_sdk/src/doc/devguide/devcycle/running.rst

 .. _devcycle-running:
 
+:template: standard_nacl_api
+
 #######
 Running
 #######
 
+
 .. contents::
   :local:
   :backlinks: none
@@ -206,7 +209,7 @@ server:
 By default, the server listens for requests on port 5103. You can use the server
 to run most applications under the ``examples`` directory where you started the
 server. For example, to run the ``flock`` example in the SDK, start the server
-and point your browser to http://localhost:5103/demo/flock/.
+and point your browser to ``http://localhost:5103/demo/flock/``.
 
 Some of the applications need special flags to Chrome, and must be run with the
 ``make run`` command. See :ref:`running_the_sdk_examples` for more details.

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

+:template: standard_nacl_api
+
 ############################
 Debugging With Visual Studio
 ############################
 
+
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
@@ -174,17 +177,20 @@ under ``User Accounts``.) Click on the link and use the buttons in the window
 to create or change these user variables (the values shown below are only for
 example):
 
-+---------------+--------------------------------------------------------------+
-| Variable Name | Description                                                  |
-+===============+==============================================================+
-| NACL_SDK_ROOT | The path to the pepper directory in the SDK. Example:        |
-|               | ``C:\nacl_sdk\pepper_23``                                    |
-+---------------+--------------------------------------------------------------+
-| CHROME_PATH   | The path to the .exe file for the version of Chrome you are  |
-|               | testing with. Example:                                       |
-|               | ``C:\Users\fred\AppData\Local\Google\Chrome                  |
-|               | SxS\Application\chrome.exe``                                 |
-+---------------+--------------------------------------------------------------+
+
++-------------------+----------------------------------------------------------+
+| Variable Name     | Description                                              |
++===================+==========================================================+
+| NACL_SDK_ROOT     | The path to the pepper directory in the SDK.             |
+|                   | For example: ``C:\nacl_sdk\pepper_23``                   |
++-------------------+----------------------------------------------------------+
+| CHROME_PATH       | The path to the .exe file for the version of Chrome you  |
+|                   | are testing with.  For example:                          |
+|                   | ``C:\Users\fred\AppData\Local\Google\Chrome              |
+|                   | SxS\Application\chrome.exe``                             |
++-------------------+----------------------------------------------------------+
+
+
 
 Download the add-in
 -------------------

native_client_sdk/src/doc/devguide/tutorial/tutorial-part1.rst

@@ -80,7 +80,7 @@ rule called ``serve`` is the easiest way to invoke it:
   Client SDK </sdk/download>` for more details.
 
 If no port number is specified, the server defaults to port 5103, and can be
-accessed at http://localhost:5103.
+accessed at ``http://localhost:5103``.
 
 Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.
@@ -165,7 +165,7 @@ Modules </devguide//devcycle/building>` for more details.
 
 Assuming the local server was started according to the instructions in
 :ref:`Step 2 <tutorial_step_2>`, you can now load the sample by pointing Chrome
-to http://localhost:5103/part1. Chrome should load the Native Client module
+to ``http://localhost:5103/part1``. Chrome should load the Native Client module
 successfully and the Status text should change from "LOADING..." to "SUCCESS".
 If you run into problems, check out the :ref:`Troubleshooting section
 <tutorial_troubleshooting>` below.
@@ -248,7 +248,7 @@ Step 8: Compile the Native Client module and run the application again
 
 Compile the Native Client module by running the ``make`` command again.
 
-Re-run the application by reloading http://localhost:5103/part1 in Chrome.
+Re-run the application by reloading ``http://localhost:5103/part1`` in Chrome.
 
 After Chrome loads the Native Client module, you should see an alert panel
 appear with the message sent from the module.

native_client_sdk/src/doc/sdk/examples.rst

@@ -168,7 +168,7 @@ To run the SDK examples, you can use the ``make run`` command::
 
 This will launch a local HTTP server which will serve the data for the
 example. It then launches Chrome with the address of this server, usually
-http://localhost:5103. After you close Chrome, the local HTTP server is
+``http://localhost:5103``. After you close Chrome, the local HTTP server is
 automatically shutdown.
 
 This command will try to find an executable named ``google-chrome`` in your
@@ -250,7 +250,7 @@ console, type::
 
   (gdb) target remote :4014
 
-This tells GDB to connect to a TCP port on localhost:4014--the port that
+This tells GDB to connect to a TCP port on ``localhost:4014``--the port that
 Chrome is listening on. GDB will respond::
 
   Remote debugging using :4014