Docs: Changes to source.android.com

  - 153141633 Update link to Security bug template in preparation for l... by daroberts <daroberts@google.com>
  - 153141624 Update bug reporting links to Issue Tracker by daroberts <daroberts@google.com>
  - 153130270 Typo fix, submitted by YOUNG HO CHA <ganadist@gmail.com> by blamb <blamb@google.com>
  - 153128486 Fix next wave of broken links from migration by claym <claym@google.com>

PiperOrigin-RevId: 153141633
Change-Id: I04448bdc8953376ade5328af97f868f0b3670cfb

7 files changed, 22 insertions, 19 deletions

diff --git a/en/devices/audio/index.html b/en/devices/audio/index.html
index 77aba3bf..e016b929 100644
--- a/en/devices/audio/index.html
+++ b/en/devices/audio/index.html
@@ -100,7 +100,7 @@ The HAL defines the standard interface that audio services call into and that
 you must implement for your audio hardware to function correctly. The audio HAL
 interfaces are located in <code>hardware/libhardware/include/hardware</code>.
 For details, see <a
-href="/devices/halref/audio_8h_source.html">hardware/audio.h</a>.
+href="https://android.googlesource.com/platform/hardware/libhardware/+/master/include/hardware/audio.h">audio.h</a>.
 </dd>
 
 <dt>
diff --git a/en/devices/audio/terminology.html b/en/devices/audio/terminology.html
index f84fa88b..14994d3c 100644
--- a/en/devices/audio/terminology.html
+++ b/en/devices/audio/terminology.html
@@ -427,7 +427,7 @@ on intra-device interconnections, refer to the following articles:
 In
 <a href="http://www.alsa-project.org/main/index.php/ASoC">ALSA System on Chip (ASoC)</a>,
 these are collectively called
-<a href="https://www.kernel.org/doc/Documentation/sound/alsa/soc/DAI.txt">Digital Audio Interfaces</a>
+<a href="https://www.kernel.org/doc/Documentation/sound/soc/dai.rst">Digital Audio Interfaces</a>
 (DAI).
 </p>
 
diff --git a/en/devices/audio/usb.html b/en/devices/audio/usb.html
index e3d5fce7..f1c99ff6 100644
--- a/en/devices/audio/usb.html
+++ b/en/devices/audio/usb.html
@@ -554,7 +554,7 @@ In order to support USB digital audio, device OEMs and SoC vendors should:
 <li>enable generic USB host support at the framework level
 via the <code>android.hardware.usb.host.xml</code> feature flag</li>
 <li>enable all kernel features needed: USB host mode, USB audio, isochronous transfer mode;
-see <a href="/devices/tech/kernel.html">Android Kernel Configuration</a></li>
+see <a href="/devices/tech/config/kernel.html">Android Kernel Configuration</a></li>
 <li>keep up-to-date with recent kernel releases and patches;
 despite the noble goal of class compliance, there are extant audio peripherals
 with <a href="http://en.wiktionary.org/wiki/quirk">quirks</a>,
diff --git a/en/devices/automotive.html b/en/devices/automotive.html
index 584fd7a4..d77e5645 100644
--- a/en/devices/automotive.html
+++ b/en/devices/automotive.html
@@ -183,7 +183,7 @@ such cases, use special values to represent such state.</p>
 
 <p>Example: get HVAC Temperature</p>
 <img src="images/vehicle_hvac_get.png" alt="Vehicle HAL get HVAC example">
