NaCl docs: clarify Chrome apps instead of packaged apps

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

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="c-tutorial-getting-started-part-2">
 <span id="tutorial2"></span><h1 id="c-tutorial-getting-started-part-2"><span id="tutorial2"></span>C++ Tutorial: Getting Started (Part 2)</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
 <li><p class="first"><a class="reference internal" href="#using-the-native-client-sdk-build-system" id="id2">Using the Native Client SDK build system</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#simplifying-the-makefile" id="id3">Simplifying the Makefile</a></li>
@@ skipping 15 matching lines @@
 </ul>
 </li>
 <li><a class="reference internal" href="#example-specific-behavior-with-example-js" id="id13">Example-specific behavior with example.js</a></li>
 <li><a class="reference internal" href="#compile-the-native-client-module-and-run-the-application-again" id="id14">Compile the Native Client module and run the application again</a></li>
 </ul>
 
 </div><h2 id="overview">Overview</h2>
 <p>This tutorial shows how to convert the finished PNaCl web application from
 <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html"><em>Part 1</em></a> to use the Native Client SDK build system and
 common JavaScript files. It also demonstrates some techniques to make your web
-application <a class="reference external" href="/apps/contentSecurityPolicy">Content Security Policy (CSP)-compliant</a>, which is necessary for <a class="reference external" href="/apps/about_apps">Chrome Apps</a>.</p>
+application <a class="reference external" href="/apps/contentSecurityPolicy">Content Security Policy (CSP)-compliant</a>, which is necessary for <a class="reference external" href="/apps">Chrome Apps</a>.</p>
 <p>Using the Native Client SDK build system makes it easy to build with all of the
 SDK toolchains, and switch between the Debug and Release configurations. It
 also simplifies the makefiles for your project, as we&#8217;ll see in the next
 section. Finally, it adds some useful commands for <a class="reference internal" href="/native-client/sdk/examples.html#running-the-sdk-examples"><em>running</em></a> and <a class="reference internal" href="/native-client/sdk/examples.html#debugging-the-sdk-examples"><em>debugging</em></a>
 your application.</p>
 <p>The finished code for this example can be found in the
 <code>pepper_$(VERSION)/getting_started/part2</code> directory in the Native Client SDK
 download.</p>
 <h2 id="using-the-native-client-sdk-build-system">Using the Native Client SDK build system</h2>
 <p>This section describes how to use the SDK build system. To do so, we&#8217;ll make
@@ skipping 148 matching lines @@
 $(eval $(call LINK_RULE,$(TARGET),$(SOURCES),$(LIBS),$(DEPS)))
 endif
 </pre>
 <p>Finally, the NMF rule generates a NaCl manifest file (<code>.nmf</code>) that references
 each executable generated in the previous step:</p>
 <pre class="prettyprint">
 $(eval $(call NMF_RULE,$(TARGET),))
 </pre>
 <h2 id="making-index-html-work-for-chrome-apps">Making index.html work for Chrome Apps</h2>
 <p>This section describes the changes necessary to make the HTML and JavaScript in
-part1 CSP-compliant. This is required if you want to build a <a class="reference external" href="/apps/about_apps">Chrome App</a>, but is not necessary if you want to use PNaCl on the open
-web.</p>
+part1 CSP-compliant. This is required if you want to build a <a class="reference external" href="/apps">Chrome App</a>, but is not necessary if you want to use PNaCl on the open web.</p>
 <h3 id="csp-rules">CSP rules</h3>
 <p><a class="reference external" href="/apps/contentSecurityPolicy#what">Chrome Apps CSP</a> restricts you from doing
 the following:</p>
 <ul class="small-gap">
 <li>You can’t use inline scripting in your Chrome App pages. The restriction
 bans both <code>&lt;script&gt;</code> blocks and event handlers (<code>&lt;button onclick=&quot;...&quot;&gt;</code>).</li>
 <li>You can’t reference any external resources in any of your app files (except
 for video and audio resources). You can’t embed external resources in an
 iframe.</li>
 <li>You can’t use string-to-JavaScript methods like <code>eval()</code> and <code>new
@@ skipping 217 matching lines @@
 </li>
 <li><p class="first">Re-run the application by reloading <code>http://localhost:5103/part2</code> in
 Chrome.</p>
 <p>After Chrome loads the Native Client module, you should see the message sent
 from the module.</p>
 </li>
 </ol>
 </section>
 
 {{/partials.standard_nacl_article}}