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

native_client_sdk/src/doc/devguide/tutorial/tutorial-part1.rst

 .. _tutorial:
 
 ######################################
 C++ Tutorial: Getting Started (Part 1)
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Overview
 ========
 
 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.
 
-It's recommended to read the :doc:`Native Client Technical Overview
+It's recommended that you read the :doc:`Native Client Technical Overview
 </overview>` prior to going through this tutorial.
 
 What the application in this tutorial does
 ------------------------------------------
 
 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 ``'hello'`` message to the Native Client module. When the Native
-Client module receives a message, it checks whether the message is equal to the
-string ``'hello'``. If it is, the Native Client module returns a message saying
-``'hello from NaCl'``. A JavaScript alert panel displays the message received
-from the Native Client module.
+web page, and how to send messages between JavaScript and the Native Client 
+module. In this simple application, the JavaScript sends a ``'hello'`` message 
+to the Native Client module. When the Native Client module receives a message, 
+it checks whether the message is equal to the string ``'hello'``. If it is, the
+Native Client module returns a message saying ``'hello from NaCl'``. A 
+JavaScript alert panel displays the message received from the Native Client 
+module.
 
 Communication between JavaScript and Native Client modules
 ----------------------------------------------------------
 
 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
 :doc:`Developer's Guide: Messaging System </devguide/coding/message-system>`.
 It is also similar to the way `web workers
 <http://en.wikipedia.org/wiki/Web_worker>`_ interact with the main document in
 JavaScript.
@@ skipping 19 matching lines @@
   $ cd pepper_$(VERSION)/getting_started
   $ make serve
 
 .. Note::
   :class: note
 
   The SDK may consist of several "bundles", one per Chrome/Pepper version (see
   :doc:`versioning information </version>`). In the sample invocation above
   ``pepper_$(VERSION)`` refers to the specific version you want to use. For
   example, ``pepper_31``. If you don't know which version you need, use the
-  one labeled ``(stable)`` by ``naclsdk list``. See :doc:`Download the Native
-  Client SDK </sdk/download>` for more details.
+  one labeled ``(stable)`` by the ``naclsdk list`` command. See 
+  :doc:`Download the Native Client SDK </sdk/download>` for more details.
 
 If no port number is specified, the server defaults to port 5103, and can be
 accessed at ``http://localhost:5103``.
 
 Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.
 
 .. _tutorial_step_3:
 
 Step 3: Set up the Chrome browser
@@ skipping 182 matching lines @@
 There's more information about troubleshooting in the documentation:
 
 * :ref:`FAQ Troubleshooting <faq_troubleshooting>`.
 * The :doc:`Progress Events </devguide/coding/progress-events>` document
   contains some useful information about handling error events.
 
 Next steps
 ==========
 
 * See the :doc:`Application Structure </devguide/coding/application-structure>`
-  chapter in the Developer's Guide for information about how to structure a
+  section in the Developer's Guide for information about how to structure a
   Native Client module.
 * Check the `C++ Reference </native-client/pepper_stable/cpp>`_ for details
   about how to use the Pepper APIs.
 * Browse through the source code of the SDK examples (in the ``examples``
   directory) to learn additional techniques for writing Native Client
   applications and using the Pepper APIs.
 * See the :doc:`Building </devguide/devcycle/building>`, :doc:`Running
   </devguide/devcycle/running>`, and :doc:`Debugging pages
   </devguide/devcycle/debugging>` for information about how to build, run, and
   debug Native Client applications.
 * Check the `naclports <http://code.google.com/p/naclports/>`_ 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 `How to check code into naclports
   <http://code.google.com/p/naclports/wiki/HowTo_Checkin>`_).