NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/src/doc/faq.rst

 ##########################
 Frequently Asked Questions
 ##########################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 This document answers some frequently asked questions about Native
@@ skipping 477 matching lines @@
 take care of most of the necessary changes. You may need to make some
 changes to your operating system calls and interactions with external
 devices to work with the web. Porting existing Linux libraries is
 generally straightforward, with large libraries often requiring no
 source change.
 
 The following kinds of code may be more challenging to port:
 
 * Code that does direct `TCP <pepper_stable/cpp/classpp_1_1_t_c_p_socket>`_ or
   `UDP <pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ networking. For security
-  reasons these APIs are only available to `packaged applications
-  </apps/about_apps>`_ after asking for the appropriate permissions, not on the
-  open web. Native Client is otherwise restricted to the networking APIs
-  available in the browser. You may want to use to `nacl_io library <nacl_io>`_
-  to use POSIX-like sockets.
+  reasons these APIs are only available to `Chrome apps </apps>`_ after asking
+  for the appropriate permissions, not on the open web. Native Client is
+  otherwise restricted to the networking APIs available in the browser. You may
+  want to use to `nacl_io library <nacl_io>`_ to use POSIX-like sockets.
 * Code that creates processes, including UNIX ``fork``, won't function
   as-is. However, threads are supported. You can nonetheless create new
   ``<embed>`` tags in your HTML page to launch new PNaCl processes. You can even
   use new ``.pexe`` files that your existing ``.pexe`` saved in a local
   filesystem. This is somewhat akin to ``execve``, but the process management
   has to go through ``postMessage`` to JavaScript in order to create the new
   ``<embed>``.
 * Code that needs to do local file I/O. Native Client is restricted to accessing
   URLs and to local storage in the browser (the Pepper :doc:`File IO API
   <devguide/coding/file-io>` has access to the same per-application storage that
@@ skipping 75 matching lines @@
 .. _Rust: http://www.rust-lang.org/
 .. _Go: https://golang.org
 .. _native-client-discuss: https://groups.google.com/group/native-client-discuss
 .. _deprecated in Chrome: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
 .. _OpenGL ES 2.0: https://www.khronos.org/opengles/
 .. _GLES2 file: https://code.google.com/p/chromium/codesearch#chromium/src/ppapi/lib/gl/gles2/gles2.c
 .. _Google Chrome privacy policy: https://www.google.com/chrome/intl/en/privacy.html
 .. _Google Chrome Terms of Service: https://www.google.com/chrome/intl/en/eula_text.html
 .. _naclports: https://code.google.com/p/naclports
 .. _CORS: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing