diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2022-05-09 14:24:15 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2022-05-09 14:24:15 -0400 |
| commit | 8e71d59492d4696c65a5f1120e99b8fa07456e8b (patch) | |
| tree | e7f2f0a14bdb2541e77ddb70c6d6df1292e58bc1 /static/faq.html | |
| parent | 2170c3d112cd55978ad9c58aed5bcf60345e5938 (diff) | |
update sandboxed Google Play links
Diffstat (limited to 'static/faq.html')
| -rw-r--r-- | static/faq.html | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/static/faq.html b/static/faq.html index a459bf61..e7f9ddc5 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1210,11 +1210,10 @@ and services. They won't ever be bundled with the OS. GrapheneOS includes compatibility layer for sandboxed Play services to make user installed Play services apps able to run as fully sandboxed, unprivileged apps. This is <a - href="https://grapheneos.org/usage#sandboxed-play-services">documented as - part of the usage guide</a>. Many apps work perfectly without Play services and - many others only depend on it for a subset of their functionality. Users can - choose to install Play services in specific profile(s) to control which apps can - use it.</p> + href="/usage#sandboxed-google-play">documented as part of the usage guide</a>. + Many apps work perfectly without Play services and many others only depend on it + for a subset of their functionality. Users can choose to install Play services in + specific profile(s) to control which apps can use it.</p> <p>AOSP APIs not tied to Google but that are typically provided via Play services will continue to be implemented using open source providers like the Seedvault |