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

native_client_sdk/doc_generated/reference/nacl-manifest-format.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="native-client-manifest-nmf-format">
 <h1 id="native-client-manifest-nmf-format">Native Client Manifest (nmf) Format</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
 <li><a class="reference internal" href="#field-summary" id="id2">Field summary</a></li>
 <li><p class="first"><a class="reference internal" href="#field-details" id="id3">Field details</a></p>
 <ul class="small-gap">
@@ skipping 111 matching lines @@
     &quot;main.nexe&quot;: {
       &quot;x86-32&quot;: { &quot;url&quot;: &quot;url_to_x86_32_nexe&quot; },
       &quot;x86-64&quot;: { &quot;url&quot;: &quot;url_to_x86_64_nexe&quot; }
     },
     // ...
   }
 }
 </pre>
 </section></section><section id="files">
 <h3 id="files">files</h3>
-<p>The <code>files</code> 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
-<a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_u_r_l_loader">URL Loader interfaces</a>
-to load resources instead). However, the <code>files</code> manifest field
-is important for dynamically linked executables, which must
-load files before PPAPI is initialized. The <code>files</code> 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
-(<code>.so</code>) for that architecture may be found.</p>
+<p>The <code>files</code> 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 <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader">URL Loader interfaces</a> to load resources
+instead). However, the <code>files</code> manifest field is important for dynamically
+linked executables, which must load files before PPAPI is initialized. The
+<code>files</code> 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 (<code>.so</code>) for that
+architecture may be found.</p>
 <p>Since <code>program</code> is used to refer to the dynamic linker that comes
 with the NaCl port of glibc, the main program is specified in the
 <code>files</code> dictionary. The main program is specified under the
 <code>&quot;main.nexe&quot;</code> field of the <code>files</code> dictionary.</p>
 <pre class="prettyprint">
 {
   &quot;program&quot;: {
     &quot;x86-64&quot;: {&quot;url&quot;: &quot;lib64/runnable-ld.so&quot;},
     &quot;x86-32&quot;: {&quot;url&quot;: &quot;lib32/runnable-ld.so&quot;}
   },
@@ skipping 86 matching lines @@
 inline with a data URI can help reduce the amount of network traffic
 required to load the Native Client application.</p>
 </section><section id="url-resolution">
 <span id="nmf-url-resolution"></span><h3 id="url-resolution"><span id="nmf-url-resolution"></span>URL resolution</h3>
 <p>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.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}