NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/src/doc/devguide/distributing.rst

 .. _distributing:
 
 #############################
 Distributing Your Application
 #############################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 27 matching lines @@
 The CWS requirement is in place to prevent the proliferation of Native Client
 executables (**nexe**\s) compiled for specific architecures (e.g., x86-32,
 x86-64, or ARM).
 
 In general, the considerations and guidelines for distributing applications
 through the Chrome Web Store apply to applications that contain NaCl modules as
 well. Here are a few pointers to relevant documentation:
 
 * `CWS Overview </webstore>`_
 * `Choosing an App Type </webstore/choosing>`_
-* `Getting started with packaged apps </apps/about_apps>`_
-* `Hosted apps <https://developers.google.com/chrome/apps/docs/developers_guide>`_
+* `Getting started with Chrome apps </apps>`_
 * `Chrome extensions </extensions>`_
 
 In this document, we'll focus only on distribution issues specific to
 applications that contain NaCl modules.
 
 .. _distributing_packaged:
 
-Packaged application
---------------------
+Chrome apps
+-----------
 
-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 application files. Refer to
-`Packaged Apps </apps/about_apps>`_
-for more information about creating a packaged application.
+A Chrome app 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
+application files. Refer to `Chrome Apps </apps>`_ for more information about
+creating a Chrome app.
 
 Reducing the size of the user download package
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 .. Note::
    :class: note
 
    **Tip:**
    Packaging an app in a multi-platform zip file can significantly reduce the
    download and storage requirements for the app.
 
-As described above, to upload a packaged app to the CWS you have to create a zip
+As described above, to upload a Chrome app to the CWS you have to create a zip
 file with all the resources that your app needs, including .nexe files for
 multiple architectures (x86-64, x86-32, and ARM). Prior to Chrome 28, when users
 installed your app they had to download a .crx file from the CWS with all the
 included .nexe files.
 
 Starting with Chrome 28, the Chrome Web Store includes a feature called
 **multi-platform zip files.** This feature lets you structure your application
 directory and zip file in a way that reduces the size of the user download
 package.  Here's how this feature works:
 
@@ skipping 144 matching lines @@
       function getPath(name) {
         return '_platform_specific/' +
           chrome.runtime.getPlatformInfo().nacl_arch +
           '/' + name;
       }
 
 #. Test your app, create a zip file, and upload the app to the CWS as before.
 
 .. _additional_considerations_packaged:
 
-Additional considerations for a packaged application
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Additional considerations for a Chrome app
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 * In the description of your application in the CWS, make sure to mention that
   your application is a Native Client application that only works with the
   Chrome browser. Also make sure to identify the minimum version of Chrome
   that your application requires.
 * Hosted and packaged applications have a "launch" parameter in the CWS
   manifest. This parameter is present only in apps (not extensions), and it
   tells Google Chrome what to show when a user starts an installed app. For
   example:
 
   .. naclcode::
     :prettyprint: 0
 
     "launch": {
       "web_url": "http://mail.google.com/mail/"
     }
 
 * If you want to write local data using the Pepper
   `FileIO </native-client/peppercpp/classpp_1_1_file_i_o>`_
   API, you must set the 'unlimitedStorage' permission in your Chrome Web
   Store manifest file, just as you would for a JavaScript application that
   uses the HTML5 File API.
-* For packaged applications, you can only use in-app purchases.
+* For Chrome apps, you can only use in-app purchases.
 * You can place your application in the Google Web Store with access only to
   certain people for testing. See `Publishing to test accounts
   </webstore/publish>`_ for more information.
 
 Extension
 ---------
 
 The NaCl-specific notes for a :ref:`package application <distributing_packaged>`
 apply to extensions as well.
 
 Hosted application
 ------------------
 
 The .html file, .nmf file (Native Client manifest file), and .nexe files must
 be served from the same domain, and the Chrome Web Store manifest file must
 specify the correct, verified domain. Other files can be served from the same
 or another domain.
 
-In addition, see :ref:`Additional considerations for a packaged application <additional_considerations_packaged>`.
+In addition, see :ref:`Additional considerations for a Chrome apps
+<additional_considerations_packaged>`.
 
 Registering Native Client modules to handle MIME types
 ------------------------------------------------------
 
 If you want Chrome to use a Native Client module to display a particular type
 of content, you can associate the MIME type of that content with the Native
 Client module. Use the ``nacl_modules`` attribute in the Chrome Web Store
 manifest file to register a Native Client module as the handler for one or more
 specific MIME types. For example, the bold code in the snippet below registers
 a Native Client module as the content handler for the OpenOffice spreadsheet
@@ skipping 39 matching lines @@
      {
         "path": "DocumentViewer.nmf",
         "mime_type": "application/vnd.oasis.opendocument.text"
      }]
   }
 
 The ``nacl_modules`` attribute is optional---specify this attribute only if
 you want Chrome to use a Native Client module to display a particular type of
 content.