diff options
| author | matchboxbananasynergy <107055883+matchboxbananasynergy@users.noreply.github.com> | 2024-06-02 12:52:05 +0000 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2024-06-02 09:30:28 -0400 |
| commit | ad539ed66783b2e2ade9a91297b2a9080c5182c2 (patch) | |
| tree | 3b3d7371bea4579bf40b60dad76ec4b4da6f2bd8 /static/features.html | |
| parent | 204585866657fd2109f516ec1be36162126231d1 (diff) | |
Fix capitalization and conforming style
Diffstat (limited to 'static/features.html')
| -rw-r--r-- | static/features.html | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/static/features.html b/static/features.html index 1ad77505..bd4e43d2 100644 --- a/static/features.html +++ b/static/features.html @@ -777,14 +777,15 @@ <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 + 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 Settings > Security > Duress Password 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> + at <b>Settings <span aria-label="and then">></span> Security  + <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> |