Move 'Versioning' topic from overview to download page.

BUG=none
R= mkearney@chromium.org, smain@chromium.org
TEST=none
NOTRY=true
(documentation only change)

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

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

native_client_sdk/doc_generated/overview.html

@@ -4,23 +4,22 @@
 <span id="overview"></span><h1 id="technical-overview"><span id="overview"></span>Technical Overview</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
-<li><a class="reference internal" href="#why-use-native-client" id="id9">Why use Native Client?</a></li>
-<li><a class="reference internal" href="#benefits-of-native-client" id="id10">Benefits of Native Client</a></li>
-<li><a class="reference internal" href="#common-use-cases" id="id11">Common use cases</a></li>
-<li><p class="first"><a class="reference internal" href="#how-native-client-works" id="id12">How Native Client works</a></p>
+<li><a class="reference internal" href="#why-use-native-client" id="id7">Why use Native Client?</a></li>
+<li><a class="reference internal" href="#benefits-of-native-client" id="id8">Benefits of Native Client</a></li>
+<li><a class="reference internal" href="#common-use-cases" id="id9">Common use cases</a></li>
+<li><p class="first"><a class="reference internal" href="#how-native-client-works" id="id10">How Native Client works</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#toolchains" id="id13">Toolchains</a></li>
-<li><a class="reference internal" href="#security" id="id14">Security</a></li>
-<li><a class="reference internal" href="#portability" id="id15">Portability</a></li>
+<li><a class="reference internal" href="#toolchains" id="id11">Toolchains</a></li>
+<li><a class="reference internal" href="#security" id="id12">Security</a></li>
+<li><a class="reference internal" href="#portability" id="id13">Portability</a></li>
 </ul>
 </li>
-<li><p class="first"><a class="reference internal" href="#structure-of-a-web-application" id="id16">Structure of a web application</a></p>
+<li><p class="first"><a class="reference internal" href="#structure-of-a-web-application" id="id14">Structure of a web application</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#pepper-plug-in-api" id="id17">Pepper plug-in API</a></li>
+<li><a class="reference internal" href="#pepper-plug-in-api" id="id15">Pepper plug-in API</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#versioning" id="id18">Versioning</a></li>
-<li><a class="reference internal" href="#where-to-start" id="id19">Where to start</a></li>
+<li><a class="reference internal" href="#where-to-start" id="id16">Where to start</a></li>
 </ul>
 
 </div><p><strong>Native Client</strong> (NaCl) is an open-source technology for running native
@@ -229,16 +228,7 @@ capabilities, including:</p>
 <p>Pepper includes both a <a class="reference internal" href="/native-client/c-api.html"><em>C API</em></a> and a <a class="reference internal" href="/native-client/cpp-api.html"><em>C++ API</em></a>.
 The C++ API is a set of bindings written on top of the C API. For additional
 information about Pepper, see <a class="reference external" href="http://code.google.com/p/ppapi/wiki/Concepts">Pepper Concepts</a>.</p>
-<h2 id="versioning"><span id="id7"></span>Versioning</h2>
-<p>Chrome is released on a six week cycle, and developer versions of Chrome are
-pushed to the public beta channel three weeks before each release. As with any
-software, each release of Chrome may include changes to Native Client and the
-Pepper interfaces that may require modification to existing applications.
-However, modules compiled for one version of Pepper/Chrome should work with
-subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
-Pepper APIs to help you make adjustments to API changes and take
-advantage of new features: <a class="reference external" href="/native-client/pepper_stable">stable</a>, <a class="reference external" href="/native-client/pepper_beta">beta</a> and <a class="reference external" href="/native-client/pepper_dev">dev</a>.</p>
-<h2 id="where-to-start"><span id="id8"></span>Where to start</h2>
+<h2 id="where-to-start">Where to start</h2>
 <p>The <a class="reference internal" href="/native-client/quick-start.html"><em>Quick Start</em></a> document provides links to downloads and
 documentation to help you get started with developing and distributing Native
 Client applications.</p>

native_client_sdk/doc_generated/sdk/download.html

@@ -47,8 +47,17 @@ not install Xcode, you can download and build an <a class="reference external" h
 To build the program you may also need to download and install <a class="reference external" href="https://github.com/kennethreitz/osx-gcc-installer">gcc</a>.</li>
 <li>On Windows, the Native Client SDK includes a copy of GNU Make.</li>
 </ul>
-<h2 id="installing-the-sdk"><span id="id3"></span>Installing the SDK</h2>
-<h3 id="downloading-and-unzipping"><span id="id4"></span>Downloading and Unzipping</h3>
+<h2 id="versioning"><span id="id3"></span>Versioning</h2>
+<p>Chrome is released on a six week cycle, and developer versions of Chrome are
+pushed to the public beta channel three weeks before each release. As with any
+software, each release of Chrome may include changes to Native Client and the
+Pepper interfaces that may require modification to existing applications.
+However, modules compiled for one version of Pepper/Chrome should work with
+subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
+Pepper APIs to help developers make adjustments to API changes and take
+advantage of new features: <a class="reference external" href="/native-client/pepper_stable">stable</a>, <a class="reference external" href="/native-client/pepper_beta">beta</a> and <a class="reference external" href="/native-client/pepper_dev">dev</a>.</p>
+<h2 id="installing-the-sdk"><span id="id4"></span>Installing the SDK</h2>
+<h3 id="downloading-and-unzipping"><span id="id5"></span>Downloading and Unzipping</h3>
 <ol class="arabic">
 <li><p class="first">Download the <a class="reference external" href="http://storage.googleapis.com/nativeclient-mirror/nacl/nacl_sdk/nacl_sdk.zip">SDK update zip file</a>.</p>
 </li>
