[NaCl SDK Docs] Only generate one top-level <section> element.

native_client_sdk/doc_generated/devguide/distributing.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="distributing-your-application">
 <span id="distributing"></span><h1 id="distributing-your-application"><span id="distributing"></span>Distributing Your Application</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#portable-native-client" id="id1">Portable Native Client</a></li>
 <li><p class="first"><a class="reference internal" href="#non-portable-native-client" id="id2">Non-portable Native Client</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#packaged-application" id="id3">Packaged application</a></li>
 <li><a class="reference internal" href="#extension" id="id4">Extension</a></li>
 <li><a class="reference internal" href="#hosted-application" id="id5">Hosted application</a></li>
 <li><a class="reference internal" href="#registering-native-client-modules-to-handle-mime-types" id="id6">Registering Native Client modules to handle MIME types</a></li>
 </ul>
 </li>
 </ul>
 
 </div><p>This document describes how to distribute Portable Native Client applications
 on the web, and Native Client applications through the
 <a class="reference external" href="/webstore">Chrome Web Store</a> (CWS).</p>
-<section id="portable-native-client">
 <h2 id="portable-native-client">Portable Native Client</h2>
 <p>Portable Native Client is enabled by default for web pages, so no separate
 distribution step is requred. Making PNaCl a part of your web application is as
 simple as embedding a manifest file that points to a <strong>pexe</strong>. See the
 <a class="reference internal" href="/native-client/overview.html"><em>technical overview</em></a> for more details.</p>
 <img alt="/native-client/images/nacl-in-a-web-app.png" src="/native-client/images/nacl-in-a-web-app.png" />
 <p>The only constraint for distributing PNaCl modules with a web application is
 abiding by the <a class="reference external" href="http://en.wikipedia.org/wiki/Same_origin_policy">Same-origin policy</a>. The PNaCl manifest and
 <strong>pexe</strong> must either be served from the same domain with the HTML, or the <a class="reference external" href="http://en.wikipedia.org/wiki/Cross-origin_resource_sharing">CORS
 mechanism</a> should
 be used to safely host them on a different domain.</p>
-</section><section id="non-portable-native-client">
 <h2 id="non-portable-native-client">Non-portable Native Client</h2>
 <p>NaCl modules are only allowed for applications distributed through the <a class="reference external" href="https://chrome.google.com/webstore/category/apps">Chrome
 Web Store (CWS)</a>
 The CWS requirement is in place to prevent the proliferation of Native Client
 executables (<strong>nexe</strong>s) compiled for specific architecures (e.g., x86-32,
 x86-64, or ARM).</p>
 <p>In general, the considerations and guidelines for distributing applications
 through the Chrome Web Store apply to applications that contain NaCl modules as
 well. Here are a few pointers to relevant documentation:</p>
 <ul class="small-gap">
 <li><a class="reference external" href="/webstore">CWS Overview</a></li>
 <li><a class="reference external" href="/webstore/choosing">Choosing an App Type</a></li>
 <li><a class="reference external" href="/apps/about_apps">Getting started with packaged apps</a></li>
 <li><a class="reference external" href="https://developers.google.com/chrome/apps/docs/developers_guide">Hosted apps</a></li>
 <li><a class="reference external" href="/extensions">Chrome extensions</a></li>
 </ul>
 <p>In this document, we&#8217;ll focus only on distribution issues specific to
 applications that contain NaCl modules.</p>
-<section id="packaged-application">
-<span id="distributing-packaged"></span><h3 id="packaged-application"><span id="distributing-packaged"></span>Packaged application</h3>
+<h3 id="packaged-application"><span id="distributing-packaged"></span>Packaged application</h3>
 <p>A packaged application is a special zip file (with a .crx extension) hosted in
 the Chrome Web Store. This file contains all of the application parts: A Chrome
 Web Store manifest file (manifest.json), an icon, and all of the regular Native
 Client application files. Refer to
 <a class="reference external" href="/apps/about_apps">Packaged Apps</a>
 for more information about creating a packaged application.</p>
