From a7848665f1ca6df2a2d3e1073cf7a925a47b588b Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Mon, 3 Jun 2019 12:26:29 -0400
Subject: adjust approach to header links

---
 static/install.html | 33 +++++++++++++--------------------
 1 file changed, 13 insertions(+), 20 deletions(-)

(limited to 'static/install.html')

diff --git a/static/install.html b/static/install.html
index fe53443e..b6a248d1 100644
--- a/static/install.html
+++ b/static/install.html
@@ -20,7 +20,7 @@
         <meta property="og:site_name" content="GrapheneOS"/>
         <link rel="icon" type="image/vnd.microsoft.icon" href="/favicon.ico?0"/>
         <link rel="mask-icon" href="/safari_pinned_tab_icon.svg" color="#000000"/>
-        <link rel="stylesheet" href="/grapheneos.css?8"/>
+        <link rel="stylesheet" href="/grapheneos.css?9"/>
         <link rel="manifest" href="/manifest.webmanifest"/>
         <link rel="canonical" href="https://grapheneos.org/install"/>
     </head>
@@ -38,10 +38,11 @@
             </ul>
         </nav>
         <div id="content">
-            <h1 id="install">Install</h1>
+            <h1 id="install">
+                <a href="#install">Install</a>
+            </h1>
             <h2 id="prerequisites">
-                Prerequisites
-                <a href="#prerequisites">¶</a>
+                <a href="#prerequisites">Prerequisites</a>
             </h2>
             <p>You should have at least 2GB of free memory available.</p>
             <p>You need the unlocked variant of one of the supported devices, not a locked carrier
@@ -66,8 +67,7 @@
             from several years ago are still shipped by Linux distributions like Debian and lack
             the compatibility detection of modern versions so they can soft brick devices.</p>
             <h2 id="enabling-oem-unlocking">
-                Enabling OEM unlocking
-                <a href="#enabling-oem-unlocking">¶</a>
+                <a href="#enabling-oem-unlocking">Enabling OEM unlocking</a>
             </h2>
             <p>OEM unlocking needs to be enabled from within the operating system.</p>
             <p>Enable the developer settings menu by going to Settings ➔ System ➔ About phone and
@@ -76,8 +76,7 @@
             'Enable OEM unlocking' setting. This requires internet access on devices with Google
             Play Services.</p>
             <h2 id="unlocking-the-bootloader">
-                Unlocking the bootloader
-                <a href="#unlocking-the-bootloader">¶</a>
+                <a href="#unlocking-the-bootloader">Unlocking the bootloader</a>
             </h2>
             <p>First, boot into the bootloader interface. You can do this by turning off the
             device and then turning it on by holding both the Volume Down and Power buttons.</p>
@@ -85,8 +84,7 @@
             <pre>fastboot flashing unlock</pre>
             <p>The command needs to be confirmed on the device.</p>
             <h2 id="obtaining-factory-images">
-                Obtaining factory images
-                <a href="#obtaining-factory-images">¶</a>
+                <a href="#obtaining-factory-images">Obtaining factory images</a>
             </h2>
             <p>The initial install will be performed by flashing the factory images. This will
             replace the existing OS installation and wipe all the existing data.</p>
@@ -96,8 +94,7 @@
 gpg --verify blueline-factory-2019.04.01.19.zip.sig blueline-factory-2019.04.01.19.zip</pre>
             <p>When this signing key is replaced, the new key will be signed with it.</p>
             <h2 id="flashing-factory-images">
-                Flashing factory images
-                <a href="#flashing-factory-images">¶</a>
+                <a href="#flashing-factory-images">Flashing factory images</a>
             </h2>
             <p>Reboot into the bootloader interface to begin the flashing procedure.</p>
             <p>Next, extract the factory images and run the script to flash them. Note that the
@@ -115,8 +112,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh</pre>
             <p>You should now proceed to locking the bootloader before using the device as locking
             wipes the data again.</p>
             <h2 id="locking-the-bootloader">
-                Locking the bootloader
-                <a href="#locking-the-bootloader">¶</a>
+                <a href="#locking-the-bootloader">Locking the bootloader</a>
             </h2>
             <p>Locking the bootloader is important as it enables full verified boot. It also
             prevents using fastboot to flash, format or erase partitions.  Verified boot will
@@ -131,14 +127,12 @@ TMPDIR="$PWD/tmp" ./flash-all.sh</pre>
             reset.</p>
             <p>Unlocking the bootloader again will perform a factory reset.</p>
             <h2 id="disabling-oem-unlocking">
-                Disabling OEM unlocking
-                <a href="#disabling-oem-unlocking">¶</a>
+                <a href="#disabling-oem-unlocking">Disabling OEM unlocking</a>
             </h2>
             <p>OEM unlocking can be disabled again in the developer settings menu within the
             operating system after booting it up again.</p>
             <h2 id="verifying-installation">
-                Verifying installation
-                <a href="#verifying-installation">¶</a>
+                <a href="#verifying-installation">Verifying installation</a>
             </h2>
             <p>Verified boot authenticates and validates the firmware images and OS from the
             hardware root of trust. Since GrapheneOS supports full verified boot, the OS images
@@ -162,8 +156,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh</pre>
             device. That makes it best to get the pairing done right after installation. You can
             also consider setting up the optional remote attestation service.</p>
             <h2 id="replacing-grapheneos-with-the-stock-os">
-                Replacing GrapheneOS with the stock OS
-                <a href="#replacing-grapheneos-with-the-stock-os">¶</a>
+                <a href="#replacing-grapheneos-with-the-stock-os">Replacing GrapheneOS with the stock OS</a>
             </h2>
             <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
-- 
cgit v1.3.1