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

native_client_sdk/src/doc/devguide/coding/url-loading.rst

 .. _devguide-coding-url-loading:
 
 ###########
 URL Loading
 ###########
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Introduction
 ============
 
 This chapter describes how to use the `URLLoader API
-<https://developers.google.com/native-client/peppercpp/classpp_1_1_u_r_l_loader>`_
-to load resources such as images and sound files from a server into your
-application.
+</native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader>`_ to load resources
+such as images and sound files from a server into your application.
 
 The example discussed in this chapter is included in the SDK in the directory
 ``examples/api/url_loader``.
 
 Reference information
 =====================
 
 For reference information related to loading data from URLs, see the
 following documentation:
 
-* `url_loader.h
-  <https://developers.google.com/native-client/peppercpp/url__loader_8h>`_ -
-  Contains ``URLLoader`` class for loading data from URLs
+* `url_loader.h </native-client/pepper_stable/cpp/url__loader_8h>`_ - Contains
+  ``URLLoader`` class for loading data from URLs
 * `url_request_info.h
-  <https://developers.google.com/native-client/peppercpp/url__request__info_8h>`_
-  - Contains ``URLRequest`` class for creating and manipulating URL requests
+  </native-client/pepper_stable/cpp/url__request__info_8h>`_ - Contains
+  ``URLRequest`` class for creating and manipulating URL requests
 * `url_response_info.h
-  <https://developers.google.com/native-client/peppercpp/url__response__info_8h>`_
-  - Contains ``URLResponse`` class for examaning URL responses
+  </native-client/pepper_stable/cpp/url__response__info_8h>`_ - Contains
+  ``URLResponse`` class for examaning URL responses
 
 Background
 ==========
 
 When a user launches your Native Client web application, Chrome downloads and
 caches your application's HTML file, manifest file (.nmf), and Native Client
 module (.pexe or .nexe). If your application needs additional assets, such as
 images and sound files, it must explicitly load those assets. You can use the
 Pepper APIs described in this chapter to load assets from a URL into your
 application.
 
 After you've loaded assets into your application, Chrome will cache those
 assets. To avoid being at the whim of the Chrome cache, however, you may want
 to use the `Pepper FileIO API
-<https://developers.google.com/native-client/peppercpp/classpp_1_1_file_i_o>`_
-to write those assets to a persistent, sandboxed location on the user's file
-system.
+</native-client/pepper_stable/cpp/classpp_1_1_file_i_o>`_ to write those assets
+to a persistent, sandboxed location on the user's file system.
 
 The ``url_loader`` example
 ==========================
 
 The SDK includes an example called ``url_loader`` demonstrating downloading
 files from a server. This example has these primary files:
 
 * ``index.html`` - The HTML code that launches the Native Client module.
 * ``example.js`` - The JavaScript file for index.html. It has code that sends
   a PostMessage request to the Native Client module when the "Get URL" button
@@ skipping 179 matching lines @@
 or there is an error (less than -1). ``OnRead`` is called in the event of an
 error or ``PP_OK``.
 
 Displaying a result
 -------------------
 
 OnRead calls ``ReportResultAndDie`` when either an error or ``PP_OK`` is
 returned to indicate streaming of file is complete. ``ReportResultAndDie`` then
 calls ``ReportResult,`` which calls ``PostMessage`` to send the result back to
 the HTML page.