[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/src/doc/devguide/distributing.rst

 .. _distributing:
 
 #############################
 Distributing Your Application
 #############################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 This document describes how to distribute Portable Native Client applications
 on the web, and Native Client applications through the
-`Chrome Web Store </chrome/web-store/docs/>`_ (CWS).
+`Chrome Web Store </webstore>`_ (CWS).
 
 Portable Native Client
 ======================
 
 Portable Native Client is enabled by default for web pages, so no separate
 distribution step is requred. Making PNaCl a part of your web application is as
 simple as embedding a manifest file that points to a **pexe**. See the
 :doc:`technical overview <../overview>` for more details.
 
 .. image:: /images/nacl-in-a-web-app.png
@@ skipping 11 matching lines @@
 NaCl modules are only allowed for applications distributed through the `Chrome
 Web Store (CWS) <https://chrome.google.com/webstore/category/apps>`_
 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 <https://developers.google.com/chrome/web-store/docs/>`_
-* `Choosing an App Type <https://developers.google.com/chrome/web-store/docs/choosing>`_
-* `Getting started with packaged apps <http://developer.chrome.com/apps/about_apps.html>`_
+* `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>`_
-* `Chrome extensions <http://developer.chrome.com/extensions/index.html>`_
+* `Chrome extensions </extensions>`_
 
 In this document, we'll focus only on distribution issues specific to
 applications that contain NaCl modules.
 
 .. _distributing_packaged:
 
 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 application files. Refer to
-`Packaged Apps <https://developer.chrome.com/apps/about_apps.html>`_
+`Packaged Apps </apps/about_apps>`_
 for more information about creating a packaged application.
 
 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
@@ skipping 140 matching lines @@
    ``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.
 
 #. Modify your application as necessary so that it uses the files for the
    correct user architecture.
 
    To reference architecture-specific files, use the JavaScript API
-   `chrome.runtime.getPlatformInfo() <http://developer.chrome.com/trunk/extensions/runtime.html#method-getPlatformInfo>`_.
+   `chrome.runtime.getPlatformInfo() </extensions/runtime.html#method-getPlatformInfo>`_.
    As an example, if you have architecture-specific files in the directories
    ``x86-64``, ``x86-32``, and ``arm``, you can use the following JavaScript
    code to create a path for the files:
 
    .. naclcode::
 
       function getPath(name) {
         return '_platform_specific/' +
           chrome.runtime.getPlatformInfo().nacl_arch +
           '/' + name;
@@ skipping 22 matching lines @@
       "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 <https://developers.google.com/chrome/web-store/docs/publish>`_
-  for more information.
+  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
 ------------------
 
@@ skipping 55 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.