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

Also change links to http://developer.chrome.com/foo/bar -> /foo/bar, and some
other manual fixes.

BUG=none
R=jfb@chromium.org

Review URL: https://codereview.chromium.org/254033002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@267327 0039d316-1c4b-4281-b951-d872f2087c98

6 files changed, 83 insertions, 90 deletions

diff --git a/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html b/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html
index 0e7cdb1..f633cb4 100644
--- a/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html
+++ b/native_client_sdk/doc_generated/devguide/coding/3D-graphics.html
@@ -94,10 +94,9 @@ than or equal to the number of simultaneous textures you need.</li>
 </ul>
 </section></section><section id="vetting-the-driver-in-the-chrome-web-store">
 <h3 id="vetting-the-driver-in-the-chrome-web-store">Vetting the driver in the Chrome Web Store</h3>
-<p>If you choose to place your application in the <a class="reference external" href="https://developers.google.com/chrome/web-store/docs/">Chrome Web
-Store</a>, its Web Store
-<a class="reference external" href="http://code.google.com/chrome/extensions/manifest.html">manifest file</a> can
-include the <code>webgl</code> feature in the requirements parameter. It looks like this:</p>
+<p>If you choose to place your application in the <a class="reference external" href="/webstore">Chrome Web Store</a>,
+its Web Store <a class="reference external" href="/extensions/manifest">manifest file</a> can include the <code>webgl</code>
+feature in the requirements parameter. It looks like this:</p>
 <pre class="prettyprint">
 &quot;requirements&quot;: {
   &quot;3D&quot;: {
@@ -119,7 +118,7 @@ the install page, and if there is a problem, the browser will display the
 message &#8220;This application is not supported on this computer. Installation has
 been disabled.&#8221;</p>
 <p>The manifest-based check applies only to downloads directly from the Chrome Web
-Store. It is not performed when an application is loaded via <a class="reference external" href="https://developers.google.com/chrome/web-store/docs/inline_installation">inline
+Store. It is not performed when an application is loaded via <a class="reference external" href="/webstore/inline_installation">inline
 installation</a>.</p>
 </section><section id="what-to-do-when-there-are-problems">
 <h3 id="what-to-do-when-there-are-problems">What to do when there are problems</h3>
@@ -214,11 +213,11 @@ hardware support exists). See <a class="reference external" href="http://www.alt
 for more info.</p>
 </section><section id="use-the-pepper-api">
 <h3 id="use-the-pepper-api">Use the Pepper API</h3>
-<p>Your code can call the Pepper <a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___open_g_l_e_s2">PPB_OpenGLES2</a>
-API directly, as with any Pepper interface. When you write in this way, each
-invocation of an OpenGL ES 2.0 function must begin with a reference to the
-Pepper interface, and the first argument is the graphics context. To invoke the
-function <code>glCompileShader</code>, your code might look like:</p>
+<p>Your code can call the Pepper PPB_OpenGLES2 API directly, as with any Pepper
+interface. When you write in this way, each invocation of an OpenGL ES 2.0
+function must begin with a reference to the Pepper interface, and the first
+argument is the graphics context. To invoke the function <code>glCompileShader</code>,
+your code might look like:</p>
 <pre class="prettyprint">
 ppb_g3d_interface-&gt;CompileShader(graphicsContext, shader);
 </pre>
@@ -244,8 +243,8 @@ callbacks, for example), the Chrome main thread will block. This means that
 lengthy operations on the Native Client thread can steal cycles from Chrome, and
 performing blocking operations on the Native Client thread can bring your app to
 a standstill.</p>
-<p>Native Client uses callback functions to synchronize the main threads of the two
-processes. Only certain Pepper functions use callbacks; <a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___graphics3_d__1__0#a293c6941c0da084267ffba3954793497">SwapBuffers</a>
+<p>Native Client uses callback functions to synchronize the main threads of the
+two processes. Only certain Pepper functions use callbacks; <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___graphics3_d__1__0#a293c6941c0da084267ffba3954793497">SwapBuffers</a>
 is one.</p>
 </section><section id="swapbuffers-and-its-callback-function">
 <h3 id="swapbuffers-and-its-callback-function"><code>SwapBuffers</code> and its callback function</h3>
diff --git a/native_client_sdk/doc_generated/devguide/coding/audio.html b/native_client_sdk/doc_generated/devguide/coding/audio.html
index b9003e0..8d06f97 100644
--- a/native_client_sdk/doc_generated/devguide/coding/audio.html
+++ b/native_client_sdk/doc_generated/devguide/coding/audio.html
@@ -43,11 +43,11 @@ for the sine wave and click buttons to start and stop audio playback.</p>
 <p>For reference information related to the Pepper audio API, see the following
 documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_audio_config">pp::AudioConfig class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_audio">pp::Audio class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/audio__config_8h">audio_config.h</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/audio_8h">audio.h</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/pepperc/group___enums.html#gaee750c350655f2fb0fe04c04029e0ff8">PP_AudioSampleRate</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_audio_config">pp::AudioConfig class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_audio">pp::Audio class</a></li>
+<li><a class="reference external" href="/native-client/pepper_cpp/audio__config_8h">audio_config.h</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/audio_8h">audio.h</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/group___enums#gaee750c350655f2fb0fe04c04029e0ff8">PP_AudioSampleRate</a></li>
 </ul>
 </section><section id="about-the-pepper-audio-api">
 <h2 id="about-the-pepper-audio-api">About the Pepper audio API</h2>
diff --git a/native_client_sdk/doc_generated/devguide/coding/file-io.html b/native_client_sdk/doc_generated/devguide/coding/file-io.html
index 590bd63..6cb5734 100644
--- a/native_client_sdk/doc_generated/devguide/coding/file-io.html
+++ b/native_client_sdk/doc_generated/devguide/coding/file-io.html
@@ -37,8 +37,8 @@
 
 </div><section id="introduction">
 <h2 id="introduction">Introduction</h2>
-<p>This chapter describes how to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_file_i_o">FileIO API</a>
-to read and write files using a local secure data store.</p>
+<p>This chapter describes how to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_file_i_o">FileIO API</a> to read and write
+files using a local secure data store.</p>
 <p>You might use the File IO API with the URL Loading APIs to create an overall
 data download and caching solution for your NaCl applications. For example:</p>
 <ol class="arabic simple">
@@ -57,12 +57,12 @@ application.</li>
 <h2 id="reference-information">Reference information</h2>
 <p>For reference information related to FileIO, see the following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__io_8h">file_io.h</a> - API
-to create a FileIO object</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__ref_8h">file_ref.h</a> - API
-to create a file reference or &#8220;weak pointer&#8221; to a file in a file system</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__system_8h">file_system.h</a> -
-API to create a file system associated with a file</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__io_8h">file_io.h</a> - API to create a
+FileIO object</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__ref_8h">file_ref.h</a> - API to create
+a file reference or &#8220;weak pointer&#8221; to a file in a file system</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__system_8h">file_system.h</a> - API to
+create a file system associated with a file</li>
 </ul>
 </section><section id="local-file-i-o">
 <h2 id="local-file-i-o">Local file I/O</h2>
@@ -77,11 +77,10 @@ use, other than the actual space available on the local drive.</p>
 <section id="enabling-local-file-i-o">
 <span id="enabling-file-access"></span><span id="quota-management"></span><h3 id="enabling-local-file-i-o"><span id="enabling-file-access"></span><span id="quota-management"></span>Enabling local file I/O</h3>
 <p>The easiest way to enable the writing of persistent local data is to include
-the <a class="reference external" href="http://developer.chrome.com/extensions/declare_permissions.html#unlimitedStorage">unlimitedStorage permission</a>
-in your Chrome Web Store manifest file. With this permission you can use the
-Pepper FileIO API without the need to request disk space at run time. When
-the user installs the app Chrome displays a message announcing that the app
-writes to the local disk.</p>
+the <a class="reference external" href="/extensions/declare_permissions#unlimitedStorage">unlimitedStorage permission</a> in your Chrome Web Store
+manifest file. With this permission you can use the Pepper FileIO API without
+the need to request disk space at run time. When the user installs the app
+Chrome displays a message announcing that the app writes to the local disk.</p>
 <p>If you do not use the <code>unlimitedStorage</code> permission you must include
 JavaScript code that calls the <a class="reference external" href="http://updates.html5rocks.com/2011/11/Quota-Management-API-Fast-Facts">HTML5 Quota Management API</a> to
 explicitly request local disk space before using the FileIO API. In this case
diff --git a/native_client_sdk/doc_generated/devguide/coding/message-system.html b/native_client_sdk/doc_generated/devguide/coding/message-system.html
index 5f8c8e7..87f84b3 100644
--- a/native_client_sdk/doc_generated/devguide/coding/message-system.html
+++ b/native_client_sdk/doc_generated/devguide/coding/message-system.html
@@ -48,22 +48,22 @@ the <code>/getting_started/part2</code> directory in the Native Client SDK downl
 <p>For reference information related to the Pepper messaging API, see the
 following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_instance">pp::Instance class</a> HandleMessage(), PostMessage())</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_module">pp::Module class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var">pp::Var class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance class</a>
+HandleMessage(), PostMessage())</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var class</a></li>
 </ul>
 </section><section id="introduction-to-the-messaging-system">
 <h2 id="introduction-to-the-messaging-system">Introduction to the messaging system</h2>
-<p>Native Client modules and JavaScript communicate by sending messages
-to each other. The most basic form of a message is a string.  Messages
-support many JavaScript types, including ints, arrays, array buffers,
-and dictionaries (see <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var">pp::Var</a>,
-<a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var_array_buffer">pp:VarArrayBuffer</a>,
-and the general <a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___messaging__1__0">messaging system documentation</a>).
-It&#8217;s up to you to decide on the type of message and define how to
-process the messages on both the JavaScript and Native Client
-side. For the &#8220;Hello, World&#8221; example, we will work with string-typed
-messages only.</p>
+<p>Native Client modules and JavaScript communicate by sending messages to each
+other. The most basic form of a message is a string.  Messages support many
+JavaScript types, including ints, arrays, array buffers, and dictionaries (see
+<a class="reference external" href="h/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var</a>,
+<a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var_array_buffer">pp:VarArrayBuffer</a>, and the
+general <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___messaging__1__0">messaging system documentation</a>).  It&#8217;s up to
+you to decide on the type of message and define how to process the messages on
+both the JavaScript and Native Client side. For the &#8220;Hello, World&#8221; example, we
+will work with string-typed messages only.</p>
 <p>When JavaScript posts a message to the Native Client module, the
 Pepper <code>HandleMessage()</code> function is invoked on the module
 side. Similarly, the Native Client module can post a message to
@@ -172,11 +172,10 @@ function moduleDidLoad() {
 by the JavaScript.</li>
 <li>Processes incoming messages. This example simply checks that JavaScript
 has sent a &#8220;hello&#8221; message and not some other message.</li>
-<li>Calls <code>PostMessage()</code> to send an acknowledgement back to the
-JavaScript code.  The acknowledgement is a string in the form of a <code>Var</code>
-that the JavaScript code can process.  In general, a <code>pp::Var</code> can be
-several JavaScript types, see the
-<a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___messaging__1__0">messaging system documentation</a>.</li>
+<li>Calls <code>PostMessage()</code> to send an acknowledgement back to the JavaScript
+code.  The acknowledgement is a string in the form of a <code>Var</code> that the
+JavaScript code can process.  In general, a <code>pp::Var</code> can be several
+JavaScript types, see the <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___messaging__1__0">messaging system documentation</a>.</li>
 </ol>
 <pre class="prettyprint">
 class HelloTutorialInstance : public pp::Instance {
diff --git a/native_client_sdk/doc_generated/devguide/coding/url-loading.html b/native_client_sdk/doc_generated/devguide/coding/url-loading.html
index e5d985f..47b6e79 100644
--- a/native_client_sdk/doc_generated/devguide/coding/url-loading.html
+++ b/native_client_sdk/doc_generated/devguide/coding/url-loading.html
@@ -23,9 +23,8 @@
 
 </div><section id="introduction">
 <h2 id="introduction">Introduction</h2>
-<p>This chapter describes how to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_u_r_l_loader">URLLoader API</a>
-to load resources such as images and sound files from a server into your
-application.</p>
+<p>This chapter describes how to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader">URLLoader API</a> to load resources
+such as images and sound files from a server into your application.</p>
 <p>The example discussed in this chapter is included in the SDK in the directory
 <code>examples/api/url_loader</code>.</p>
 </section><section id="reference-information">
@@ -33,12 +32,12 @@ application.</p>
 <p>For reference information related to loading data from URLs, see the
 following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/url__loader_8h">url_loader.h</a> -
-Contains <code>URLLoader</code> class for loading data from URLs</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/url__request__info_8h">url_request_info.h</a>
-- Contains <code>URLRequest</code> class for creating and manipulating URL requests</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/url__response__info_8h">url_response_info.h</a>
-- Contains <code>URLResponse</code> class for examaning URL responses</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/url__loader_8h">url_loader.h</a> - Contains
+<code>URLLoader</code> class for loading data from URLs</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/url__request__info_8h">url_request_info.h</a> - Contains
+<code>URLRequest</code> class for creating and manipulating URL requests</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/url__response__info_8h">url_response_info.h</a> - Contains
+<code>URLResponse</code> class for examaning URL responses</li>
 </ul>
 </section><section id="background">
 <h2 id="background">Background</h2>
@@ -50,9 +49,8 @@ Pepper APIs described in this chapter to load assets from a URL into your
 application.</p>
 <p>After you&#8217;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 <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_file_i_o">Pepper FileIO API</a>
-to write those assets to a persistent, sandboxed location on the user&#8217;s file
-system.</p>
+to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_file_i_o">Pepper FileIO API</a> to write those assets
+to a persistent, sandboxed location on the user&#8217;s file system.</p>
 </section><section id="the-url-loader-example">
 <h2 id="the-url-loader-example">The <code>url_loader</code> example</h2>
 <p>The SDK includes an example called <code>url_loader</code> demonstrating downloading
diff --git a/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html b/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
index 793e57b..8dc052a4 100644
--- a/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
+++ b/native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html
@@ -36,18 +36,16 @@ boiler plate.  The <code>pi_generator</code> example in
 change events and 2D graphics.</p>
 <section id="overview">
 <h2 id="overview">Overview</h2>
-<p>When a user interacts with the web page using a keyboard, mouse or
-some other input device, the browser generates input events.
-In a traditional web application, these input events are
-passed to and handled in JavaScript, typically through event listeners
-and event handlers. In a Native Client application, user interaction
-with an instance of a module (e.g., clicking inside the rectangle
-managed by a module) also generates input events, which are passed to
-the module. The browser also passes view change and focus events that
-affect a module&#8217;s instance to the module. Native Client modules can
-override certain functions in the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_instance">pp::Instance</a>
-class to handle input and browser events. These functions are listed in
-the table below:</p>
+<p>When a user interacts with the web page using a keyboard, mouse or some other
+input device, the browser generates input events.  In a traditional web
+application, these input events are passed to and handled in JavaScript,
+typically through event listeners and event handlers. In a Native Client
+application, user interaction with an instance of a module (e.g., clicking
+inside the rectangle managed by a module) also generates input events, which
+are passed to the module. The browser also passes view change and focus events
+that affect a module&#8217;s instance to the module. Native Client modules can
+override certain functions in the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance</a> class to handle input
+and browser events. These functions are listed in the table below:</p>
 <table border="1" class="docutils">
 <colgroup>
 </colgroup>
@@ -156,8 +154,8 @@ branches accordingly.</td>
 </tr>
 </tbody>
 </table>
-<p>These interfaces are found in the <a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_instance">pp::Instance class</a>.
-The sections below provide examples of how to handle these events.</p>
+<p>These interfaces are found in the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance class</a>.  The sections below
+provide examples of how to handle these events.</p>
 </section><section id="handling-browser-events">
 <h2 id="handling-browser-events">Handling browser events</h2>
 <section id="didchangeview">
@@ -194,8 +192,8 @@ void MouseLockInstance::DidChangeView(const pp::View&amp; view) {
 </pre>
 <p>For more information about graphics contexts and how to manipulate images, see:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_image_data">pp::ImageData class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_graphics2_d">pp::Graphics2D class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_image_data">pp::ImageData class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_graphics2_d">pp::Graphics2D class</a></li>
 </ul>
 </section><section id="didchangefocus">
 <h3 id="didchangefocus">DidChangeFocus()</h3>
@@ -236,18 +234,18 @@ class InputEventInstance : public pp::Instance {
 };
 </pre>
 <p><code>RequestInputEvents()</code> and <code>RequestFilteringInputEvents()</code> accept a
-combination of flags that identify the class of events that the
-instance is requesting to receive. Input event classes are defined in
-the <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd">PP_InputEvent_Class</a>
-enumeration in <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h">ppb_input_event.h</a>.</p>
+combination of flags that identify the class of events that the instance is
+requesting to receive. Input event classes are defined in the
+<a class="reference external" href="/native-client/pepper_stable/c/group___enums.html#gafe68e3c1031daa4a6496845ff47649cd">PP_InputEvent_Class</a>
+enumeration in <a class="reference external" href="/native-client/pepper_stable/c/ppb__input__event_8h">ppb_input_event.h</a>.</p>
 </section><section id="determining-and-branching-on-event-types">
 <h3 id="determining-and-branching-on-event-types">Determining and branching on event types</h3>
-<p>In a typical implementation, the <code>HandleInputEvent()</code> function
-determines the type of each event using the <code>GetType()</code> function found
-in the <code>InputEvent</code> class. The <code>HandleInputEvent()</code> function then uses a
-switch statement to branch on the type of input event. Input events
-are defined in the <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5">PP_InputEvent_Type</a>
-enumeration in <a class="reference external" href="https://developers.google.com/native-client/dev/pepperc/ppb__input__event_8h">ppb_input_event.h</a>.</p>
+<p>In a typical implementation, the <code>HandleInputEvent()</code> function determines the
+type of each event using the <code>GetType()</code> function found in the <code>InputEvent</code>
+class. The <code>HandleInputEvent()</code> function then uses a switch statement to
+branch on the type of input event. Input events are defined in the
+<a class="reference external" href="/native-client/pepper_stable/c/group___enums.html#gaca7296cfec99fcb6646b7144d1d6a0c5">PP_InputEvent_Type</a>
+enumeration in <a class="reference external" href="/native-client/pepper_stable/c/ppb__input__event_8h">ppb_input_event.h</a>.</p>
 <pre class="prettyprint">
 virtual bool HandleInputEvent(const pp::InputEvent&amp; event) {
   Event* event_ptr = NULL;
@@ -324,13 +322,13 @@ converted into a specific type after the event type is
 determined.  The event types handled in the example code are
 <code>MouseInputEvent</code>, <code>WheelInputEvent</code>, and <code>KeyboardInputEvent</code>.
 There are also <code>TouchInputEvents</code>.  For the latest list of event types,
-see the <a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_input_event">InputEvent documentation</a>.
+see the <a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_input_event">InputEvent documentation</a>.
 For reference information related to the these event classes, see the
 following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_mouse_input_event">pp::MouseInputEvent class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_wheel_input_event">pp::WheelInputEvent class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/dev/peppercpp/classpp_1_1_keyboard_input_event">pp::KeyboardInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_mouse_input_event">pp::MouseInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_wheel_input_event">pp::WheelInputEvent class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/c/classpp_1_1_keyboard_input_event">pp::KeyboardInputEvent class</a></li>
 </ul>
 </section><section id="threading-and-blocking">
 <h3 id="threading-and-blocking">Threading and blocking</h3>