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

native_client_sdk/src/doc/devguide/coding/application-structure.rst

 .. _devcycle-application-structure:
 
 #####################
 Application Structure
 #####################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 72 matching lines @@
 .. _manifest_file:
 
 Manifest Files
 ==============
 
 Native Client applications have two types of manifest files: a Chrome Web Store
 manifest file and a Native Client manifest file.
 
 A **Chrome Web Store manifest file** is a file with information about a web
 application that is published in the Chrome Web Store. This file, named
-``manifest.json``, is required for applications that are published in the Chrome
-Web Store. For more information about this file see :doc:`Distributing Your
-Application <../distributing>`.  and the `Chrome Web Store manifest file format
-<http://code.google.com/chrome/extensions/manifest.html>`_.
+``manifest.json``, is required for applications that are published in the
+Chrome Web Store. For more information about this file see :doc:`Distributing
+Your Application <../distributing>`.  and the `Chrome Web Store manifest file
+format </extensions/manifest>`_.
 
 A **Native Client manifest file** is a file that specifies which Native Client
 module (executable) to load. For PNaCl it specifies a single portable
 executable; otherwise it specifies one for each of the supported end-user
 computer architectures (for example x86-32, x86-64, or ARM). This file is
 required for all Native Client applications. The extension for this file is
 .nmf.
 
 Manifest files for applications that use PNaCl are simple. Here is the manifest
 for the hello world example:
@@ skipping 139 matching lines @@
 leaves the web page, or the NaCl module's ``<embed>`` is otherwise destroyed.
 If the NaCl module does call the ``exit()`` function, the instance will
 issue a ``crash`` event
 :doc:`which can be handled in Javascript<progress-events>`.
 
 While the ``CreateModule()`` factory function, the ``Module`` class, and the
 ``Instance`` class are required for a Native Client application, the code
 samples shown above don't actually do anything. Subsequent chapters in the
 Developer's Guide build on these code samples and add more interesting
 functionality.