-<section id="reducing-the-size-of-the-user-download-package">
 <h4 id="reducing-the-size-of-the-user-download-package">Reducing the size of the user download package</h4>
 <aside class="note">
 <strong>Tip:</strong>
 Packaging an app in a multi-platform zip file can significantly reduce the
 download and storage requirements for the app.
 </aside>
 <p>As described above, to upload a packaged app to the CWS you have to create a zip
 file with all the resources that your app needs, including .nexe files for
 multiple architectures (x86-64, x86-32, and ARM). Prior to Chrome 28, when users
 installed your app they had to download a .crx file from the CWS with all the
@@ skipping 158 matching lines @@
 function getPath(name) {
   return '_platform_specific/' +
     chrome.runtime.getPlatformInfo().nacl_arch +
     '/' + name;
 }
 </pre>
 </li>
 <li><p class="first">Test your app, create a zip file, and upload the app to the CWS as before.</p>
 </li>
 </ol>
-</section><section id="additional-considerations-for-a-packaged-application">
-<span id="additional-considerations-packaged"></span><h4 id="additional-considerations-for-a-packaged-application"><span id="additional-considerations-packaged"></span>Additional considerations for a packaged application</h4>
+<h4 id="additional-considerations-for-a-packaged-application"><span id="additional-considerations-packaged"></span>Additional considerations for a packaged application</h4>
 <ul class="small-gap">
 <li>In the description of your application in the CWS, make sure to mention that
 your application is a Native Client application that only works with the
 Chrome browser. Also make sure to identify the minimum version of Chrome
 that your application requires.</li>
 <li><p class="first">Hosted and packaged applications have a &#8220;launch&#8221; parameter in the CWS
 manifest. This parameter is present only in apps (not extensions), and it
 tells Google Chrome what to show when a user starts an installed app. For
 example:</p>
 <pre>
 &quot;launch&quot;: {
   &quot;web_url&quot;: &quot;http://mail.google.com/mail/&quot;
 }
 </pre>
 </li>
 <li>If you want to write local data using the Pepper
 <a class="reference external" href="/native-client/peppercpp/classpp_1_1_file_i_o">FileIO</a>
 API, you must set the &#8216;unlimitedStorage&#8217; permission in your Chrome Web
 Store manifest file, just as you would for a JavaScript application that
 uses the HTML5 File API.</li>
 <li>For packaged applications, you can only use in-app purchases.</li>
 <li>You can place your application in the Google Web Store with access only to
 certain people for testing. See <a class="reference external" href="/webstore/publish">Publishing to test accounts</a> for more information.</li>
 </ul>
-</section></section><section id="extension">
 <h3 id="extension">Extension</h3>
 <p>The NaCl-specific notes for a <a class="reference internal" href="#distributing-packaged"><em>package application</em></a>
 apply to extensions as well.</p>
-</section><section id="hosted-application">
 <h3 id="hosted-application">Hosted application</h3>
 <p>The .html file, .nmf file (Native Client manifest file), and .nexe files must
 be served from the same domain, and the Chrome Web Store manifest file must
 specify the correct, verified domain. Other files can be served from the same
 or another domain.</p>
 <p>In addition, see <a class="reference internal" href="#additional-considerations-packaged"><em>Additional considerations for a packaged application</em></a>.</p>
-</section><section id="registering-native-client-modules-to-handle-mime-types">
 <h3 id="registering-native-client-modules-to-handle-mime-types">Registering Native Client modules to handle MIME types</h3>
 <p>If you want Chrome to use a Native Client module to display a particular type
 of content, you can associate the MIME type of that content with the Native
 Client module. Use the <code>nacl_modules</code> attribute in the Chrome Web Store
 manifest file to register a Native Client module as the handler for one or more
 specific MIME types. For example, the bold code in the snippet below registers
 a Native Client module as the content handler for the OpenOffice spreadsheet
 MIME type:</p>
 <pre>
 {
@@ skipping 28 matching lines @@
    },
    {
       &quot;path&quot;: &quot;DocumentViewer.nmf&quot;,
       &quot;mime_type&quot;: &quot;application/vnd.oasis.opendocument.text&quot;
    }]
 }
 </pre>
 <p>The <code>nacl_modules</code> attribute is optional&#8212;specify this attribute only if
 you want Chrome to use a Native Client module to display a particular type of
 content.</p>
-</section></section></section>
+</section>
 
 {{/partials.standard_nacl_article}}