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

native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="c-tutorial-getting-started-part-1">
 <span id="tutorial"></span><h1 id="c-tutorial-getting-started-part-1"><span id="tutorial"></span>C++ Tutorial: Getting Started (Part 1)</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#overview" id="id1">Overview</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#what-the-application-in-this-tutorial-does" id="id2">What the application in this tutorial does</a></li>
 <li><a class="reference internal" href="#communication-between-javascript-and-native-client-modules" id="id3">Communication between JavaScript and Native Client modules</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#step-1-download-and-install-the-native-client-sdk" id="id4">Step 1: Download and install the Native Client SDK</a></li>
 <li><a class="reference internal" href="#step-2-start-a-local-server" id="id5">Step 2: Start a local server</a></li>
 <li><a class="reference internal" href="#step-3-set-up-the-chrome-browser" id="id6">Step 3: Set up the Chrome browser</a></li>
 <li><a class="reference internal" href="#step-4-stub-code-for-the-tutorial" id="id7">Step 4: Stub code for the tutorial</a></li>
 <li><a class="reference internal" href="#step-5-compile-the-native-client-module-and-run-the-stub-application" id="id8">Step 5: Compile the Native Client module and run the stub application</a></li>
 <li><a class="reference internal" href="#step-6-modify-the-javascript-code-to-send-a-message-to-the-native-client-module" id="id9">Step 6: Modify the JavaScript code to send a message to the Native Client module</a></li>
 <li><a class="reference internal" href="#step-7-implement-a-message-handler-in-the-native-client-module" id="id10">Step 7: Implement a message handler in the Native Client module</a></li>
 <li><a class="reference internal" href="#step-8-compile-the-native-client-module-and-run-the-application-again" id="id11">Step 8: Compile the Native Client module and run the application again</a></li>
 <li><a class="reference internal" href="#troubleshooting" id="id12">Troubleshooting</a></li>
 <li><a class="reference internal" href="#next-steps" id="id13">Next steps</a></li>
 </ul>
 
 </div><h2 id="overview">Overview</h2>
 <p>This tutorial shows how to build and run a web application using Portable Native
 Client (PNaCl). This is a client-side application that uses HTML, JavaScript and
 a Native Client module written in C++. The PNaCl toolchain is used to enable
 running the Native Client module directly from a web page.</p>
-<p>It&#8217;s recommended to read the <a class="reference internal" href="/native-client/overview.html"><em>Native Client Technical Overview</em></a> prior to going through this tutorial.</p>
+<p>It&#8217;s recommended that you read the <a class="reference internal" href="/native-client/overview.html"><em>Native Client Technical Overview</em></a> prior to going through this tutorial.</p>
 <h3 id="what-the-application-in-this-tutorial-does">What the application in this tutorial does</h3>
 <p>The application in this tutorial shows how to load a Native Client module in a
-web page, and how to send messages between JavaScript and the C++ code in the
-Native Client module. In this simple application, the JavaScript code in the web
-page sends a <code>'hello'</code> message to the Native Client module. When the Native
-Client module receives a message, it checks whether the message is equal to the
-string <code>'hello'</code>. If it is, the Native Client module returns a message saying
-<code>'hello from NaCl'</code>. A JavaScript alert panel displays the message received
-from the Native Client module.</p>
+web page, and how to send messages between JavaScript and the Native Client
+module. In this simple application, the JavaScript sends a <code>'hello'</code> message
+to the Native Client module. When the Native Client module receives a message,
+it checks whether the message is equal to the string <code>'hello'</code>. If it is, the
+Native Client module returns a message saying <code>'hello from NaCl'</code>. A
+JavaScript alert panel displays the message received from the Native Client
+module.</p>
 <h3 id="communication-between-javascript-and-native-client-modules">Communication between JavaScript and Native Client modules</h3>
 <p>The Native Client programming model supports bidirectional communication between
