tweaked wording to read better

Author: mooreds

docs/getting-started/sync-data.mdx

@@ -179,7 +179,7 @@ In Write Data API response you'll get a snap token of the operation.
 }
 ```
 
-This token consists of an encoded timestamp, which is used to ensure fresh results in access control checks. We're suggesting using snap tokens in production to prevent data inconsistency and optimize performance. See more on [Snap Tokens](../operations/snap-tokens)
+This token consists of an encoded timestamp, which is used to ensure fresh results in access control checks. We're suggesting using snap tokens in production to prevent data inconsistency and optimize performance. See more on [Snap Tokens](../operations/snap-tokens).
 
 ## More Examples
 
@@ -362,10 +362,10 @@ curl --location --request POST 'localhost:3476/v1/tenants/{tenant_id}/data/write
 <Note>
 Note: `relation: “...”` used when subject type is different from **user** entity. **#…** represents a relation that does not affect the semantics of the tuple.
 
-Simply, the usage of ... is straightforward: if you're using the user entity as a subject, you should not be using the `...` If you're using another subject rather than the user entity then you need to use the `...` 
+Simply, the usage of ... is straightforward: if you're using the user entity as a subject, you should not be using the `...` If you're using another subject rather than the user entity then you need to use the `...` .
 </Note>
 
-### Organization Members Are Maintainers in specific Doc
+### Organization Members Are Maintainers Of A Specific Doc
 
 **Created relational tuple:** document:1#maintainer@organization:2#member
 
@@ -469,4 +469,4 @@ We have a strong foundation for permission baselining and review, thanks to MVCC
 
 **Current State Review:** You can review the current state of permissions by examining the latest versions of each permission setting.
 
-**Cleanup:** Your system incorporates a garbage collector for managing old data, which helps keep your permissions structure clean and optimized.
+**Cleanup:** Your system incorporates a garbage collector for managing old data, which helps keep your permissions structure clean and optimized.

docs/permify-overview/authorization-service.mdx

@@ -54,7 +54,7 @@ You can get started quickly with a [simple API](../getting-started/enforcement)
 
 Permify is based on [Google Zanzibar], which is the global authorization system used at Google for handling authorization for hundreds of its services and products including; YouTube, Drive, Calendar, Cloud and Maps.
 
-The Zanzibar system achieved more than 95% of the access checks responded in 10 milliseconds and has maintained more than 99.999% availability for the 3-year period.
+The Zanzibar system achieved more than 95% of the access checks responded to in 10 milliseconds and has maintained more than 99.999% availability for the 3-year period.
 
 Permify applies proven techniques that Google used. We’re trying to make Zanzibar available to everyone to use and benefit in their applications and services
 

docs/permify-overview/faqs.mdx

@@ -61,7 +61,7 @@ As we can see above: only users with an admin role in an organization, which `do
 
 **Q2:** Get admins of the organization where `document:12` belongs to.
 
-Since edit action consists of **or** between owner and parent.admin, if Permify Engine finds user:3 in results of one of these queries then it terminates the other ongoing queries and returns authorized true to the client.
+Since edit action consists of **or** between owner and parent.admin, if Permify Engine finds user:3 in the results of one of these queries then it terminates the other ongoing queries and returns authorized true to the client.
 
 Rather than **or**, if we had an **and** relation then Permify Engine waits for the results of these queries before returning a decision.