-<p class="img-caption"><strong>Figure 2</strong>. Get HVAC temperature (CD =
+<p class="img-caption"><strong>Figure 2</strong>. Get HVAC temperature (CS =
 CarService, VNS = VehicleNetworkService, VHAL = Vehicle HAL)</p>
 
 <h3 id=set>Set calls</h3>
diff --git a/en/devices/sensors/sensor-stack.html b/en/devices/sensors/sensor-stack.html
index cd4fcab1..8ec03204 100644
--- a/en/devices/sensors/sensor-stack.html
+++ b/en/devices/sensors/sensor-stack.html
@@ -127,7 +127,9 @@
 <p>The interface is defined by Android and AOSP contributors, and the
   implementation is provided by the manufacturer of the device.</p>
 <p>The sensor HAL interface is located in <code>hardware/libhardware/include/hardware</code>.
-  See <a href="/devices/halref/sensors_8h.html">sensors.h</a> for additional details.</p>
+  See <a
+    href="https://android.googlesource.com/platform/hardware/libhardware/+/master/include/hardware/sensors.h">sensors.h</a>
+  for additional details.</p>
 <h3 id="release_cycle">Release cycle</h3>
 <p>The HAL implementation specifies what version of the HAL interface it
   implements by setting <code>your_poll_device.common.version</code>. The existing HAL
diff --git a/en/devices/tech/ota/tools.html b/en/devices/tech/ota/tools.html
index 32eec985..1b26f918 100644
--- a/en/devices/tech/ota/tools.html
+++ b/en/devices/tech/ota/tools.html
@@ -23,11 +23,12 @@
 
 
 
-<p>The <a href="https://android.googlesource.com/platform/build/+/master/tools/
-releasetools/ota_from_target_files">ota_from_target_files</a> tool provided in
-<code>build/tools/releasetools</code> can build two types of package: <i>full
-</i> and <i>incremental</i>. The tool takes the <i>target-files</i> .zip file
-produced by the Android build system as input.</p>
+<p>The <a
+  href="https://android.googlesource.com/platform/build/+/master/tools/releasetools/ota_from_target_files">ota_from_target_files</a>
+tool provided in <code>build/tools/releasetools</code> can build two types of
+package: <i>full </i> and <i>incremental</i>. The tool takes the
+<i>target-files</i> .zip file produced by the Android build system as
+input.</p>
 
 <h2 id="full-updates">Full updates</h2>
 <p>A <i>full</i> update is one where the entire final state of the device
@@ -62,8 +63,8 @@ done.
 
 <p>The ota_update.zip is now ready to be sent to test devices (everything is
 signed with the test key). For user devices, generate and use your own private
-keys as detailed in <a href="/devices/tech/ota/sign_builds
-.html">Signing builds for release</a>.
+keys as detailed in <a href="/devices/tech/ota/sign_builds.html">Signing builds
+  for release</a>.
 
 <h2 id="incremental-updates">Incremental updates</h2>
 <p>An <i>incremental</i> update contains a set of binary patches to be applied
diff --git a/en/devices/tech/test_infra/tradefed/fundamentals/lifecycle.html b/en/devices/tech/test_infra/tradefed/fundamentals/lifecycle.html
index f5c836d1..a46bb22c 100644
--- a/en/devices/tech/test_infra/tradefed/fundamentals/lifecycle.html
+++ b/en/devices/tech/test_infra/tradefed/fundamentals/lifecycle.html
@@ -26,17 +26,17 @@
 <p>The lifecycle of a test executed using TradeFederation is composed of four separate stages, designed
 around formally defined interfaces.</p>
 <ul>
-<li><a href="/reference/com/android/tradefed/build/IBuildProvider.html"
+<li><a href="/reference/tradefed/com/android/tradefed/build/IBuildProvider.html"
   >Build Provider</a>: Provides a build to test, downloading appropriate files if necessary.</li>
-<li><a href="/reference/com/android/tradefed/targetprep/ITargetPreparer.html"
+<li><a href="/reference/tradefed/com/android/tradefed/targetprep/ITargetPreparer.html"
   >Target Preparer</a>: Prepares the test environment, possibly including software installation and
   device configuration.</li>
-<li><a href="/reference/com/android/tradefed/testtype/IRemoteTest.html"
+<li><a href="/reference/tradefed/com/android/tradefed/testtype/IRemoteTest.html"
   >Test</a>: Executes test(s) and gathers test results.  This may be any JUnit Test, although our
-  <a href="/reference/com/android/tradefed/testtype/IRemoteTest.html"
+  <a href="/reference/tradefed/com/android/tradefed/testtype/IRemoteTest.html"
   >IRemoteTest</a> interface is specifically designed to work well in the Trade Federation
   environment.</li>
-<li><a href="/reference/com/android/tradefed/result/ITestInvocationListener.html"
+<li><a href="/reference/tradefed/com/android/tradefed/result/ITestInvocationListener.html"
   >Test Invocation Listener</a>: Listens for test results, usually for the purpose of forwarding the
   test results to a repository or displaying them to the Test Runner.</li>
 </ul>
@@ -59,9 +59,9 @@ In short, an Invocation encompasses a complete TF test execution, across its ent
 
 <h3>Additional Components of a Configuration</h3>
 <ul>
-<li><a href="/reference/com/android/tradefed/device/IDeviceRecovery.html"
+<li><a href="/reference/tradefed/com/android/tradefed/device/IDeviceRecovery.html"
   >Device Recovery</a>: mechanism to recover device communication if lost.</li>
-<li><a href="/reference/com/android/tradefed/log/package-summary.html">Logger</a>: collects tradefed logging data.</li>
+<li><a href="/reference/tradefed/com/android/tradefed/log/package-summary.html">Logger</a>: collects tradefed logging data.</li>
 </ul>