Per P0 reqs add launch pts + make download obvious. Also misc cpy edits.

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="#introduction" id="id2">Introduction</a></li>
 <li><a class="reference internal" href="#why-use-native-client" id="id3">Why use Native Client?</a></li>
 <li><a class="reference internal" href="#common-use-cases" id="id4">Common use cases</a></li>
 <li><p class="first"><a class="reference internal" href="#how-native-client-works" id="id5">How Native Client works</a></p>
@@ skipping 24 matching lines @@
 applications that use NaCl and run in Chrome across multiple platforms.</p>
 <p>A web application that uses Native Client generally consists of a combination of
 JavaScript, HTML, CSS, and a NaCl module that is written in a language supported
 by the SDK. The NaCl SDK currently supports C and C++; as compilers for
 additional languages are developed, the SDK will be updated to support those
 languages as well.</p>
 <img alt="/native-client/images/web-app-with-nacl.png" src="/native-client/images/web-app-with-nacl.png" />
 <h2 id="why-use-native-client">Why use Native Client?</h2>
 <p>Native Client open-source technology is designed to run compiled code
 securely inside a browser at near-native speeds. Native Client puts web
-applications on the same playing field as traditional (locally-run)
-software&#8212;it provides the means to fully harness the client&#8217;s computational
-resources for applications such as 3D games, multimedia editors, CAD modeling,
+applications on the same playing field as desktop software&#8212;it provides the
+means to fully harness the client&#8217;s computational resources for applications
+such as 3D games, multimedia editors, CAD modeling,
 client-side data analytics, and interactive simulations.
 Native Client also aims to give C and C++ (and eventually other languages) the
 same level of portability and safety that JavaScript provides on the web today.</p>
-<p>Here are a few of the key benefits that Native Client offers:</p>
+<p>Important benefits of Native Client include:</p>
 <ul class="small-gap">
-<li><strong>Graphics, audio, and much more:</strong> Run native code modules that render 2D
+<li><strong>Graphics, audio, and much more:</strong> Running native code modules that render 2D
 and 3D graphics, play audio, respond to mouse and keyboard events, run on
 multiple threads, and access memory directly&#8212;all without requiring
 the user to install a plugin.</li>
-<li><strong>Portability:</strong> Write your applications once and you&#8217;ll be able to run them
-across operating systems (Windows, Linux, Mac, and Chrome OS) and CPU
-architectures (x86 and ARM).</li>
-<li><strong>Easy migration path to the web:</strong> Many developers and companies have years
-of work invested in existing desktop applications. Native Client makes the
-transition from the desktop to a web application significantly easier because
-it supports C and C++.</li>
-<li><strong>Security:</strong> Native Client uses a double sandbox model designed to protect
-the user&#8217;s system from malicious or buggy applications. This model offers the
-safety of traditional web applications without sacrificing performance and
+<li><strong>Portability:</strong> Writing your applications once and running them on operating
+systems (Windows, Linux, Mac, and Chrome OS) and CPU architectures (x86 and
+ARM).</li>
+<li><strong>Easy migration path to the web:</strong> Leveraging years of work in existing
+desktop applications. Native Client makes the transition from the desktop to a
+web application significantly easier because it supports C and C++.</li>
+<li><strong>Security:</strong> Protecting the user&#8217;s system from malicious or buggy
+applications through Native Client&#8217;s double sandbox model. This model offers
+the safety of traditional web applications without sacrificing performance and
 without requiring users to install a plugin.</li>
-<li><strong>Performance:</strong> Native Client allows web applications to run at speeds
-comparable to desktop applications (within 5-15% of native speed).
-Native Client also allows applications to harness all available CPU cores via
-a threading API; this enables demanding applications such as console-quality
-games to run inside the browser.</li>
+<li><strong>Performance:</strong> Running at speeds comparable to desktop applications (within
+5-15% of native speed). Native Client also allows applications to harness all
+available CPU cores via a threading API; this enables demanding applications
+such as console-quality games to run inside the browser.</li>
 </ul>
 <h2 id="common-use-cases">Common use cases</h2>
 <p>Typical use cases for Native Client include the following:</p>
 <ul class="small-gap">
 <li><strong>Existing software components:</strong> With support for C and C++, Native
