NaCL docs: add missing generated files

native_client_sdk/doc_generated/devguide/coding/application-structure.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="application-structure">
 <span id="devcycle-application-structure"></span><h1 id="application-structure"><span id="devcycle-application-structure"></span>Application Structure</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#application-components" id="id1">Application components</a></li>
 <li><a class="reference internal" href="#html-file-and-the-embed-element" id="id2">HTML file and the &lt;embed&gt; element</a></li>
 <li><a class="reference internal" href="#manifest-files" id="id3">Manifest Files</a></li>
 <li><a class="reference internal" href="#modules-and-instances" id="id4">Modules and instances</a></li>
@@ skipping 56 matching lines @@
 <dd>specifies the MIME type of the embedded content; for Portable Native Client
 modules the type must be &#8220;application/x-pnacl&#8221;. For architecture-specific
 Native Client modules the type must be &#8220;application/x-nacl&#8221;</dd>
 </dl>
 </section><section id="manifest-files">
 <span id="manifest-file"></span><h2 id="manifest-files"><span id="manifest-file"></span>Manifest Files</h2>
 <p>Native Client applications have two types of manifest files: a Chrome Web Store
 manifest file and a Native Client manifest file.</p>
 <p>A <strong>Chrome Web Store manifest file</strong> is a file with information about a web
 application that is published in the Chrome Web Store. This file, named
-<code>manifest.json</code>, is required for applications that are published in the Chrome
-Web Store. For more information about this file see <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your
-Application</em></a>.  and the <a class="reference external" href="http://code.google.com/chrome/extensions/manifest.html">Chrome Web Store manifest file format</a>.</p>
+<code>manifest.json</code>, is required for applications that are published in the
+Chrome Web Store. For more information about this file see <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing
+Your Application</em></a>.  and the <a class="reference external" href="/extensions/manifest">Chrome Web Store manifest file
+format</a>.</p>
 <p>A <strong>Native Client manifest file</strong> is a file that specifies which Native Client
 module (executable) to load. For PNaCl it specifies a single portable
 executable; otherwise it specifies one for each of the supported end-user
 computer architectures (for example x86-32, x86-64, or ARM). This file is
 required for all Native Client applications. The extension for this file is
 .nmf.</p>
 <p>Manifest files for applications that use PNaCl are simple. Here is the manifest
 for the hello world example:</p>
 <pre class="prettyprint">
 {
@@ skipping 117 matching lines @@
 issue a <code>crash</code> event
 <a class="reference internal" href="/native-client/devguide/coding/progress-events.html"><em>which can be handled in Javascript</em></a>.</p>
 <p>While the <code>CreateModule()</code> factory function, the <code>Module</code> class, and the
 <code>Instance</code> class are required for a Native Client application, the code
 samples shown above don&#8217;t actually do anything. Subsequent chapters in the
 Developer&#8217;s Guide build on these code samples and add more interesting
 functionality.</p>
 </section></section>
 
 {{/partials.standard_nacl_article}}