[NaCl SDK] Re-generate docs

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" 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>
@@ skipping 496 matching lines @@
 <dt>libnacl_io.a</dt>
 <dd>Provides a POSIX layer for NaCl. In particular, the library provides a
 virtual file system and support for sockets. The virtual file system
 allows a module to &#8220;mount&#8221; a given directory tree. Once a module has
 mounted a file system, it can use standard C library file operations:
 <code>fopen</code>, <code>fread</code>, <code>fwrite</code>, <code>fseek</code>, and <code>fclose</code>.
 For more detail, see the header <code>include/nacl_io/nacl_io.h</code>.
 For an example of how to use nacl_io, see <code>examples/demo/nacl_io_demo</code>.</dd>
 <dt>libppapi_simple.a</dt>
 <dd>Provides a familiar C programming environment by letting a module have a
-simple entry point that is registered by <code>PPAPI_SIMPLE_REGISTER_MAIN</code>.
-The entry point is similar to the standard C <code>main()</code> function, complete
-with <code>argc</code> and <code>argv[]</code> parameters. For details see
-<code>include/ppapi_simple/ps.h</code>. For an example of
+simple <code>main()</code> entry point.  The entry point is similar to the standard C
+<code>main()</code> function, complete with <code>argc</code> and <code>argv[]</code> parameters. For
+details see <code>include/ppapi_simple/ps.h</code>. For an example of
 how to use ppapi_simple, <code>see examples/tutorial/using_ppapi_simple</code>.</dd>
 </dl>
 <aside class="note">
 <ul class="small-gap">
 <li>Since the Native Client toolchains use their own library and header search
 paths, the tools won&#8217;t find third-party libraries you use in your
 non-Native-Client development. If you want to use a specific third-party
 library for Native Client development, look for it in <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a>, or port the library yourself.</li>
 <li>The order in which you list libraries in your build commands is important,
 since the linker searches and processes libraries in the order in which they
@@ skipping 55 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>
 
 {{/partials.standard_nacl_article}}