-JavaScript and the Native Client module (C/C++ code). Both sides can initiate
+JavaScript and the Native Client module. Both sides can initiate
 and respond to messages. In all cases, the communication is asynchronous: The
 caller (JavaScript or the Native Client module) sends a message, but the caller
 does not wait for, or may not even expect, a response. This behavior is
 analogous to client/server communication on the web, where the client posts a
 message to the server and returns immediately. The Native Client messaging
 system is part of the Pepper API, and is described in detail in
 <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Developer&#8217;s Guide: Messaging System</em></a>.
 It is also similar to the way <a class="reference external" href="http://en.wikipedia.org/wiki/Web_worker">web workers</a> interact with the main document in
 JavaScript.</p>
 <h2 id="step-1-download-and-install-the-native-client-sdk">Step 1: Download and install the Native Client SDK</h2>
 <p>Follow the instructions on the <a class="reference internal" href="/native-client/sdk/download.html"><em>Download</em></a> page to
 download and install the Native Client SDK.</p>
 <h2 id="step-2-start-a-local-server"><span id="tutorial-step-2"></span>Step 2: Start a local server</h2>
 <p>To simulate a production environment, the SDK provides a simple web server that
 can be used to serve the application on <code>localhost</code>. A convenience Makefile
 rule called <code>serve</code> is the easiest way to invoke it:</p>
 <pre>
 $ cd pepper_$(VERSION)/getting_started
 $ make serve
 </pre>
 <aside class="note">
 The SDK may consist of several &#8220;bundles&#8221;, one per Chrome/Pepper version (see
 <a class="reference internal" href="/native-client/version.html"><em>versioning information</em></a>). In the sample invocation above
 <code>pepper_$(VERSION)</code> refers to the specific version you want to use. For
 example, <code>pepper_31</code>. If you don&#8217;t know which version you need, use the
-one labeled <code>(stable)</code> by <code>naclsdk list</code>. See <a class="reference internal" href="/native-client/sdk/download.html"><em>Download the Native
-Client SDK</em></a> for more details.
+one labeled <code>(stable)</code> by the <code>naclsdk list</code> command. See
+<a class="reference internal" href="/native-client/sdk/download.html"><em>Download the Native Client SDK</em></a> for more details.
 </aside>
 <p>If no port number is specified, the server defaults to port 5103, and can be
 accessed at <code>http://localhost:5103</code>.</p>
 <p>Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.</p>
 <h2 id="step-3-set-up-the-chrome-browser"><span id="tutorial-step-3"></span>Step 3: Set up the Chrome browser</h2>
 <p>PNaCl is enabled by default in Chrome version 31 and later. Please make sure
 that you have a suitable version to work through this tutorial. It&#8217;s also
 important to use a Chrome version that&#8217;s the same or newer than the SDK bundle
 used to build the Native Client modules.</p>
@@ skipping 127 matching lines @@
 possibility that the Native Client module has a bug; <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>debugging</em></a> may be required.</p>
 <p>There&#8217;s more information about troubleshooting in the documentation:</p>
 <ul class="small-gap">
 <li><a class="reference internal" href="/native-client/faq.html#faq-troubleshooting"><em>FAQ Troubleshooting</em></a>.</li>
 <li>The <a class="reference internal" href="/native-client/devguide/coding/progress-events.html"><em>Progress Events</em></a> document
 contains some useful information about handling error events.</li>
 </ul>
 <h2 id="next-steps">Next steps</h2>
 <ul class="small-gap">
 <li>See the <a class="reference internal" href="/native-client/devguide/coding/application-structure.html"><em>Application Structure</em></a>
-chapter in the Developer&#8217;s Guide for information about how to structure a
+section in the Developer&#8217;s Guide for information about how to structure a
 Native Client module.</li>
 <li>Check the <a class="reference external" href="/native-client/pepper_stable/cpp">C++ Reference</a> for details
 about how to use the Pepper APIs.</li>
 <li>Browse through the source code of the SDK examples (in the <code>examples</code>
 directory) to learn additional techniques for writing Native Client
 applications and using the Pepper APIs.</li>
 <li>See the <a class="reference internal" href="/native-client/devguide/devcycle/building.html"><em>Building</em></a>, <a class="reference internal" href="/native-client/devguide/devcycle/running.html"><em>Running</em></a>, and <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging pages</em></a> for information about how to build, run, and
 debug Native Client applications.</li>
 <li>Check the <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> project to see
 what libraries have been ported for use with Native Client. If you port an
 open-source library for your own use, we recommend adding it to naclports
 (see <a class="reference external" href="http://code.google.com/p/naclports/wiki/HowTo_Checkin">How to check code into naclports</a>).</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}