More fixes to overview.rst

native_client_sdk/src/doc/overview.rst

 .. _overview:
 
 ##################
 Technical Overview
 ##################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 67 matching lines @@
   application---you don't need to spend time reinventing and debugging code
   that's already proven to work well.
 * **Legacy desktop applications:** Native Client provides a smooth migration
   path from desktop applications to the web. You can port and recompile existing
   code for the computation engine of your application directly to Native Client,
   and need repurpose only the user interface and event handling portions to the
   new browser platform. Native Client allows you to embed existing functionality
   directly into the browser. At the same time, your application takes advantage
   of things the browser does well: handling user interaction and processing
   events, based on the latest developments in HTML5.
-* **Enterprise applications that require heavy computation:** Native Client
-  handles the number crunching required by large-scale enterprise applications.
-  To ensure protection of user data, Native Client enables you to build complex
+* **Heavy computation in enterprise applications:** Native Client handles the
+  number crunching required by large-scale enterprise applications. To ensure
+  protection of user data, Native Client enables you to build complex
   cryptographic algorithms directly into the browser so that unencrypted data
   never goes out over the network.
 * **Multimedia applications:** Codecs for processing sounds, images, and movies
   can be added to the browser in a Native Client module.
 * **Games:** Native Client enables a web application to run close to native
   speed, reusing existing multithreaded/multicore C/C++ code bases, combined
   with low-level access to low-latency audio, networking APIs and OpenGL ES with
   programmable shaders. Programming to Native Client also enables your binary to
   run unchanged across many platforms. Native Client is a natural fit for
   running a physics engine or artificial intelligence module that powers a
@@ skipping 56 matching lines @@
 within the Native Client sandbox as described above. It also uses intelligent
 caching to avoid re-compiling the **pexe** if it was already compiled on the
 client's browser.
 
 Native Client also supports running a **nexe** directly in the browser. However,
 since a **nexe** contains architecture-specific machine code, distributing
 **nexe** modules on the open web is not allowed. **nexe** modules can only be
 used as part of applications that are installed from the Chrome Web Store and in
 browser extensions.
 
+For more details, see :doc:`NaCl and PNaCl <nacl-and-pnacl>`.
+
 Toolchains
 ----------
 
 A *toolchain* is a set of tools used to create an application from a set of
 source files. In the case of Native Client, a toolchain consists of a compiler,
 linker, assembler and other tools that are used by the developer to convert an
 application written in C/C++ into a module loadable by the browser.
 
 The Native Client SDK provides two toolchains:
 
@@ skipping 68 matching lines @@
 help developers make adjustments to API changes and take advantage of new
 features.
 
 Where to go next
 ================
 
 The :doc:`quick start <quick-start>` document provides links to downloads and
 documentation that should help you get started with developing and distributing
 NaCl applications.