-Client enables you to reuse existing software modules in
-web applications&#8212;you don&#8217;t need to rewrite and debug code
-that&#8217;s already proven to work well.</li>
+Client lets you to reuse existing software modules in web applications. You
+don&#8217;t need to rewrite and debug code that already works.</li>
 <li><strong>Legacy desktop applications:</strong> 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 can take
-advantage of things the browser does well: handling user interaction and
-processing events, based on the latest developments in HTML5.</li>
+and need rebuild only the user interface and event handling portions for the
+browser.</li>
 <li><strong>Heavy computation in enterprise applications:</strong> Native Client can handle 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.</li>
 <li><strong>Multimedia applications:</strong> Codecs for processing sounds, images, and movies
 can be added to the browser in a Native Client module.</li>
 <li><strong>Games:</strong> Native Client lets web applications run at close to native
 speed, reuse existing multithreaded/multicore C/C++ code bases, and
 access low-latency audio, networking APIs, and OpenGL ES with programmable
 shaders. Native Client is a natural fit for running a physics engine or
 artificial intelligence module that powers a sophisticated web game.
 Native Client also enables applications to run unchanged across
 many platforms.</li>
 <li><strong>Any application that requires acceleration</strong>: Native Client fits seamlessly
 into web applications&#8212;it&#8217;s up to you to decide to what extent to use it.
 Use of Native Client covers the full spectrum from complete applications to
-small optimized routines that accelerate vital parts of web apps.</li>
+small optimized routines that accelerate vital parts of web applications.</li>
 </ul>
 <h2 id="how-native-client-works"><span id="link-how-nacl-works"></span>How Native Client works</h2>
-<p>Native Client is an umbrella name for a set of interrelated software components
-that work together to provide a way to develop C/C++ applications and run them
-securely on the web.</p>
+<p>Native Client is an umbrella name for a set of related software components that
+provide a way to develop C/C++ applications and run them securely on the web.</p>
 <p>At a high level, Native Client consists of:</p>
 <ul class="small-gap">
-<li><strong>Toolchains</strong>: collections of development tools (compilers, linkers, etc.)
+<li><strong>Toolchains</strong>: Collections of development tools (compilers, linkers, etc.)
 that transform C/C++ code to Native Client modules.</li>
 <li><strong>Runtime components</strong>: components embedded in the browser or other
 host platforms that allow execution of  Native Client modules
 securely and efficiently.</li>
 </ul>
 <p>The following diagram shows how these components interact:</p>
 <img alt="/native-client/images/nacl-pnacl-component-diagram.png" src="/native-client/images/nacl-pnacl-component-diagram.png" />
 <p>The left side of the diagram shows how to use Portable Native Client
 (PNaCl, pronounced &#8220;pinnacle&#8221;). Developers use the PNaCl toolchain
 to produce a single, portable (<strong>pexe</strong>) module. At runtime, a translator
 built into the browser translates the pexe into native code for the
-relevant client architecture.</p>
-<p>The right side of the diagram shows how to use traditional (non-portable)
-Native Client. Developers use a nacl-gcc based toolchain to produce multiple
+relevant client architecture. Translation occurs before any code is executed.</p>
+<p>The right side of the diagram shows how to use (non-portable) Native Client.
+Developers use a nacl-gcc based toolchain to produce multiple
 architecture-dependent (<strong>nexe</strong>) modules, which are packaged into an
 application. At runtime, the browser decides which nexe to load based
 on the architecture of the client machine.</p>
 <h3 id="security">Security</h3>
 <p>Since Native Client permits the execution of native code on client machines,
 special security measures have to be implemented:</p>
 <ul class="small-gap">
 <li>The NaCl sandbox ensures that code accesses system resources only through
 safe, whitelisted APIs, and operates within its limits without attempting to
 interfere with other code running either within the browser or outside it.</li>
@@ skipping 81 matching lines @@
 subsequent versions of Pepper/Chrome. The SDK includes multiple versions of the
 Pepper APIs to help developers 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">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 that should help you get started with developing and distributing
 Native Client applications.</p>
 </section>
 
 {{/partials.standard_nacl_article}}