Move 'Versioning' topic from overview to download page.

native_client_sdk/src/doc/overview.rst

 .. _overview:
 
 ##################
 Technical Overview
 ##################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 262 matching lines @@
   <devguide/coding/message-system>` from the C++ code in your NaCl module.
 * :doc:`Doing file I/O <devguide/coding/file-io>`.
 * :doc:`Playing audio <devguide/coding/audio>`.
 * :doc:`Rendering 3D graphics <devguide/coding/3D-graphics>`.
 
 Pepper includes both a :doc:`C API </c-api>` and a :doc:`C++ API </cpp-api>`.
 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
 ==============
 
 The :doc:`Quick Start <quick-start>` document provides links to downloads and
 documentation to help you get started with developing and distributing Native
 Client applications.