docs: Fixing broken links and bad paths.
Bug: 9192223
Change-Id: Iee1dadd0a2b38a48ac0ebcbc78f87d6087e01bb1
diff --git a/src/compatibility/contact-us.jd b/src/compatibility/contact-us.jd
index 72999e6..b9e969f 100644
--- a/src/compatibility/contact-us.jd
+++ b/src/compatibility/contact-us.jd
@@ -21,11 +21,11 @@
<p>If you have questions about Android compatibility that aren't covered in
this site, you can reach us in one of a few different ways. To get the most
out of any of these options, please first read "Getting the Most from Our
-Lists" on the <a href="{/community/index.html">Community page</a></p>
+Lists" on the <a href="{@docRoot}community/index.html">Community page</a></p>
<h2 id="for-android-compatibility-definition-and-compatibility-test-suite-technical-questions">For Android Compatibility Definition and Compatibility Test Suite Technical Questions</h2>
<p>If you have questions about Android compatibility that aren't covered in this site, you can reach
us in one of a few different ways. To get the most out of any of these options, please first read "Getting the Most from Our
-Lists" on the <a href="/community/index.html">Community page</a>. If you have specific issues with the Compatibility Test Suite or the Compatibility Definition
+Lists" on the <a href="{@docRoot}community/index.html">Community page</a>. If you have specific issues with the Compatibility Test Suite or the Compatibility Definition
<a href="https://groups.google.com/forum/?fromgroups#!forum/android-compatibility">android-compatibility list.</a> is the discussion forum for you.</p>
<ul>
<li>Subscribe using Google Groups: <a href="https://groups.google.com/forum/?fromgroups#!forum/android-compatibility">android-compatibility</a></li>
@@ -37,4 +37,4 @@
<p>Finally, business inquiries about the compatibility program, including
requests to use branding elements and so on, can be sent to the address <a href="mailto:android-partnerships@google.com">android-partnerships@google.com</a>. Like
the CTS address, this address is for specific, private inquiries; general
-questions will be directed back to the android-compatibility list.</p>
\ No newline at end of file
+questions will be directed back to the android-compatibility list.</p>
diff --git a/src/compatibility/cts-development.jd b/src/compatibility/cts-development.jd
index bacbd9c..a7c5491 100644
--- a/src/compatibility/cts-development.jd
+++ b/src/compatibility/cts-development.jd
@@ -18,12 +18,12 @@
-->
<h2 id="initializing-your-repo-client">Initializing Your Repo Client</h2>
-<p>Follow the <a href="/source/downloading.html">instructions</a>
+<p>Follow the <a href="{@docRoot}source/downloading.html">instructions</a>
to get and build the Android source code but specify <code>-b android-4.2_r1</code>
when issuing the <code>repo init</code> command. This assures that your CTS
changes will be included in the next CTS release and beyond.</p>
<h2 id="setting-up-eclipse">Setting Up Eclipse</h2>
-<p>Follow the <a href="/source/using-eclipse.html">instructions</a>
+<p>Follow the <a href="{@docRoot}source/using-eclipse.html">instructions</a>
to setup Eclipse but execute the following command to generate the
<code>.classpath</code> file rather than copying the one from the development
project:</p>
@@ -104,6 +104,6 @@
<li>Fix or remove tests annotated with BrokenTest and KnownFailure.</li>
</ul>
<h2 id="submitting-your-changes">Submitting Your Changes</h2>
-<p>Follow the <a href="/source/submit-patches.html">Android Contributors' Workflow</a>
+<p>Follow the <a href="{@docRoot}source/submit-patches.html">Android Contributors' Workflow</a>
to contribute changes to CTS. A reviewer
will be assigned to your change, and your change should be reviewed shortly!</p>
diff --git a/src/compatibility/cts-intro.jd b/src/compatibility/cts-intro.jd
index 3db4b36..83f9f5f 100644
--- a/src/compatibility/cts-intro.jd
+++ b/src/compatibility/cts-intro.jd
@@ -19,7 +19,7 @@
<h2 id="how-does-the-cts-work">How does the CTS work?</h2>
<div style="float: right">
- <img src="/images/cts-0.png">
+ <img src="{@docRoot}images/cts-0.png">
</div>
<p>The CTS is an automated testing harness that includes two major software components:</p>
diff --git a/src/compatibility/index.jd b/src/compatibility/index.jd
index d081d3c..13ee12e 100644
--- a/src/compatibility/index.jd
+++ b/src/compatibility/index.jd
@@ -49,7 +49,7 @@
<ol>
<li>
<p><em>Obtain the Android software source code</em>.
- This is <a href="/source/index.html">the source code for the Android platform</a>, that you port to your hardware.</p>
+ This is <a href="{@docRoot}source/index.html">the source code for the Android platform</a>, that you port to your hardware.</p>
</li>
<li>
<p><em>Comply with Android Compatibility Definition Document (CDD)</em>.
@@ -66,4 +66,4 @@
Play to provide your users access to the third-party app ecosystem.
Unfortunately, for a variety of legal and business reasons, we aren't able to
automatically license Google Play to all compatible devices. To inquire
-about access about Google Play, you can <a href="contact-us.html">contact us</a>.</p>
\ No newline at end of file
+about access about Google Play, you can <a href="contact-us.html">contact us</a>.</p>