Rearrange tables so that navigation can be added back to certain pages.

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

 .. _devcycle-running:
 
-:template: standard_nacl_api
-
 #######
 Running
 #######
 
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
@@ skipping 45 matching lines @@
   application, including all application assets and metadata, to the CWS.
 
 It's clearly not convenient to package and upload files to the Chrome Web Store
 every time you want to run a new build of your application, but there are four
 alternative techniques you can use to run the application during development.
 These techniques are listed in the following table and described in detail
 below. Each technique has certain requirements (NaCl flag, web server, and/or
 CWS metadata); these are explained in the :ref:`Requirements <requirements>`
 section below.
 
-.. list-table::
-   :header-rows: 1
 
-   * - #
-     - Technique
-     - Requires NaCl flag
-     - Requires Web Server
-     - Requires CWS Metadata
-     - Description
-   * - 1
-     - Local server
-     - |CHK|
-     - |CHK|
-     -
-     - Run a local server and simply point your browser to your application on
-       the server.
-   * - 2
-     - Packaged application loaded as an unpacked extension
-     -
-     -
-     - |CHK|
-     - Load your packaged application into Chrome as an unpacked extension and
-       run it without a server. An unpacked extension is simply an application
-       whose source and metadata files are located in a plain (unzipped) folder
-       on your development machine. The CWS manifest file (explained below) must
-       specify a ``local_path`` field.
-   * - 3
-     - Hosted application loaded as an unpacked extension
-     -
-     - |CHK|
-     - |CHK|
-     - Load your hosted application into Chrome as an unpacked extension and run
-       it from a server (which can be a local server). The CWS manifest file
-       must specify a ``web_url`` field.
-   * - 4
-     - CWS application with untrusted testers
-     -
-     -
-     - |CHK|
-     - This is the standard technique for distributing a packaged or hosted
-       application in the CWS, but you can limit the application to a few
-       trusted testers. This technique requires a server if your application is
-       a hosted application.
++--------------------------------------------------------+----------+----------+
+| Technique                                              | Requires | Requires |
+|                                                        | Web      | CWS      |
+|                                                        | Server   | Metadata |
++========================================================+==========+==========+
+|**1. Local server**                                     | |CHK|    |          |
+|                                                        |          |          |
+| ..                                                     |          |          |
+|                                                        |          |          |
+|  Run a local server and simply point your browser to   |          |          |
+|  your application on the server.                       |          |          |
+|                                                        |          |          |
+|  .. Note::                                             |          |          |
+|    :class: note                                        |          |          |
+|                                                        |          |          |
+|    This technique requires the NaCl flag.              |          |          |
++---------------------------------------------+----------+----------+----------+
+|**2. Packaged application loaded as an unpacked         |          | |CHK|    |
+|extension**                                             |          |          |
+|                                                        |          |          |
+| ..                                                     |          |          |
+|                                                        |          |          |
+|  Load your packaged application into Chrome as an      |          |          |
+|  unpacked extension and run it without a server. An    |          |          |
+|  unpacked extension is an application whose source and |          |          |
+|  metadata files are located in an unzipped folder on   |          |          |
+|  your development machine. The CWS manifest file       |          |          |
+|  (explained below) must specify a local_path field.    |          |          |
++--------------------------------------------------------+----------+----------+
+|**3. Hosted application loaded as an unpacked           | |CHK|    | |CHK|    |
+|extension**                                             |          |          |
+|                                                        |          |          |
+| ..                                                     |          |          |
+|                                                        |          |          |
+|  Load your hosted application into Chrome as an        |          |          |
+|  unpacked extension and run it from a server (which can|          |          |
+|  be a local server). The CWS manifest file must specify|          |          |
+|  a web_url field.                                      |          |          |
++--------------------------------------------------------+----------+----------+
+|**4. CWS application with untrusted testers**           |          | |CHK|    |
+|                                                        |          |          |
+| ..                                                     |          |          |
+|                                                        |          |          |
+|  The standard technique for distributing a packaged or |          |          |
+|  hosted application in the CWS. You can limit the      |          |          |
+|  application to trusted testers. This technique        |          |          |
+|  requires a server if your application is a hosted     |          |          |
+|  application.                                          |          |          |
++--------------------------------------------------------+----------+----------+
+
 
 .. |CHK| image:: /images/check-red.png
 
 Which of the above techniques you use to run your application during development
 is largely a matter of personal preference (i.e., would you rather start a local
 server or create CWS metadata?). As a general rule, once you have an idea of how
 you plan to distribute your application, you should use the corresponding
 technique during development. Choosing a distribution option depends on a number
 of factors such as application size, application start-up time, hosting costs,
 offline functionality, etc. (see :doc:`Distributing Your Application
@@ skipping 342 matching lines @@
      be able to find the application by searching in the CWS.
 
 To publish an application to the world after publishing it to test accounts,
 you must first unpublish the application. For additional information see
 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing
 to test accounts </webstore/publish#testaccounts>`_.
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |extensions| image:: /images/extensions-management.png
 .. |new-tab-apps| image:: /images/new-tab-apps.png