NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/doc_generated/devguide/devcycle/running.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="running">
 <span id="devcycle-running"></span><h1 id="running"><span id="devcycle-running"></span>Running</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
-<li><a class="reference internal" href="#introduction" id="id5">Introduction</a></li>
-<li><a class="reference internal" href="#portable-native-client-pnacl-applications" id="id6">Portable Native Client (PNaCl) applications</a></li>
-<li><a class="reference internal" href="#native-client-applications-and-the-chrome-web-store" id="id7">Native Client applications and the Chrome Web Store</a></li>
-<li><p class="first"><a class="reference internal" href="#prerequisites" id="id8">Prerequisites</a></p>
+<li><a class="reference internal" href="#introduction" id="id6">Introduction</a></li>
+<li><a class="reference internal" href="#portable-native-client-pnacl-applications" id="id7">Portable Native Client (PNaCl) applications</a></li>
+<li><a class="reference internal" href="#native-client-applications-and-the-chrome-web-store" id="id8">Native Client applications and the Chrome Web Store</a></li>
+<li><p class="first"><a class="reference internal" href="#prerequisites" id="id9">Prerequisites</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#browser-and-pepper-versions" id="id9">Browser and Pepper versions</a></li>
-<li><a class="reference internal" href="#chrome-cache" id="id10">Chrome Cache</a></li>
+<li><a class="reference internal" href="#browser-and-pepper-versions" id="id10">Browser and Pepper versions</a></li>
+<li><a class="reference internal" href="#chrome-cache" id="id11">Chrome Cache</a></li>
 </ul>
 </li>
-<li><p class="first"><a class="reference internal" href="#requirements" id="id11">Requirements</a></p>
+<li><p class="first"><a class="reference internal" href="#requirements" id="id12">Requirements</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#native-client-flag" id="id12">Native Client flag</a></li>
-<li><a class="reference internal" href="#web-server" id="id13">Web server</a></li>
+<li><a class="reference internal" href="#native-client-flag" id="id13">Native Client flag</a></li>
+<li><a class="reference internal" href="#web-server" id="id14">Web server</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#technique-1-local-server" id="id14">Technique 1: Local server</a></li>
-<li><a class="reference internal" href="#technique-2-packaged-application-loaded-as-an-unpacked-extension" id="id15">Technique 2: Packaged application loaded as an unpacked extension</a></li>
-<li><a class="reference internal" href="#technique-3-hosted-application-loaded-as-an-unpacked-extension" id="id16">Technique 3: Hosted application loaded as an unpacked extension</a></li>
-<li><a class="reference internal" href="#technique-4-chrome-web-store-application-with-trusted-testers" id="id17">Technique 4: Chrome Web Store application with trusted testers</a></li>
+<li><a class="reference internal" href="#technique-1-local-server" id="id15">Technique 1: Local server</a></li>
+<li><a class="reference internal" href="#technique-2-packaged-application-loaded-as-an-unpacked-extension" id="id16">Technique 2: Packaged application loaded as an unpacked extension</a></li>
+<li><a class="reference internal" href="#technique-3-hosted-application-loaded-as-an-unpacked-extension" id="id17">Technique 3: Hosted application loaded as an unpacked extension</a></li>
+<li><a class="reference internal" href="#technique-4-chrome-web-store-application-with-trusted-testers" id="id18">Technique 4: Chrome Web Store application with trusted testers</a></li>
 </ul>
 
 </div><h2 id="introduction">Introduction</h2>
 <p>This document describes how to run Native Client applications during
 development.</p>
 <p>The workflow for PNaCl applications is straightfoward and will only be discussed
 briefly. For NaCl applications distributed through the web-store, there is a
 number of options and these will be discussed more in-depth.</p>
 <h2 id="portable-native-client-pnacl-applications">Portable Native Client (PNaCl) applications</h2>
 <p>Running PNaCl applications from the open web is enabled in Chrome version 31 and
 above; therefore, no special provisions are required to run and test such
 applications locally. An application that uses a PNaCl module can be tested
 similarly to any other web application that only consists of HTML, CSS and
 JavaScript.</p>
 <p>To better simulate a production environment, it&#8217;s recommended to start a local
 web server to serve the application&#8217;s files. The NaCl SDK comes with a simple
 local server built in, and the process of using it to run PNaCl applications is
 described in <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html#tutorial-step-2"><em>the tutorial</em></a>.</p>
 <h2 id="native-client-applications-and-the-chrome-web-store">Native Client applications and the Chrome Web Store</h2>
 <p>Before reading about how to run Native Client applications, it&#8217;s important to
 understand a little bit about how Native Client applications are distributed.
 As explained in <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your Application</em></a>, Native
 Client applications must currently be distributed through the <strong>Chrome Web
 Store (CWS)</strong>. Applications in the CWS are one of three types:</p>
 <ul class="small-gap">
 <li>A <strong>hosted application</strong> is an application that you host on a server of your
 choice. To distribute an application as a hosted application, you upload
