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

native_client_sdk/src/doc/devguide/tutorial/tutorial-part2.rst

 .. _tutorial2:
 
 ######################################
 C++ Tutorial: Getting Started (Part 2)
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Overview
 ========
 
 This tutorial shows how to convert the finished PNaCl web application from
 :doc:`Part 1 <tutorial-part1>` to use the Native Client SDK build system and
-common JavaScript files. It also demonstrates some techniques to make your
-web application `Content Security Policy (CSP)-compliant
-<http://developer.chrome.com/apps/contentSecurityPolicy.html>`, which is
-necessary for `Chrome Apps
-<https://developer.chrome.com/apps/about_apps.html>`_.
+common JavaScript files. It also demonstrates some techniques to make your web
+application `Content Security Policy (CSP)-compliant
+</apps/contentSecurityPolicy>`_, which is necessary for `Chrome Apps
+</apps/about_apps>`_.
 
 Using the Native Client SDK build system makes it easy to build with all of the
 SDK toolchains, and switch between the Debug and Release configurations. It
 also simplifies the makefiles for your project, as we'll see in the next
 section. Finally, it adds some useful commands for :ref:`running
 <running_the_sdk_examples>` and :ref:`debugging <debugging_the_sdk_examples>`
 your application.
 
 The finished code for this example can be found in the
 ``pepper_$(VERSION)/getting_started/part2`` directory in the Native Client SDK
@@ skipping 112 matching lines @@
   the target ``part2``, which will generate an executable called
   ``part2.pexe`` for PNaCl. For NaCl toolchains, the executable's file name
   will be given a suffix for its architecture. For example, the ARM executable
   is called ``part2_arm.nexe``.
 
 LIBS
   A list of libraries that this executable needs to link against. The library
   search path is already set up to only look in the directory for the current
   toolchain and architecture. In this example, we link against ``ppapi_cpp``
   and ``ppapi``. ``ppapi_cpp`` is needed to use the `Pepper C++ interface
-  <https://developers.google.com/native-client/peppercpp/>`_. ``ppapi`` is
-  needed for communicating with the browser.
+  </native-client/pepper_stable/cpp/>`_. ``ppapi`` is needed for communicating
+  with the browser.
 
 CFLAGS
   A list of extra flags to pass to the compiler. In this example, we pass
   ``-Wall``, which turns on all warnings.
 
 LDFLAGS
   A list of additional flags to pass to the linker. This example does not need
   any special linker flags, so this variable is omitted.
 
 SOURCES
@@ skipping 58 matching lines @@
 Finally, the NMF rule generates a NaCl manifest file (``.nmf``) that references
 each executable generated in the previous step:
 
 .. naclcode::
 
     $(eval $(call NMF_RULE,$(TARGET),))
 
 Making index.html work for Chrome Apps
 ======================================
 
-This section describes the changes necessary to make the HTML and JavaScript
-in part1 CSP-compliant. This is required if you want to build a `Chrome App
-<https://developer.chrome.com/apps/about_apps.html>`_, but is not necessary
-if you want to use PNaCl on the open web.
+This section describes the changes necessary to make the HTML and JavaScript in
+part1 CSP-compliant. This is required if you want to build a `Chrome App
+</apps/about_apps>`_, but is not necessary if you want to use PNaCl on the open
+web.
 
 CSP rules
 ---------
 
-`Chrome Apps CSP
-<http://developer.chrome.com/apps/contentSecurityPolicy.html#what>`_
-restricts you from doing the following:
+`Chrome Apps CSP </apps/contentSecurityPolicy#what>`_ restricts you from doing
+the following:
 
 * You can’t use inline scripting in your Chrome App pages. The restriction
   bans both ``<script>`` blocks and event handlers (``<button onclick="...">``).
 * You can’t reference any external resources in any of your app files (except
   for video and audio resources). You can’t embed external resources in an
   iframe.
 * You can’t use string-to-JavaScript methods like ``eval()`` and ``new
   Function()``.
 
 Making index.html CSP-compliant
@@ skipping 236 matching lines @@
       // postMessage sends a message to it.
       common.naclModule.postMessage('hello');
     }
 
     // This function is called by common.js when a message is received from the
     // NaCl module.
     function handleMessage(message) {
       var logEl = document.getElementById('log');
       logEl.textContent += message.data;
     }