summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
authorDaniel Micay <daniel.micay@grapheneos.org>2024-06-02 16:22:44 -0400
committerDaniel Micay <daniel.micay@grapheneos.org>2024-06-02 16:22:44 -0400
commit8c2aae1ddf3c031965eb500fcdc5e7b3634529a4 (patch)
tree5a85e73806568d0a583c68dc4739ca5b6ff490f3 /static
parent4b599c242140cbc9d35d98b9f15f2ad13051b45e (diff)
whitespace fixes
Diffstat (limited to 'static')
-rw-r--r--static/features.html21
1 files changed, 11 insertions, 10 deletions
diff --git a/static/features.html b/static/features.html
index 6b1ca845..1eae62f8 100644
--- a/static/features.html
+++ b/static/features.html
@@ -808,21 +808,22 @@
<section id="duress">
<h3><a href="#duress">Duress PIN/Password</a></h3>
- <p>GrapheneOS provides users with the ability to set a duress PIN/Password that
- will irreversibly wipe the device (along with any installed eSIMs) once entered
- anywhere where the device credentials are requested (on the lockscreen, along
+ <p>GrapheneOS provides users with the ability to set a duress PIN/Password that
+ will irreversibly wipe the device (along with any installed eSIMs) once entered
+ anywhere where the device credentials are requested (on the lockscreen, along
with any such prompt in the OS).</p>
- <p>The wipe does not require a reboot and cannot be interrupted. It can be set up
- at <b>Settings&#160;<span aria-label="and then">></span> Security&#160;
- <span aria-label="and then">></span> Duress Password</b> in the owner profile.
- Both a duress PIN and password will need to be set to account for different profiles
+ <p>The wipe does not require a reboot and cannot be interrupted. It can be set
+ up at <b>Settings&#160;<span aria-label="and then">></span> Security&#160; <span
+ aria-label="and then">></span> Duress Password</b> in the owner profile. Both a
+ duress PIN and password will need to be set to account for different profiles
that may have different unlock methods.</p>
- <p>Note that if the duress PIN/Password is the same as the actual unlock method, the
- actual unlock method always takes precedence, and therefore no wipe will occur.</p>
+ <p>Note that if the duress PIN/Password is the same as the actual unlock method,
+ the actual unlock method always takes precedence, and therefore no wipe will
+ occur.</p>
</section>
-
+
<section id="more-secure-fingerprint-unlock">
<h3><a href="#more-secure-fingerprint-unlock">More secure fingerprint unlock</a></h3>