From df2ba99dea1005a4a63389c5935295621b3ff935 Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Fri, 12 Nov 2021 11:14:29 -0500
Subject: [PATCH] add missing word

---
 static/usage.html | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/static/usage.html b/static/usage.html
index 1e63bfe2..d5d7275e 100644
--- a/static/usage.html
+++ b/static/usage.html
@@ -784,16 +784,17 @@
 
                 <p>GrapheneOS has a compatibility layer providing the option to install and use
                 the official releases of Play services in the standard app sandbox. Play services
-                receives absolutely no special or privileges on GrapheneOS as opposed to bypassing
-                the app sandbox and receiving a massive amount of highly privileged access. It
-                also doesn't become a backend for the OS services as it does elsewhere. GrapheneOS
-                itself doesn't use Play services even when it's installed. Since the Play services
-                apps are simply regular apps on GrapheneOS, they get installed by the user within
-                a specific user or work profile and are only available within that profile. Only
-                apps within the same profile can use it and they need to explicitly choose to use
-                it. It works the same way as any other app and has no special capabilities. As
-                with any other app, it can't access data of other apps and requires explicit user
-                consent to gain access to profile data or the standard permissions.</p>
+                receives absolutely no special access or privileges on GrapheneOS as opposed to
+                bypassing the app sandbox and receiving a massive amount of highly privileged
+                access. It also doesn't become a backend for the OS services as it does elsewhere.
+                GrapheneOS itself doesn't use Play services even when it's installed. Since the
+                Play services apps are simply regular apps on GrapheneOS, they get installed by
+                the user within a specific user or work profile and are only available within that
+                profile. Only apps within the same profile can use it and they need to explicitly
+                choose to use it. It works the same way as any other app and has no special
+                capabilities. As with any other app, it can't access data of other apps and
+                requires explicit user consent to gain access to profile data or the standard
+                permissions.</p>
 
                 <p>The core functionality and APIs are almost entirely supported already since
                 GrapheneOS largely only has to coerce these apps into continuing to run without