NaCl documentation: update FAQ and examples

native_client_sdk/src/doc/sdk/examples.rst

Index: native_client_sdk/src/doc/sdk/examples.rst
diff --git a/native_client_sdk/src/doc/sdk/examples.rst b/native_client_sdk/src/doc/sdk/examples.rst
index 1b12b12cca2ed3c853f26995174dbe53fd31f0a6..9a4c5d5e7b6fa85dcff9a59516168e5502a8db09 100644
--- a/native_client_sdk/src/doc/sdk/examples.rst
+++ b/native_client_sdk/src/doc/sdk/examples.rst
@@ -208,13 +208,16 @@ Run the SDK examples as packaged apps
 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 (``manifest.json``), an icon, and all of the regular Native Client
 application files. Refer to `What are Chrome Apps </apps/about_apps>`_ for more
 information about creating a packaged application.
 
-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::
+Some Pepper features, such as `TCP
+<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP

[binji, 2015/02/09 18:13:42]

bad link

[JF, 2015/02/09 19:25:39]

Are you sure? This works:

https://developer.chrome.com/native-client/pepper_stable/cpp/classpp_1_1_u_d_...

[binji, 2015/02/09 21:29:51]

I mean it looks like that's a link to udp, not tcp.

+<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ socket access, are only allowed
+in `packaged applications </apps/about_apps>`_. The examples that use these
+features must be run as `packaged applications </apps/about_apps>`_, by using
+the following command::
 
   $ make run_package