Move 'Versioning' topic from overview to download page.

native_client_sdk/src/doc/overview.rst

Index: native_client_sdk/src/doc/overview.rst
diff --git a/native_client_sdk/src/doc/overview.rst b/native_client_sdk/src/doc/overview.rst
index a98c491550163e00d2c839d154ded01a1b0c4954..c6bc9933144f2d96ae6fecf1bb089cc67d53892c 100644
--- a/native_client_sdk/src/doc/overview.rst
+++ b/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
 ==============