From 70b400cba92fef2bf559f3ae3358324ed74008a9 Mon Sep 17 00:00:00 2001
From: June <june@eridan.me>
Date: Sun, 23 Jan 2022 19:59:47 +0000
Subject: Mention remove custom AVB key before flashing and locking stock

Signed-off-by: June <june@eridan.me>
---
 static/install/cli.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'static/install/cli.html')

diff --git a/static/install/cli.html b/static/install/cli.html
index dd711a8a..dab5f855 100644
--- a/static/install/cli.html
+++ b/static/install/cli.html
@@ -545,11 +545,11 @@ curl -O https://releases.grapheneos.org/DEVICE_NAME-factory-2021110122.zip.sig</
                     <h3><a href="#replacing-grapheneos-with-the-stock-os">Replacing GrapheneOS with the stock OS</a></h3>
 
                     <p>Installation of the stock OS via the stock factory images is the same process
-                    described above. However, before locking, there's an additional step to fully revert
-                    the device to a clean factory state.</p>
+                    described above. However, before flashing and locking, there's an additional step
+                    to fully revert the device to a clean factory state.</p>
 
                     <p>The GrapheneOS factory images flash a non-stock Android Verified Boot key which
-                    needs to be erased to fully revert back to a stock device state. After flashing the
+                    needs to be erased to fully revert back to a stock device state. Before flashing the
                     stock factory images and before locking the bootloader, you should erase the custom
                     Android Verified Boot key to untrust it:</p>
 
-- 
cgit v1.3.1