[NaCl SDK Docs] Remove table-of-contents from generated pages.

native_client_sdk/doc_generated/devguide/devcycle/building.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="building">
 <span id="devcycle-building"></span><h1 id="building"><span id="devcycle-building"></span>Building</h1>
-<div class="contents local topic" id="table-of-contents">
+<div class="contents local" id="table-of-contents" style="display: none">
 <p class="topic-title first">Table Of Contents</p>
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#introduction" id="id4">Introduction</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#target-architectures" id="id5">Target architectures</a></li>
 <li><a class="reference internal" href="#c-libraries" id="id6">C libraries</a></li>
 <li><a class="reference internal" href="#c-standard-libraries" id="id7">C++ standard libraries</a></li>
 <li><a class="reference internal" href="#sdk-toolchains" id="id8">SDK toolchains</a></li>
 <li><a class="reference internal" href="#sdk-toolchains-versus-your-hosted-toolchain" id="id9">SDK toolchains versus your hosted toolchain</a></li>
 </ul>
@@ skipping 17 matching lines @@
 <li><a class="reference internal" href="#using-make" id="id20">Using make</a></li>
 <li><a class="reference internal" href="#libraries-and-header-files-provided-with-the-sdk" id="id21">Libraries and header files provided with the SDK</a></li>
 <li><p class="first"><a class="reference internal" href="#troubleshooting" id="id22">Troubleshooting</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#undefined-reference-error" id="id23">&#8220;Undefined reference&#8221; error</a></li>
 <li><a class="reference internal" href="#can-t-find-libraries-containing-necessary-symbols" id="id24">Can&#8217;t find libraries containing necessary symbols</a></li>
 <li><a class="reference internal" href="#pnacl-abi-verification-errors" id="id25">PNaCl ABI Verification errors</a></li>
 </ul>
 </li>
 </ul>
-</div>
-<section id="introduction">
+
+</div><section id="introduction">
 <h2 id="introduction">Introduction</h2>
 <p>This document describes how to build Native Client modules. It is intended for
 developers who have experience writing, compiling, and linking C and C++ code.
 If you haven&#8217;t read the Native Client <a class="reference internal" href="/native-client/overview.html"><em>Technical Overview</em></a> and <a class="reference internal" href="/native-client/devguide/tutorial/index.html"><em>Tutorial</em></a>, we recommend starting
 with those.</p>
 <section id="target-architectures">
 <span id="id1"></span><h3 id="target-architectures"><span id="id1"></span>Target architectures</h3>
 <p>Portable Native Client (PNaCl) modules are written in C or C++ and compiled
 into an executable file ending in a <strong>.pexe</strong> extension using the PNaCl
 toolchain in the Native Client SDK. Chrome can load <strong>pexe</strong> files
@@ skipping 506 matching lines @@
 Function foo has disallowed type: i128 (i128)
 LLVM ERROR: PNaCl ABI verification failed
 </pre>
 <p>When faced with a PNaCl ABI verification error, check the list of features
 that are <a class="reference internal" href="/native-client/nacl-and-pnacl.html#when-to-use-nacl"><em>not supported by PNaCl</em></a>.
 If the problem you face is not listed as restricted,
 <a class="reference internal" href="/native-client/help.html#help"><em>let us know</em></a>!</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}