From ddb6d1c28ddcf5c529cf4db703d43746b91a31ae Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Sat, 14 Mar 2020 21:51:42 -0400
Subject: [PATCH] split up signing information

---
 static/build.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/static/build.html b/static/build.html
index 92f0bbda..7cedd57e 100644
--- a/static/build.html
+++ b/static/build.html
@@ -427,9 +427,9 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
 
             <p>The keys should not be given passwords due to limitations in the upstream scripts.
             If you want to secure them at rest, you should take a different approach where they
-            can still be available to the signing scripts as a directory of unencrypted keys. The
-            sample certificate subject can be replaced with your own information or simply left
-            as-is.</p>
+            can still be available to the signing scripts as a directory of unencrypted keys.</p>
+
+            <p>The sample certificate subject should be replaced with your own information.</p>
 
             <p>To generate keys for crosshatch (you should use unique keys per device
             variant):</p>