[NaCl SDK Docs] Remove links to developers.google.com

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>
@@ skipping 234 matching lines @@
 </pre>
 <p>You must put the <code>manifest.json</code> file in the same directory as your
 application&#8217;s main HTML page.</p>
 <p>If you don&#8217;t have icons for your application, you can use the following icons as
 placeholders:</p>
 <p><img alt="ICON16" src="/native-client/images/icon16.png" /></p>
 <p><img alt="ICON128" src="/native-client/images/icon128.png" /></p>
 <p>Put the icons in the same directory as the CWS manifest file. For more
 information about CWS manifest files and application icons, see:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/chrome/web-store/docs/get_started_simple">Chrome Web Store Tutorial: Getting Started</a></li>
-<li><a class="reference external" href="http://code.google.com/chrome/extensions/manifest.html">Chrome Web Store Formats: Manifest Files</a></li>
+<li><a class="reference external" href="/webstore/get_started_simple">Chrome Web Store Tutorial: Getting Started</a></li>
+<li><a class="reference external" href="/extensions/manifest">Chrome Web Store Formats: Manifest Files</a></li>
 </ul>
 </section></section></section><section id="technique-1-local-server">
 <h2 id="technique-1-local-server">Technique 1: Local server</h2>
 <p>To run your application from a local server:</p>
 <ul class="small-gap">
 <li>Enable the <a class="reference internal" href="#flag"><em>Native Client flag</em></a> in Chrome.</li>
 <li>Start a <a class="reference internal" href="#web-server"><em>local web server</em></a>.</li>
 <li>Put your application under the examples directory in the SDK bundle you are
 using (e.g., in the directory <code>pepper_31/examples/my_app</code>).</li>
 <li>Access your application on the local server by typing the location of its
@@ skipping 32 matching lines @@
 </ul>
 </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="https://developers.google.com/chrome/web-store/docs/get_started_simple">Chrome Web Store Tutorial: Getting Started</a>.</p>
+<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>
 </section><section id="technique-3-hosted-application-loaded-as-an-unpacked-extension">
 <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>
@@ skipping 29 matching lines @@
 </ul>
 </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="https://developers.google.com/chrome/web-store/docs/get_started_simple">Chrome Web Store Tutorial: Getting Started</a>.</p>
+<a class="reference external" href="/webstore/get_started_simple">Chrome Web Store Tutorial: Getting Started</a>.</p>
 </section><section id="technique-4-chrome-web-store-application-with-trusted-testers">
 <h2 id="technique-4-chrome-web-store-application-with-trusted-testers">Technique 4: Chrome Web Store application with trusted testers</h2>
 <p>When you&#8217;re ready to test your application more broadly, you can upload the
 application to the Chrome Web Store and let some trusted testers run it. Here
 is how to do so:</p>
 <ol class="arabic simple">
 <li>Create the Chrome Web Store metadata required to publish your application:<ul class="small-gap">
 <li>First, create a Chrome Web Store manifest file and one or more icons for
 your application, as described above under <a class="reference internal" href="#metadata"><em>Chrome Web Store metadata</em></a>. Note that packaged applications must have at least two icons
 (a 16x16 icon and a 128x128 icon).</li>
@@ skipping 57 matching lines @@
 <li>When you publish an application to test accounts, the application&#8217;s CWS
 listing is visible only to you and to people who are logged into those
 accounts. Your application won&#8217;t appear in search results, so you need to
 give testers a direct link to your application&#8217;s CWS listing. Users won&#8217;t
 be able to find the application by searching in the CWS.</li>
 </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="https://developers.google.com/chrome/web-store/docs/publish">Publishing Your App</a>, and in
-particular <a class="reference external" href="https://developers.google.com/chrome/web-store/docs/publish#testaccounts">Publishing to test accounts</a>.</p>
+<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></section>
 
 {{/partials.standard_nacl_article}}