@@ -75,7 +84,7 @@ you have already downloaded.</p>
 </ul>
 </li>
 </ol>
-<h3 id="installing-the-stable-bundle"><span id="id5"></span>Installing the stable bundle</h3>
+<h3 id="installing-the-stable-bundle"><span id="id6"></span>Installing the stable bundle</h3>
 <ol class="arabic">
 <li><p class="first">To see the SDK bundles that are available for download, go to the
 <code>nacl_sdk</code> directory and run <code>naclsdk</code> with the <code>list</code> command. The SDK
@@ -139,7 +148,7 @@ $ ./naclsdk update pepper_36
 </pre>
 </li>
 </ol>
-<h2 id="updating-bundles"><span id="id6"></span>Updating bundles</h2>
+<h2 id="updating-bundles"><span id="id7"></span>Updating bundles</h2>
 <ol class="arabic">
 <li><p class="first">Run <code>naclsdk</code> with the <code>list</code> command. This shows you the list of available
 bundles and verifies which bundles you have installed.</p>
@@ -189,7 +198,7 @@ $ ./naclsdk update --force
 </pre>
 </li>
 </ol>
-<h2 id="help-with-the-naclsdk-utility"><span id="id7"></span>Help with the <code>naclsdk</code> utility</h2>
+<h2 id="help-with-the-naclsdk-utility"><span id="id8"></span>Help with the <code>naclsdk</code> utility</h2>
 <ol class="arabic">
 <li><p class="first">For more information about the <code>naclsdk</code> utility, run:</p>
 <p>On Mac/Linux:</p>
@@ -202,7 +211,7 @@ $ ./naclsdk help
 </pre>
 </li>
 </ol>
-<h2 id="next-steps"><span id="id8"></span>Next steps</h2>
+<h2 id="next-steps"><span id="id9"></span>Next steps</h2>
 <ul class="small-gap">
 <li>Browse the <a class="reference external" href="release-notes">Release Notes</a> for important
 information about the SDK and new bundles.</li>

native_client_sdk/doc_generated/sitemap.html

@@ -11,7 +11,6 @@
 <li class="toctree-l2"><a class="reference internal" href="/native-client/overview.html#common-use-cases">Common use cases</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/overview.html#how-native-client-works">How Native Client works</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/overview.html#structure-of-a-web-application">Structure of a web application</a></li>
-<li class="toctree-l2"><a class="reference internal" href="/native-client/overview.html#versioning">Versioning</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/overview.html#where-to-start">Where to start</a></li>
 </ul>
 </li>
@@ -27,6 +26,7 @@
 <li class="toctree-l1"><a class="reference internal" href="/native-client/sdk/download.html">Download the Native Client SDK</a><ul class="small-gap">
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#overview">Overview</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#prerequisites">Prerequisites</a></li>
+<li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#versioning">Versioning</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#installing-the-sdk">Installing the SDK</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#updating-bundles">Updating bundles</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/download.html#help-with-the-naclsdk-utility">Help with the <code>naclsdk</code> utility</a></li>

native_client_sdk/src/doc/overview.rst

@@ -280,23 +280,6 @@ The C++ API is a set of bindings written on top of the C API. For additional
 information about Pepper, see `Pepper Concepts 
 <http://code.google.com/p/ppapi/wiki/Concepts>`_.
 
-.. _versioning:
-
-Versioning
-==========
-
-Chrome is released on a six week cycle, and developer versions of Chrome are
-pushed to the public beta channel three weeks before each release. As with any
-software, each release of Chrome may include changes to Native Client and the
-Pepper interfaces that may require modification to existing applications.
-However, modules compiled for one version of Pepper/Chrome should work with
-subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
-Pepper APIs to help you make adjustments to API changes and take
-advantage of new features: `stable </native-client/pepper_stable>`_, `beta
-</native-client/pepper_beta>`_ and `dev </native-client/pepper_dev>`_.
-
-.. _where-to-start:
-
 Where to start
 ==============
 

native_client_sdk/src/doc/sdk/download.rst

@@ -73,6 +73,21 @@ Make
   <https://github.com/kennethreitz/osx-gcc-installer>`_.
 * On Windows, the Native Client SDK includes a copy of GNU Make.
 
+.. _versioning:
+
+Versioning
+----------
+
+Chrome is released on a six week cycle, and developer versions of Chrome are
+pushed to the public beta channel three weeks before each release. As with any
+software, each release of Chrome may include changes to Native Client and the
+Pepper interfaces that may require modification to existing applications.
+However, modules compiled for one version of Pepper/Chrome should work with
+subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
+Pepper APIs to help developers make adjustments to API changes and take
+advantage of new features: `stable </native-client/pepper_stable>`_, `beta
+</native-client/pepper_beta>`_ and `dev </native-client/pepper_dev>`_.
+
 .. _installing-the-sdk:
 
 Installing the SDK