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

native_client_sdk/src/doc/reference/nacl-manifest-format.rst

 ###################################
 Native Client Manifest (nmf) Format
 ###################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Overview
@@ skipping 115 matching lines @@
         "x86-64": { "url": "url_to_x86_64_nexe" }
       },
       // ...
     }
   }
 
 
 files
 -----
 
-The ``files`` field specifies a dictionary of file resources to be 
-used by a Native Client application. This is not supported and
-not needed by Portable Native Client applications (use the PPAPI
-`URL Loader interfaces
-<https://developers.google.com/native-client/peppercpp/classpp_1_1_u_r_l_loader>`_
-to load resources instead). However, the ``files`` manifest field
-is important for dynamically linked executables, which must
-load files before PPAPI is initialized. The ``files`` dictionary
-should include the main dynamic program and its dynamic libraries.
-There should be one file entry that corresponds to each a
-dynamic library. Each file entry is a dictionary of supported architectures
-and the URLs where the appropriate Native Client shared object
-(``.so``) for that architecture may be found.
+The ``files`` field specifies a dictionary of file resources to be used by a
+Native Client application. This is not supported and not needed by Portable
+Native Client applications (use the PPAPI `URL Loader interfaces
+</native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader>`_ to load resources
+instead). However, the ``files`` manifest field is important for dynamically
+linked executables, which must load files before PPAPI is initialized. The
+``files`` dictionary should include the main dynamic program and its dynamic
+libraries.  There should be one file entry that corresponds to each a dynamic
+library. Each file entry is a dictionary of supported architectures and the
+URLs where the appropriate Native Client shared object (``.so``) for that
+architecture may be found.
 
 Since ``program`` is used to refer to the dynamic linker that comes
 with the NaCl port of glibc, the main program is specified in the
 ``files`` dictionary. The main program is specified under the
 ``"main.nexe"`` field of the ``files`` dictionary.
 
 
 .. naclcode::
 
   {
@@ skipping 105 matching lines @@
 required to load the Native Client application.
 
 .. _nmf_url_resolution:
 
 URL resolution
 --------------
 
 All URLs contained in a manifest are resolved relative to the URL of
 the manifest. If the manifest was specified as a data URI, the URLs must
 all be absolute.