[NaCl Docs] Remove use of hyperlink references in target URIs.

This feature requires docutils 0.11 and precise is still on 0.8:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#embedded-uris-and-aliases

R=binji@chromium.org

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

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

4 files changed, 21 insertions, 23 deletions

diff --git a/native_client_sdk/src/doc/community/security-contest/contest-announcement.rst b/native_client_sdk/src/doc/community/security-contest/contest-announcement.rst
index a11ab78..9b0ce1cd 100644
--- a/native_client_sdk/src/doc/community/security-contest/contest-announcement.rst
+++ b/native_client_sdk/src/doc/community/security-contest/contest-announcement.rst
@@ -33,8 +33,10 @@ To participate, you will need to:
   yourself (or your team)
 * `Download <http://code.google.com/p/nativeclient/wiki/Downloads?tm=2>`_
   our latest build
-* `Join <mailing_list_>`_ the Native Client discussion group
-* `Report <nacl_bugs_>`_ the exploits you find to our team
+* `Join <https://groups.google.com/group/native-client-discuss>`_ the Native
+  Client discussion group
+* `Report <https://code.google.com/p/nativeclient/issues>`_ the exploits you
+  find to our team
 
 When
 ====
diff --git a/native_client_sdk/src/doc/faq.rst b/native_client_sdk/src/doc/faq.rst
index dc7e9f5f..b615e8d 100644
--- a/native_client_sdk/src/doc/faq.rst
+++ b/native_client_sdk/src/doc/faq.rst
@@ -116,9 +116,9 @@ lower overheads whereas very branch-heavy code often performs worse.
 For details, see:
 
 * `Adapting Software Fault Isolation to Contemporary CPU Architectures
-  <sfi_paper_>`_ (PDF).
-* `Native Client: A Sandbox for Portable, Untrusted x86 Code <nacl_paper_>`_
-  (PDF).
+  <https://nativeclient.googlecode.com/svn/data/site/NaCl_SFI.pdf>`_ (PDF).
+* `Native Client: A Sandbox for Portable, Untrusted x86 Code
+  <http://research.google.com/pubs/pub34913.html>`_ (PDF).
 
 If your code isn't performing as close to native speed as you'd expect,
 :doc:`let us know <help>`!
@@ -157,7 +157,7 @@ What development environment and development operating system do you recommend?
 You can develop on Windows, Mac, or Linux, and the resulting Native
 Client or Portable Native Client application will run inside the Google
 Chrome browser on all those platforms as well as ChromeOS. You can also
-develop on ChromeOS with `Crouton`_, and we're working on
+develop on ChromeOS with Crouton_, and we're working on
 self-hosting a full development environment on Portable Native Client.
 
 Any editor+shell combination should work as well as IDEs like Eclipse,
@@ -236,7 +236,7 @@ transpile languages to C/C++ (source-to-source compilation).
 
 If you're interested in getting other languages working, please contact the
 Native Client team by way of the `native-client-discuss mailing list
-<mailing_list_>`_.
+<https://groups.google.com/group/native-client-discuss>`_.
 
 Will you only support Chrome? What about other browsers?
 --------------------------------------------------------
@@ -378,7 +378,8 @@ output.
 In addition to static analysis of untrusted code, the Native Client
 runtime also includes an outer sandbox that mediates system calls. For
 more details about both sandboxes, see `Native Client: A Sandbox for
-Portable, Untrusted x86 Code <nacl_paper_>`_ (PDF).
+Portable, Untrusted x86 Code <http://research.google.com/pubs/pub34913.html>`_
+(PDF).
 
 How does Google know that the safety measures in Native Client are sufficient?
 ------------------------------------------------------------------------------
@@ -394,7 +395,7 @@ works, including:
 Google is committed to making Native Client safer than JavaScript and
 other popular browser technologies. If you have suggestions for security
 improvements, let the team know, by way of the `native-client-discuss
-mailing list <mailing_list_>`_.
+mailing list <https://groups.google.com/group/native-client-discuss>`_.
 
 Development
 ===========
