Move 'Versioning' topic from overview to download page.

native_client_sdk/doc_generated/overview.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="technical-overview">
 <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
 compiled code in the browser, with the goal of maintaining the portability
 and safety that users expect from web applications. Native Client expands web
 programming beyond JavaScript, enabling you to enhance your web applications
 using your preferred language. This document describes some of the key benefits
 and common use cases of Native Client.</p>
 <p>Google has implemented the open-source <a class="reference external" href="http://www.chromium.org/nativeclient">Native Client project</a> in the Chrome browser on Windows, Mac,
 Linux, and Chrome OS. The <a class="reference internal" href="/native-client/sdk/download.html"><em>Native Client Software Development Kit (SDK)</em></a>, itself an open-source project, lets you create web applications
@@ skipping 188 matching lines @@
 capabilities, including:</p>
 <ul class="small-gap">
 <li><a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Talking to the JavaScript code in your application</em></a> from the C++ code in your NaCl module.</li>
 <li><a class="reference internal" href="/native-client/devguide/coding/file-io.html"><em>Doing file I/O</em></a>.</li>
 <li><a class="reference internal" href="/native-client/devguide/coding/audio.html"><em>Playing audio</em></a>.</li>
 <li><a class="reference internal" href="/native-client/devguide/coding/3D-graphics.html"><em>Rendering 3D graphics</em></a>.</li>
 </ul>
 <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>
 </section>
 
 {{/partials.standard_nacl_article}}