aboutsummaryrefslogtreecommitdiff
path: root/en/devices/tech/ota/tools.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/devices/tech/ota/tools.html')
-rw-r--r--en/devices/tech/ota/tools.html15
1 files changed, 8 insertions, 7 deletions
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