@@ -454,7 +455,7 @@ Google has ported several third-party libraries to Native Client; such
 libraries are available in the naclports_ project. We encourage you to
 contribute libraries to naclports, and/or to host your own ported
 libraries, and to `let the team know about it
-<mailing_list_>`_ when you do.
+<https://groups.google.com/group/native-client-discuss>`_ when you do.
 
 Do all the files in an application need to be served from the same domain?
 --------------------------------------------------------------------------
@@ -567,7 +568,4 @@ Here are ways to resolve some common problems that can prevent loading:
 
 .. _CORS: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
 .. _naclports: https://code.google.com/p/naclports
-.. _mailing_list: https://groups.google.com/group/native-client-discuss
-.. _nacl_paper: http://research.google.com/pubs/pub34913.html
-.. _sfi_paper: https://nativeclient.googlecode.com/svn/data/site/NaCl_SFI.pdf
 .. _Crouton: https://github.com/dnschneid/crouton
diff --git a/native_client_sdk/src/doc/help.rst b/native_client_sdk/src/doc/help.rst
index 95ad94d..68b5e21 100644
--- a/native_client_sdk/src/doc/help.rst
+++ b/native_client_sdk/src/doc/help.rst
@@ -28,9 +28,9 @@ Forums
   great resource --- check this forum first for answers to your
   questions.
 * For in-depth technical discussions: `native-client-discuss mailing
-  list <mailing_list_>`_ is a good group for detailed technical discussions
-  about bugs and other Native Client issues.
-* For announcements, follow the `native-client-announce mailing list
+  list <https://groups.google.com/group/native-client-discuss>`_ is a good
+  group for detailed technical discussions about bugs and other Native Client
+  issues.  * For announcements, follow the `native-client-announce mailing list
   <http://groups.google.com/group/native-client-announce>`_.
 * For 140 character goodness follow `@nativeclient
   <https://twitter.com/nativeclient>`_ on Twitter.
@@ -42,9 +42,10 @@ Issue tracker
 
 To report a new issue:
 
-#. Go to the `Native Client issue tracker <nacl_bugs_>`_ for a Native Client
-   bug, or the `Chromium issue tracker <chrome_bugs_>`_ for a Chrome/Chromium
-   bug.
+#. Go to the `Native Client issue tracker
+   <https://code.google.com/p/nativeclient/issues>`_ for a Native Client
+   bug, or the `Chromium issue tracker
+   <https://code.google.com/p/chromium/issues>`_ for a Chrome/Chromium bug.
 #. Before you report an issue, search to see if your issue has already
    been reported. You can add a comment to an existing issue if you have
    additional information.
@@ -61,6 +62,3 @@ To report a new issue:
    * A `Native Client + Chrome integration security issue
      <https://code.google.com/p/chromium/issues/entry?template=Security%20Bug>`_
      (only visible to the security team).
-
-.. _nacl_bugs: https://code.google.com/p/nativeclient/issues
-.. _chrome_bugs: https://code.google.com/p/chromium/issues
diff --git a/native_client_sdk/src/doc/publications-and-presentations.rst b/native_client_sdk/src/doc/publications-and-presentations.rst
index 611b1c5..ccf5dc7 100644
--- a/native_client_sdk/src/doc/publications-and-presentations.rst
+++ b/native_client_sdk/src/doc/publications-and-presentations.rst
@@ -93,7 +93,7 @@ Publications
        <http://research.google.com/pubs/author37895.html>`_
      - 19th USENIX Security Symposium, 2010, pp. 1-11
    * - `Native Client: A Sandbox for Portable, Untrusted x86 Native Code
-       <nacl_paper_>`_
+       <http://research.google.com/pubs/pub34913.html>`_
      - Bennet S. Yee, David Sehr, Greg Dardyk, `Brad Chen
        <http://research.google.com/pubs/author37895.html>`_, Robert
        Muth, Tavis Ormandy, Shiki Okasaka, Neha Narula, Nicholas