diff options
| author | June <june@eridan.me> | 2022-02-25 16:38:56 +0000 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2022-02-25 11:55:05 -0500 |
| commit | 27fe9586e5fa12b95d6f14ac427a9c4673f4f40b (patch) | |
| tree | 42eda4e1036bbbc64b20ff085ee5c641d1841855 | |
| parent | 14a075aa18ca61e826984c82bbd917715f81d839 (diff) | |
Fix typos
Signed-off-by: June <june@eridan.me>
| -rw-r--r-- | static/usage.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/static/usage.html b/static/usage.html index b10945ea..e9583524 100644 --- a/static/usage.html +++ b/static/usage.html @@ -919,11 +919,11 @@ <h3><a href="#sandboxed-google-play-limitations">Limitations</a></h3> <p>Our compatibility layer has to be expanded on a case-by-case basis to teach - Play services to work as a regular app without any of the invasive the access + Play services to work as a regular app without any of the invasive access and integration it expects. In many cases, it doesn't truly need the access or we can teach it to use the regular approach available to a normal app. In some - cases, the functionality it offers fundamentally requiresy requires privileged - access and cannot be support. For example, it's unlikely Android Auto will be + cases, the functionality it offers fundamentally requires privileged + access and cannot be supported. For example, it's unlikely Android Auto will be supported. The same applies to other highly invasive OS integration / control or privileged access to hardware. There are also a lot of features such as the FIDO2 security key support which could be made to fully work despite reliance |