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

native_client_sdk/doc_generated/io2014.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="building-a-nacl-app">
 <span id="io2014"></span><h1 id="building-a-nacl-app"><span id="io2014"></span>Building a NaCl App</h1>
-<section id="in-the-browser">
 <h2 id="in-the-browser">In the browser!</h2>
 <p>Follow along with Brad Nelson&#8217;s Google I/O 2014 talk.
 Explore our new in-browser development environment and debugger.</p>
 <p>Learn how easy it is to edit, build, and debug NaCl application
 all in your desktop web browser or on a Chromebook.
 Work either on-line or off-line!</p>
 <iframe class="video" width="500" height="281"
-src="//www.youtube.com/embed/OzNuzBDEWzk?rel=0" frameborder="0"></iframe><section id="work-in-progress">
-<h3 id="work-in-progress">Work in Progress</h3>
+src="//www.youtube.com/embed/OzNuzBDEWzk?rel=0" frameborder="0"></iframe><h3 id="work-in-progress">Work in Progress</h3>
 <p>These development tools are a work in progress, see <a class="reference internal" href="#feature-status">Feature Status</a>.
 At this point, they are a learning tool and demonstration of NaCl&#8217;s
 flexibility, but are not the recommended tools for a production application.
 To develop a substantial application for Native Client /
 Portable Native Client,
 we currently recommend you use the
 <a class="reference external" href="/native-client/sdk/download">Native Client SDK</a>.</p>
 <b><font color="#880000">
 NOTE: The NaCl Development Environment is not yet stable.
 Ideally user data is preserved, but currently it can be lost during updates
 or sporadically. We're working to resolve this.
-</font></b></section><section id="installation">
-<h3 id="installation">Installation</h3>
+</font></b><h3 id="installation">Installation</h3>
 <p>The setup process currently requires several steps.
 We&#8217;re working to reduce the number of steps in future releases.
 As the process gets easier, we&#8217;ll update this page.</p>
 <p>To install the development environment:</p>
 <blockquote>
 <div><ul class="small-gap">
 <li>Install the <a class="reference external" href="https://chrome.google.com/webstore/detail/nacl-development-environm/aljpgkjeipgnmdpikaajmnepbcfkglfa">NaCl Development Environment</a>.</li>
 <li><p class="first">Navigate to: chrome://flags and:</p>
 <ul class="small-gap">
 <li>Enable <strong>Native Client</strong>.</li>
@@ skipping 16 matching lines @@
 <li><p class="first">Navigate to: chrome://flags and:</p>
 <ul class="small-gap">
 <li>Enable <strong>Native Client GDB-based debugging</strong>.</li>
 <li>Restart your browser by clicking <strong>Relaunch Now</strong>.</li>
 </ul>
 </li>
 <li>NOTE: If you experience unexplained hangs, disable GDB-based debugging
 temporarily and try again.</li>
 </ul>
 </div></blockquote>
-</section><section id="editor">
 <h3 id="editor">Editor</h3>
 <p>To follow along in this tutorial, you&#8217;ll need to use a text editor to modify
 various files in our development environment.
 There are currently two editor options, nano or vim.
 Emacs is coming soon...
 If you&#8217;re unsure what to pick, nano is simpler to start with and has on-screen
 help.</p>
 <ul class="small-gap">
 <li><p class="first">You can open <strong>nano</strong> like this:</p>
 <pre class="prettyprint">
 $ nano &lt;filename&gt;
 </pre>
 <p>Here&#8217;s an online <a class="reference external" href="http://mintaka.sdsu.edu/reu/nano.html">nano tutorial</a>.</p>
 </li>
 <li><p class="first">You can open <strong>vim</strong> like this:</p>
 <pre class="prettyprint">
 $ vim &lt;filename&gt;
 </pre>
 <p>Here&#8217;s an online <a class="reference external" href="http://www.openvim.com/tutorial.html">vim tutorial</a>.</p>
 </li>
 </ul>
