mark up top-level FAQ sections

This commit is contained in:
Daniel Micay 2020-12-05 14:17:17 -05:00
parent af84fee780
commit 82493a7556

View File

@ -113,7 +113,8 @@
</ul>
</nav>
<h2 id="device-support">
<section id="device-support">
<h2>
<a href="#device-support">Device support</a>
</h2>
@ -271,8 +272,10 @@
security of the project when exceptions for old devices need to be listed out. The
project ends up wanting to drop devices for this reason but has always kept them going
until the end-of-life date to provide more time for people to migrate.</p>
</section>
<h2 id="security-and-privacy">
<section id="security-and-privacy">
<h2>
<a href="#security-and-privacy">Security and privacy</a>
</h2>
@ -821,8 +824,10 @@
Linux kernel is monolithic and has no internal security boundaries, the attack surface
is problematic and a HardMAC implementation with most complexity in the isolated
firmware could be better than the status quo. An isolated driver would be ideal.</p>
</section>
<h2 id="day-to-day-use">
<section id="day-to-day-use">
<h2>
<a href="#day-to-day-use">Day to day use</a>
</h2>
@ -907,6 +912,7 @@
cases we want to support. GPLv3 is no problem for our own usage, but we don't want to
forbid using GrapheneOS as a replacement for the Android Open Source Project in locked
down devices.</p>
</section>
</main>
<footer>
<a href="/"><img src="/logo.png" width="512" height="512" alt=""/>GrapheneOS</a>