docs: Repairing broken links from staging.
Bug: 9192223
Change-Id: I4579b4cc5a58785f4ade92a748a434e3f2806425
Staging location:
http://claym.mtv.corp.google.com:8082/index.html
diff --git a/src/devices/tech/input/migration-guide.jd b/src/devices/tech/input/migration-guide.jd
index dbdf666..ff39dfd 100644
--- a/src/devices/tech/input/migration-guide.jd
+++ b/src/devices/tech/input/migration-guide.jd
@@ -38,7 +38,7 @@
function input devices. These files should simple contain a line to set
the keyboard type to <code>SPECIAL_FUNCTION</code>.</p>
<p>A good way to ensure that all built-in input devices are appropriately configured
-is to run <a href="/tech/input/dumpsys.html">Dumpsys</a> and look for devices that
+is to run <a href="dumpsys.html">Dumpsys</a> and look for devices that
are inappropriately using <code>Generic.kcm</code>.</p>
<h2 id="migrating-to-android-honeycomb-32">Migrating to Android Honeycomb 3.2</h2>
<p>In Honeycomb 3.2, we added support for joysticks and extended the key layout file
@@ -51,5 +51,5 @@
multitouch input protocol correctly according to the standard.</p>
<p>You will also need to update your input device configuration files because some
properties have been changed to be simpler and more systematic.</p>
-<p>Refer to <a href="/tech/input/touch-devices.html">Touch Devices</a> for more details about
-driver requirements.</p>
\ No newline at end of file
+<p>Refer to <a href="touch-devices.html">Touch Devices</a> for more details about
+driver requirements.</p>