[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/src/doc/nacl-and-pnacl.rst

Index: native_client_sdk/src/doc/nacl-and-pnacl.rst
diff --git a/native_client_sdk/src/doc/nacl-and-pnacl.rst b/native_client_sdk/src/doc/nacl-and-pnacl.rst
index b83f0a5c464b881c5c630a94318779be7e466958..d305c223ddfcb4b63add8c8a19030929fe994cab 100644
--- a/native_client_sdk/src/doc/nacl-and-pnacl.rst
+++ b/native_client_sdk/src/doc/nacl-and-pnacl.rst
@@ -81,11 +81,11 @@ Native Client modules without the Google Web Store. Unless your project is
 subject to one of the narrow limitations described under ":ref:`When to use
 NaCl<when-to-use-nacl>`", you should use PNaCl.
 
-Since version 31, Chrome supports translation of pexe 
-modules and their use in web applications without requiring installation either
-of a browser plug-in or of the applications themselves. Native Client and PNaCl
-are open-source technologies, and our hope is that they will be added to other
-hosting platforms in the future.
+Chrome supports translation of pexe  modules and their use in web applications

[Sam Clegg, 2014/10/08 17:38:01]

extra space?

[jpmedley, 2014/11/05 03:56:11]

Done.

+without requiring installation either of a browser plug-in or of the
+applications themselves. Native Client and PNaCl are open-source technologies,
+and our hope is that they will be added to other hosting platforms in the
+future.
 
 If controlled distribution through the Chrome Web Store is an important part of
 your product plan, the benefits of PNaCl are less critical for you. But you can