-application metadata to the CWS.</li>
+application metadata to the CWS. Learn more on the <a class="reference external" href="/apps">Chrome App</a>
+documentation page.</li>
 <li>A <strong>packaged application</strong> is an application that is hosted in the CWS and
 downloaded to the user&#8217;s machine. To distribute an application as a packaged
 application, you upload the entire application, including all application
-assets and metadata, to the CWS.</li>
+assets and metadata, to the CWS. Learn more on the <a class="reference external" href="/apps">Chrome App</a>
+documentation page.</li>
 <li>An <strong>extension</strong> is a packaged application that has a tiny UI component
 (extensions are typically used to extend the functionality of the Chrome
 browser). To distribute an application as an extension, you upload the entire
-application, including all application assets and metadata, to the CWS.</li>
+application, including all application assets and metadata, to the CWS. Learn
+more on the <a class="reference external" href="/extensions">Chrome extensions</a> documentation page.</li>
 </ul>
+<p>The web store documentation contains a handy guide to <a class="reference external" href="https://developer.chrome.com/webstore/choosing">help you choose which to
+use</a>.</p>
 <p>It&#8217;s clearly not convenient to package and upload files to the Chrome Web Store
 every time you want to run a new build of your application, but there are four
 alternative techniques you can use to run the application during development.
 These techniques are listed in the following table and described in detail
 below. Each technique has certain requirements (NaCl flag, web server, and/or
 CWS metadata); these are explained in the <a class="reference internal" href="#requirements"><em>Requirements</em></a>
 section below.</p>
 <table border="1" class="docutils">
 <colgroup>
 </colgroup>
@@ skipping 86 matching lines @@
 that is equal to or higher than the version of the Pepper API that your
 application uses. For example, if you compiled your application using the
 <code>pepper_37</code> bundle, your application uses the Pepper 37 API, and you must run
 the application in Chrome 37 or higher. To check which version of Chrome you&#8217;re
 using, type <code>about:version</code> in the Chrome address bar.</p>
 <h3 id="chrome-cache"><span id="cache"></span>Chrome Cache</h3>
 <p>Chrome caches resources aggressively. You should disable Chrome&#8217;s cache whenever
 you are developing a Native Client application in order to make sure Chrome
 loads new versions of your application. Follow the instructions <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html#tutorial-step-3"><em>in the
 tutorial</em></a>.</p>