-</section><section id="git-setup">
 <h3 id="git-setup">Git Setup</h3>
 <p>This tutorial also uses a revision control program called
 <a class="reference external" href="http://en.wikipedia.org/wiki/Git_(software)">git</a>.
 In order to commit to a git repository,
 you need to setup your environment to with your identity.</p>
 <p>You&#8217;ll need to add these lines to <cite>~/.bashrc</cite> to cause them to be invoked each
 time you start the development environment.</p>
 <pre class="prettyprint">
 git config --global user.name &quot;John Doe&quot;
 git config --global user.email johndoe&#64;example.com
 </pre>
 <p>You can reload you <cite>~/.bashrc</cite> by running:</p>
 <pre class="prettyprint">
 source ~/.bashrc
 </pre>
-</section><section id="tour-follow-the-video">
 <h3 id="tour-follow-the-video">Tour (follow the video)</h3>
 <p>Create a working directory and go into it:</p>
 <pre class="prettyprint">
 $ mkdir work
 $ cd work
 </pre>
 <p>Download a zip file containing our sample:</p>
 <pre class="prettyprint">
 $ curl http://nacltools.storage.googleapis.com/io2014/voronoi.zip -O
 $ ls -l
@@ skipping 52 matching lines @@
 </pre>
 <p>To test our application, we run a local web server, written in python.
 Run the server with this command (NOTE: Running through a Makefile
 now):</p>
 <pre class="prettyprint">
 $ make serve
 </pre>
 <p>Then, navigate to <a class="reference external" href="http://localhost:5103/">http://localhost:5103/</a> to test the demo.</p>
 <p>If you follow along with the demo video, you will discover the sample crashes
 when you change the thread count.</p>
-</section><section id="debugging">
 <h3 id="debugging">Debugging</h3>
 <p>If you haven&#8217;t installed the debugger at this point, skip to the next section.</p>
 <p>At this point, if you have the debugger installed, you should be able to open
 the developer console and view the resulting crash.</p>
 <p>You can see a backtrace with:</p>
 <pre class="prettyprint">
 bt
 </pre>
 <p>You can see active threads with:</p>
 <pre class="prettyprint">
 info threads
 </pre>
 <p>Currently, symbol information is limited for GLibC executables.
 We have improvements coming that will improve the experience further.</p>
 <p>For newlib and PNaCl executables you can retrieve full symbols information
 with:</p>
 <pre class="prettyprint">
 remote get irt irt
 add-symbol-file irt
 remote get nexe nexe
 add-symbol-file nexe
 </pre>
-</section><section id="fix-it-up">
 <h3 id="fix-it-up">Fix it up</h3>
 <p>Return to the development environment and stop the test server,
 by pressing Ctrl-C.</p>
 <p>Open your editor again, navigate to line 485 and change <em>valu</em> to <em>value</em>.</p>
 <p>Then rebuild:</p>
 <pre class="prettyprint">
 $ make -j10
 </pre>
 <p>Check the diff and commit our fix:</p>
 <pre class="prettyprint">
 $ git diff
 $ git commit -am &quot;fixed thread ui bug&quot;
 </pre>
 <p>Now look at your commit history:</p>
 <pre class="prettyprint">
 $ git log
 </pre>
 <p>Run the demo again. And everything now works:</p>
 <pre class="prettyprint">
 $ make serve
 </pre>
-</section><section id="thanks">
 <h3 id="thanks">Thanks</h3>
 <p>Thanks for checking out our environment.
 Things are rapidly changing and in the coming months you can expect to see
 further improvements and filling out of our platform and library support.</p>
 <p>Check back at this page for the latest status.</p>
-</section><section id="feature-status">
 <h3 id="feature-status">Feature Status</h3>
 <p>Here is a summary of feature status. We hope to overcome these limitations
 in the near future:</p>
 <blockquote>
 <div><ul class="small-gap">
 <li><p class="first">NaCl Development Environment</p>
 <ul class="small-gap">
 <li><p class="first">General</p>
 <ul class="small-gap">
 <li><p class="first">Supported:</p>
@@ skipping 31 matching lines @@
 <ul class="small-gap">
 <li>ChromeOS</li>
 <li>Mac OSX</li>
 <li>Windows</li>
 </ul>
 </li>
 </ul>
 </li>
 </ul>
 </div></blockquote>
-</section></section></section>
+</section>
 
 {{/partials.standard_nacl_article}}