NaCl documentation: update FAQ and examples

native_client_sdk/doc_generated/sdk/examples.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <span class="target" id="sdk-examples-2"></span><section id="examples">
 <h1 id="examples">Examples</h1>
 <p>Every Native Client SDK bundle comes with a folder of example applications.
 Each example demonstrates one or two key Native Client programming concepts.
 After you&#8217;ve <a class="reference internal" href="/native-client/sdk/download.html"><em>downloaded the SDK</em></a>, follow the instructions
 on this page to build and run the examples.</p>
 <p>Your version of Chrome must be equal to or greater than the version of your SDK
 bundle. For example, if you&#8217;re developing with the <code>pepper_35</code> bundle, you
@@ skipping 150 matching lines @@
 application bundle, not the top-level <code>.app</code> directory:</p>
 <pre class="prettyprint">
 $ export CHROME_PATH=&lt;Path to Google Chrome&gt;
 </pre>
 </li>
 </ul>
 <h2 id="run-the-sdk-examples-as-packaged-apps"><span id="run-sdk-examples-as-packaged"></span>Run the SDK examples as packaged apps</h2>
 <p>Each example can also be launched as a packaged application. 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
+manifest file (<code>manifest.json</code>), an icon, and all of the regular Native Client
 application files. Refer to <a class="reference external" href="/apps/about_apps">What are Chrome Apps</a> for more
 information about creating a packaged application.</p>
-<p>Some Pepper features, such as TCP/UDP socket access, are only allowed in
-packaged applications. The examples that use these features must be run as
-packaged applications, by using the following command:</p>
+<p>Some Pepper features, such as <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">TCP</a> or <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">UDP</a> socket access, are only allowed
+in <a class="reference external" href="/apps/about_apps">packaged applications</a>. The examples that use these
+features must be run as <a class="reference external" href="/apps/about_apps">packaged applications</a>, by using
+the following command:</p>
 <pre class="prettyprint">
 $ make run_package
 </pre>
 <p>You can use <code>TOOLCHAIN</code> and <code>CONFIG</code> parameters as described above to run
 with a different toolchain or configuration.</p>
-<h2 id="debugging-the-sdk-examples"><span id="id4"></span>Debugging the SDK examples</h2>
+<h2 id="debugging-the-sdk-examples"><span id="id5"></span>Debugging the SDK examples</h2>
 <p>The NaCl SDK uses <a class="reference external" href="https://www.gnu.org/software/gdb/">GDB</a> to debug Native
 Client code. The SDK includes a prebuilt version of GDB that is compatible with
 NaCl code. To use it, run the <code>make debug</code> command from an example directory:</p>
 <pre class="prettyprint">
 $ make debug
 </pre>
 <p>This launches Chrome with the <code>--enable-nacl-debug</code> flag set. This flag causes
 Chrome to pause when a NaCl module is first loaded, waiting for a connection
 from gdb. The <code>make debug</code> command also simultaneously launches GDB and loads
 the symbols for that NEXE. To connect GDB to Chrome, in the GDB console, type:</p>
 <pre class="prettyprint">
 (gdb) target remote :4014
 </pre>
 <p>This tells GDB to connect to a TCP port on <code>localhost:4014</code>, the port that
 Chrome is listening on. GDB will respond:</p>
 <pre class="prettyprint">
 Remote debugging using :4014
 0x000000000fa00080 in ?? ()
 </pre>
 <p>At this point, you can use the standard GDB commands to debug your NaCl module.
 The most common commands you will use to debug are <code>continue</code>, <code>step</code>,
 <code>next</code>, <code>break</code> and <code>backtrace</code>. See
 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging</em></a> for more information about
 debugging a Native Client application.</p>
 </section>
 
 {{/partials.standard_nacl_article}}