docs: Fixing broken links and bad paths.
Bug: 9192223
Change-Id: Iee1dadd0a2b38a48ac0ebcbc78f87d6087e01bb1
diff --git a/src/source/community/index.jd b/src/source/community/index.jd
index 0af20a6..22aa73c 100644
--- a/src/source/community/index.jd
+++ b/src/source/community/index.jd
@@ -92,7 +92,7 @@
</li>
<li>
<p><em>Give plenty of details in your post.</em> Code or log snippets, pointers to screenshots, and similar details will get better results and make for better discussions. For a great guide to phrasing your questions, read <a href="http://www.catb.org/%7Eesr/faqs/smart-questions.html">How to Ask Questions the Smart Way</a>.
-<img src="/images/external-link.png"></p>
+<img src="{@docRoot}images/external-link.png"></p>
</li>
</ul>
diff --git a/src/source/contributing.jd b/src/source/contributing.jd
index 377c449..dd1ded9 100644
--- a/src/source/contributing.jd
+++ b/src/source/contributing.jd
@@ -18,7 +18,7 @@
-->
<p>Thanks for your interest in Android! Here are some ways you can get involved
and help us improve Android. For background on the Android project and our
-goals, check out the <a href="/source/index.html">Overview</a> page.</p>
+goals, check out the <a href="{@docRoot}source/index.html">Overview</a> page.</p>
<h2 id="report-bugs">Report Bugs</h2>
<p>One of the easiest and most effective ways you can help improve Android is
@@ -46,4 +46,4 @@
and by learning about <code>git</code>, <code>repo</code>, and other tools using the links to the left.
You can also view the activity on all contributions on our
<a href="https://android-review.googlesource.com/">Gerrit server</a>.
-If you need help along the way, you can join our <a href="/source/index.html">discussion groups</a>.</p>
\ No newline at end of file
+If you need help along the way, you can join our <a href="/source/index.html">discussion groups</a>.</p>
diff --git a/src/source/developing.jd b/src/source/developing.jd
index d8bfb05..6fe7b73 100644
--- a/src/source/developing.jd
+++ b/src/source/developing.jd
@@ -73,7 +73,7 @@
</code></pre>
<h2 id="creating-topic-branches">Creating topic branches</h2>
<p>Start a topic branch in your local work environment whenever you begin a change, for example when you begin work on a bug or new feature. A topic branch is not a copy of the original files; it is a pointer to a particular commit. This makes creating local branches and switching among them a light-weight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic branches, see <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt">Separating topic branches</a>.
-<img src="/images/external-link.png" alt=""></p>
+<img src="{@docRoot}images/external-link.png" alt=""></p>
<p>To start a topic branch using Repo: </p>
<pre><code>$ repo start BRANCH_NAME
</code></pre>
@@ -156,4 +156,4 @@
</code></pre>
<p>Deleting a client will <em>permanently delete</em> any changes you have not yet uploaded for review.</p>
<h2 id="git-and-repo-cheatsheet">Git and Repo cheatsheet</h2>
-<p><img src="/images/git-repo-1.png" alt="list of basic git and repo commands"></p>
+<p><img src="{@docRoot}images/git-repo-1.png" alt="list of basic git and repo commands"></p>
diff --git a/src/source/faqs.jd b/src/source/faqs.jd
index e56669c..7c1e5d4 100644
--- a/src/source/faqs.jd
+++ b/src/source/faqs.jd
@@ -93,7 +93,7 @@
<p>Finally, Google works on the next version of the Android platform in tandem
with developing a flagship device. This branch pulls in changes from the
experimental and stable branches as appropriate.</p>
-<p>You can find more information on this topic at our <a href="source/code-lines.html">Branches and Releases</a>.</p>
+<p>You can find more information on this topic at our <a href="{@docRoot}source/code-lines.html">Branches and Releases</a>.</p>
<h3 id="why-are-parts-of-android-developed-in-private">Why are parts of Android developed in private?</h3>
<p>It typically takes over a year to bring a device to market, but of course
device manufacturers want to ship the latest software they can. Developers,
diff --git a/src/source/life-of-a-patch.jd b/src/source/life-of-a-patch.jd
index a6fee4b..5e316a0 100644
--- a/src/source/life-of-a-patch.jd
+++ b/src/source/life-of-a-patch.jd
@@ -23,4 +23,4 @@
the steps below are performed in the web application.</p>
<p>For full instructions on how to get set up to use gerrit and git, please
see the <a href="submit-patches.html">Submitting Patches</a> page.</p>
-<p><img src="/images/workflow-0.png" alt="workflow diagram"/></p>
\ No newline at end of file
+<p><img src="{@docRoot}images/workflow-0.png" alt="workflow diagram"/></p>
diff --git a/src/source/roles.jd b/src/source/roles.jd
index 9c93efc..7f2258b 100644
--- a/src/source/roles.jd
+++ b/src/source/roles.jd
@@ -31,7 +31,7 @@
<p>Anyone who is interested in exploring and contributing to Android can use the
Android Open Source Project resources. Anyone can join the mailing lists, ask
questions, contribute patches, report bugs, look at submitted patches, and use
-the tools. To get started with the Android code, see <a href="/source/contributing.html">Contributing</a>.</p>
+the tools. To get started with the Android code, see <a href="{@docRoot}source/contributing.html">Contributing</a>.</p>
<h2 id="contributor">Contributor</h2>
<p>A "Contributor" is anyone making contributions to the AOSP source code,
including both employees of Google or other companies, as well as external