-<h2 id="requirements"><span id="id1"></span>Requirements</h2>
+<h2 id="requirements"><span id="id2"></span>Requirements</h2>
 <h3 id="native-client-flag"><span id="flag"></span>Native Client flag</h3>
 <p>Native Client is automatically enabled for applications that are installed from
 the Chrome Web Store. To enable Native Client for applications that are not
 installed from the Chrome Web Store, you must explicitly turn on the Native
 Client flag in Chrome as follows:</p>
 <ol class="arabic simple">
 <li>Type <code>about:flags</code> in the Chrome address bar.</li>
 <li>Scroll down to &#8220;Native Client&#8221;.</li>
 <li>If the link below &#8220;Native Client&#8221; says &#8220;Disable&#8221;, then Native Client is
 already enabled and you don&#8217;t need to do anything else.</li>
 <li>If the link below &#8220;Native Client&#8221; says &#8220;Enable&#8221;:<ul class="small-gap">
 <li>Click the &#8220;Enable&#8221; link.</li>
 <li>Click the &#8220;Relaunch Now&#8221; button in the bottom of the screen. <strong>Native
 Client will not be enabled until you relaunch your browser</strong>. All browser
 windows will restart when you relaunch Chrome.</li>
 </ul>
 </li>
 </ol>
 <p>If you enable the Native Client flag and still can&#8217;t run applications from
 outside the Chrome Web Store, you may need to enable the Native Client plugin:</p>
 <ol class="arabic simple">
 <li>Type <code>about:plugins</code> in the Chrome address bar.</li>
 <li>Scroll down to &#8220;Native Client&#8221;.</li>
 <li>If the link below &#8220;Native Client&#8221; says &#8220;Enable&#8221;, click the link to enable
 the Native Client plugin. You do not need to relaunch Chrome after enabling
 the Native Client plugin.</li>
 </ol>
-<h3 id="web-server"><span id="id2"></span>Web server</h3>
+<h3 id="web-server"><span id="id3"></span>Web server</h3>
 <p>For security reasons, Native Client applications must come from a server (you
 can&#8217;t simply drag HTML files into your browser). The Native Client SDK comes
 with a lightweight Python web server that you can run to serve your application
 locally. The server can be invoked from a Makefile. Here is how to run the
 server:</p>
 <pre>
 $ cd examples
 $ make serve
 </pre>
 <p>By default, the server listens for requests on port 5103. You can use the server
@@ skipping 98 matching lines @@
 </li>
 <li>Open a new tab in Chrome and click the <strong>Apps</strong> link at the bottom of the
 page to show your installed apps:
 <img alt="new-tab-apps" src="/native-client/images/new-tab-apps.png" /></li>
 <li>The icon for your newly installed app should appear on the New Tab page.
 Click the icon to launch the app.</li>
 </ol>
 <p>For additional information about how to create CWS metadata and load your
 application into Chrome (including troubleshooting information), see the
 <a class="reference external" href="/webstore/get_started_simple">Chrome Web Store Tutorial: Getting Started</a>.</p>
-<p>See also <a class="reference internal" href="/native-client/sdk/examples.html#run-sdk-examples-as-packaged"><em>Run the SDK examples as packaged apps</em></a>.</p>
+<p>See also <a class="reference internal" href="/native-client/sdk/examples.html#run-sdk-examples-as-packaged"><em>Run the SDK examples as Chrome apps</em></a>.</p>
 <h2 id="technique-3-hosted-application-loaded-as-an-unpacked-extension">Technique 3: Hosted application loaded as an unpacked extension</h2>
 <p>For development purposes, Chrome lets you load a hosted application as an
 unpacked extension. To load and run your hosted application as an unpacked
 extension:</p>
 <ol class="arabic simple">
 <li>Start a web server to serve your application.<ul class="small-gap">
 <li>You can use the <a class="reference internal" href="#web-server"><em>local web server</em></a> included with the
 Native Client SDK if you want.</li>
 </ul>
 </li>
@@ skipping 109 matching lines @@
 </ul>
 </li>
 </ol>
 <p>To publish an application to the world after publishing it to test accounts,
 you must first unpublish the application. For additional information see
 <a class="reference external" href="/webstore/docs/publish">Publishing Your App</a>, and in particular <a class="reference external" href="/webstore/publish#testaccounts">Publishing
 to test accounts</a>.</p>
 </section>
 
 {{/partials.standard_nacl_article}}