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

native_client_sdk/doc_generated/devguide/coding/native-client-modules.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="native-client-modules">
 <span id="devcycle-native-client-modules"></span><h1 id="native-client-modules"><span id="devcycle-native-client-modules"></span>Native Client Modules</h1>
 <p>This document describes the classes and functions that you need to implement in
 a Native Client module in order for Chrome to load, initialize, and run it.  The
 requirements are the same regardless of whether or not the module uses PNaCl,
 but depend on whether the module is written in C or C++.</p>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id2">Introduction</a></li>
 <li><a class="reference internal" href="#writing-modules-in-c" id="id3">Writing modules in C</a></li>
 <li><a class="reference internal" href="#id1" id="id4">Writing modules in C++</a></li>
 </ul>
 
-</div><section id="introduction">
-<h2 id="introduction">Introduction</h2>
+</div><h2 id="introduction">Introduction</h2>
 <p>Native Client modules do not have a <code>main()</code> function. When a module loads,
 the Native Client runtime calls the code in the module to create an instance and
 initialize the interfaces for the APIs the module uses. This initialization
 sequence depends on whether the module is written in C or C++ and requires that
 you implement specific functions in each case.</p>
-</section><section id="writing-modules-in-c">
 <h2 id="writing-modules-in-c">Writing modules in C</h2>
 <p>The C API uses a prefix convention to show whether an interface is implemented
 in the browser or in a module. Interfaces starting with <code>PPB_</code> (which can be
 read as &#8220;Pepper <em>browser</em>&#8221;) are implemented in the browser and they are called
 from your module. Interfaces starting with <code>PPP_</code> (&#8220;Pepper <em>plugin</em>&#8221;) are
 implemented in the module; they are called from the browser and will execute on
 the main thread of the module instance.</p>
 <p>When you implement a Native Client module in C you must include these components:</p>
 <ul class="small-gap">
 <li>The functions <code>PPP_InitializeModule</code> and <code>PPP_GetInterface</code></li>
@@ skipping 70 matching lines @@
 }
 
 // Define PPP_InitializeModule, the entry point of your module.
 // Retrieve the API for the browser-side (PPB) interfaces you will use.
 PP_EXPORT int32_t PPP_InitializeModule(PP_Module a_module_id, PPB_GetInterface get_browser) {
         ppb_instance_interface = (PPB_Instance*)(get_browser(PPB_INSTANCE_INTERFACE));
         ppb_input_event_interface = (PPB_InputEvent*)(get_browser(PPB_INPUT_EVENT_INTERFACE));
         return PP_OK;
 }
 </pre>
-</section><section id="id1">
 <h2 id="id1">Writing modules in C++</h2>
 <p>When you implement a Native Client module in C++ you must include these components:</p>
 <ul class="small-gap">
 <li>The factory function called <code>CreateModule()</code></li>
 <li>Code that defines your own Module class (derived from the <code>pp::Module</code>
 class)</li>
 <li>Code that defines your own Instance class (derived from the <code>pp:Instance</code>
 class)</li>
 </ul>
 <p>In the &#8220;Hello tutorial&#8221; example (in the <code>getting_started/part1</code> directory of
@@ skipping 41 matching lines @@
 an implementation of the <code>HandleMessage()</code> function. The browser calls an
 instance&#8217;s <code>HandleMessage()</code> function every time the JavaScript code in an
 application calls <code>postMessage()</code> to send a message to the instance. See the
 <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Native Client messaging system</em></a> for more information about
 how to send messages between JavaScript code and Native Client modules.</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 documents in the
 Developer&#8217;s Guide build on these code samples and add more interesting
 functionality.</p>
-</section></section>
+</section>
 
 {{/partials.standard_nacl_article}}