summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2022-05-09 14:25:15 -0400
committerDaniel Micay <danielmicay@gmail.com>2022-05-09 14:25:15 -0400
commit6a1b3041efd010791637fce2663dae9e40e67c87 (patch)
tree8ba8df44b0aaf3b3df5c69b5f8f234760719a9b2 /static
parent8e71d59492d4696c65a5f1120e99b8fa07456e8b (diff)
use bare absolute paths for internal links
Diffstat (limited to 'static')
-rw-r--r--static/usage.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/static/usage.html b/static/usage.html
index 5dbc4867..3cff20c0 100644
--- a/static/usage.html
+++ b/static/usage.html
@@ -355,7 +355,7 @@
<h3><a href="#updates-sideloading">Sideloading</a></h3>
<p>Updates can be downloaded via
- <a href="https://grapheneos.org/releases">the releases page</a> and installed via recovery
+ <a href="/releases">the releases page</a> and installed via recovery
with adb sideloading. The zip files are signed and verified by recovery, just as they
are by the update client within the OS. This includes providing downgrade protection,
which prevents attempting to downgrade the version. If recovery didn't enforce these
@@ -1022,11 +1022,11 @@
enforce using Google certified operating systems. However, app developers can use
it directly and permit other properly signed operating systems upholding the
security model. GrapheneOS has a
- <a href="https://grapheneos.org/articles/attestation-compatibility-guide">
- detailed guide</a> for app developers on how to support GrapheneOS with the
- hardware attestation API. Direct use of the hardware attestation API provides much
- higher assurance than using SafetyNet so these apps have nothing to lose by using a
- more meaningful API and supporting a more secure OS.</p>
+ <a href="/articles/attestation-compatibility-guide">detailed guide</a> for app
+ developers on how to support GrapheneOS with the hardware attestation API. Direct
+ use of the hardware attestation API provides much higher assurance than using
+ SafetyNet so these apps have nothing to lose by using a more meaningful API and
+ supporting a more secure OS.</p>
</section>
<section id="app-link-verification">