Minor cleanups for SDK devsite docs.

native_client_sdk/src/doc/devguide/distributing.rst

 ====================================
 Distributing Your Application (NaCl)
 ====================================
 
 .. {% setvar pepperversion %}pepper28{% endsetvar %}
 .. {% include "native-client/_local_variables.html" %}
 
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
@@ skipping 127 matching lines @@
 Here is how to use this feature:
 
 1. Create a directory called ``_platform_specific``.
    Put this directory at the same level where your CWS manifest file,
    ``manifest.json``, is located.
 
 2. Create a subdirectory for each specific architecture that you support,
    and add the files for each architecture in the relevant subdirectory.
 
    Here is a sample app directory structure:
-   
+
    .. naclcode::
-      :prettyprint: 0
+     :prettyprint: 0
 
-         |-- my_app_directory/
-         |       |-- manifest.json
-         |       |-- my_app.html
-         |       |-- my_module.nmf
-         |       +-- css/
-         |       +-- images/
-         |       +-- scripts/
-         |       |-- **_platform_specific/**
-         |       |       |-- x86-64/
-         |       |       |       |-- my_module_x86_64.nexe
-         |       |       |-- x86-32/
-         |       |       |       |-- my_module_x86_32.nexe
-         |       |       |-- arm/
-         |       |       |       |-- my_module_arm.nexe
-         |       |       |-- all/
-         |       |       |       |-- my_module_x86_64.nexe
-         |       |       |       |-- my_module_x86_64.nexe
-         |       |       |       |-- my_module_x86_32.nexe
-   
+     |-- my_app_directory/
+     |       |-- manifest.json
+     |       |-- my_app.html
+     |       |-- my_module.nmf
+     |       +-- css/
+     |       +-- images/
+     |       +-- scripts/
+     |       |-- **_platform_specific/**
+     |       |       |-- x86-64/
+     |       |       |       |-- my_module_x86_64.nexe
+     |       |       |-- x86-32/
+     |       |       |       |-- my_module_x86_32.nexe
+     |       |       |-- arm/
+     |       |       |       |-- my_module_arm.nexe
+     |       |       |-- all/
+     |       |       |       |-- my_module_x86_64.nexe
+     |       |       |       |-- my_module_x86_64.nexe
+     |       |       |       |-- my_module_x86_32.nexe
+
    Please note a few important points about the app directory structure:
 
    * The architecture-specific subdirectories:
 
      * can have arbitrary names;
      * must be directly under the ``_platform_specific`` directory; and
      * must be listed in the CWS manifest file (see step 3 below).
 
    * You can include a fallback subdirectory that provides a download package
      with all the architecture-specific files.  (In the example above this
@@ skipping 25 matching lines @@
    +----------------------+---------------------------------------+
    | ``sub_package_path`` | the path of the directory (starting   |
    |                      | with ``_platform_specific``) that     |
    |                      | contains the files for the designated |
    |                      | NaCl architecture                     |
    +----------------------+---------------------------------------+
 
    Here is a sample ``manifest.json`` file:
 
    .. naclcode::
-      :prettyprint: 0
+     :prettyprint: 0
 
-      {
-        "name": "My Reminder App",
-        "description": "A reminder app that syncs across Chrome browsers.",
-        "manifest_version": 2,
-        "minimum_chrome_version": "28",
-        "offline_enabled": true,
-        "version": "0.3",
-        "permissions": [
-          {"fileSystem": ["write"]},
-          "alarms",
-          "storage"
-        ],
-        "app": {
-          "background": {
-            "scripts": ["scripts/background.js"]
-          }
-        },
-        "icons": {
-          "16": "images/icon-16x16.png",
-          "128": "images/icon-128x128.png"
-        },
-        **"platforms": [
-          {
-            "nacl_arch": "x86-64",
-            "sub_package_path": "_platform_specific/x86-64/"
-          },
-          {
-            "nacl_arch": "x86-32",
-            "sub_package_path": "_platform_specific/x86-32/"
-          },
-          {
-            "nacl_arch": "arm",
-            "sub_package_path": "_platform_specific/arm/"
-          },
-          {
-            "sub_package_path": "_platform_specific/all/"
-          }
-        ]**
-      }
+     {
+       "name": "My Reminder App",
+       "description": "A reminder app that syncs across Chrome browsers.",
+       "manifest_version": 2,
+       "minimum_chrome_version": "28",
+       "offline_enabled": true,
+       "version": "0.3",
+       "permissions": [
+         {"fileSystem": ["write"]},
+         "alarms",
+         "storage"
+       ],
+       "app": {
+         "background": {
+           "scripts": ["scripts/background.js"]
+         }
+       },
+       "icons": {
+         "16": "images/icon-16x16.png",
+         "128": "images/icon-128x128.png"
+       },
+       **"platforms": [
+         {
+           "nacl_arch": "x86-64",
+           "sub_package_path": "_platform_specific/x86-64/"
+         },
+         {
+           "nacl_arch": "x86-32",
+           "sub_package_path": "_platform_specific/x86-32/"
+         },
+         {
+           "nacl_arch": "arm",
+           "sub_package_path": "_platform_specific/arm/"
+         },
+         {
+           "sub_package_path": "_platform_specific/all/"
+         }
+       ]**
+     }
 
    Note the last entry in the CWS manifest file above, which specifies a
    ``sub_package_path`` without a corresponding ``nacl_arch``. This entry
    identifies the fallback directory, which is included in the download
    package if the user architecture does not match any of the listed NaCl
    architectures, or if the user is using an older version of Chrome that
    does not support multi-platform zip files.
 
 4. Modify your application as necessary so that it uses the files for the
    correct user architecture.
@@ skipping 20 matching lines @@
 * 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/"
-     }
+    "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.
 * You can place your application in the Google Web Store with access only to
   certain people for testing. See
   `Publishing to test accounts </chrome/web-store/docs/publish#testaccounts>`_
@@ skipping 76 matching lines @@
   your application is a Native Client application that only works with the
   Chrome browser. Also make sure to identify the 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
+    :prettyprint: 0
 
-     "launch": {
-       "web_url": "http://mail.google.com/mail/"
-     }
+    "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.
 
 * You can place your application in the Google Web Store with access only to
   certain people for testing.  See
   `Publishing to test accounts </chrome/web-store/docs/publish#testaccounts>`_
   for more information.
 
 Additional considerations
 =========================
 
 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
 MIME type:
 
 .. naclcode::
-   :prettyprint: 0
+  :prettyprint: 0
 
-   {
-      "name": "My Native Client Spreadsheet Viewer",
-      "version": "0.1",
-      "description": "Open spreadsheets right in your browser.",
-      **"nacl_modules": [{
-         "path": "SpreadsheetViewer.nmf",
-         "mime_type": "application/vnd.oasis.opendocument.spreadsheet"
-      }]**
-   }
+  {
+     "name": "My Native Client Spreadsheet Viewer",
+     "version": "0.1",
+     "description": "Open spreadsheets right in your browser.",
+     **"nacl_modules": [{
+        "path": "SpreadsheetViewer.nmf",
+        "mime_type": "application/vnd.oasis.opendocument.spreadsheet"
+     }]**
+  }
 
 The value of "path" is the location of a Native Client manifest file (.nmf)
 within the application directory. For more information on Native Client
 manifest files, see
 `Files in a Native Client application </native-client/overview#application-files>`_.
 
 The value of "mime_type" is a specific MIME type that you want the Native
 Client module to handle. Each MIME type can be associated with only one .nmf
 file, but a single .nmf file might handle multiple MIME types. The following
 example shows an extension with two .nmf files that handle three MIME types.
 
 .. naclcode::
-   :prettyprint: 0
+  :prettyprint: 0
 
-   {
-      "name": "My Native Client Spreadsheet and Document Viewer",
-      "version": "0.1",
-      "description": "Open spreadsheets and documents right in your browser.",
-      "nacl_modules": [{
+  {
+     "name": "My Native Client Spreadsheet and Document Viewer",
+     "version": "0.1",
+     "description": "Open spreadsheets and documents right in your browser.",
+     "nacl_modules": [{
+       "path": "SpreadsheetViewer.nmf",
+       "mime_type": "application/vnd.oasis.opendocument.spreadsheet"
+     },
+     {
         "path": "SpreadsheetViewer.nmf",
-        "mime_type": "application/vnd.oasis.opendocument.spreadsheet"
-      },
-      {
-         "path": "SpreadsheetViewer.nmf",
-         "mime_type": "application/vnd.oasis.opendocument.spreadsheet-template"
-      },
-      {
-         "path": "DocumentViewer.nmf",
-         "mime_type": "application/vnd.oasis.opendocument.text"
-      }]
-   }
+        "mime_type": "application/vnd.oasis.opendocument.spreadsheet-template"
+     },
+     {
+        "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.
 
 Using CWS inline install
 ------------------------
 
 Once you've published an application, you may be wondering how users will find
 and install the application. For users who browse the Chrome Web Store and find
 your application, installing the application is a simple one-click process.
 However, if a user is already on your site, it can be cumbersome for them to
 complete the installation---they would need to navigate away from your site
 to the CWS, complete the installation process, and then return to your site. To
 address this issue, you can initiate installation of applications "inline" from
 your site---the applications are still hosted in the Chrome Web Store, but
 users no longer have to leave your site to install them. See
 `Using Inline Installation </chrome/web-store/docs/inline_installation>`_
 for information on how to use this feature.
 
 Monetizing applications and extensions
 --------------------------------------
 
 Google provides three primary monetization options for Native Client
 applications: in-app payments, one-time charges, and subscriptions.  Refer to
 `Monetizing Your App </chrome/web-store/docs/money>`_
 to learn about these options. The
 `Chrome Web Store Overview </chrome/web-store/docs/>`_
 also has information on different approaches to charging for your application.