chore: fix grammar errors in documentation (#393)

- Fix spelling errors (documented, absence, analysis, hierarchies, homage)
- Fix missing articles and auxiliary verbs
- Remove duplicate words
- Fix subject-verb agreement
- Correct markdown formatting

Author: ivanauth

CONTRIBUTING.md

@@ -18,7 +18,7 @@ All bugs and mistakes are considered very seriously, regardless of complexity.
 Before creating an issue, please check that an issue reporting the same problem does not already exist.
 To make the issue accurate and easy to understand, please try to create issues that are:
 
-- Unique -- do not duplicate existing bug report.
+- Unique -- do not duplicate an existing bug report.
   Duplicate bug reports will be closed.
 - Specific -- include as much details as possible: which version, what environment, what configuration, etc.
 - Reproducible -- include the steps to reproduce the problem.
@@ -63,6 +63,6 @@ Signed-off-by: Random J Developer <[email protected]>
 ```
 
 This can be done by using the `--signoff` (or `-s` for short) git flag to append this automatically to your commit message.
-If you have already authored a commit that is missing the signed-off, you can amend or rebase your commits and force push them to GitHub.
+If you have already authored a commit that is missing the signed-off-by, you can amend or rebase your commits and force push them to GitHub.
 
 [DCO]: /DCO

README.md

@@ -42,4 +42,4 @@ Run linters:
 
 ```sh
 pnpm run lint
-````
+```

pages/authzed/concepts/authzed-materialize.mdx

@@ -39,7 +39,7 @@ In summary, AuthZed Materialize allows you to:
 
 ## Client SDK
 
-All SpiceDB SDKs have the generated gRPC and protobuf coded
+All SpiceDB SDKs have the generated gRPC and protobuf code
 
 - [authzed-go v0.15.0](https://github.com/authzed/authzed-go/releases/tag/v0.15.0)
 - [authzed-java 0.10.0](https://github.com/authzed/authzed-java/releases/tag/0.10.0)

pages/authzed/concepts/expedited-support.mdx

@@ -37,7 +37,7 @@ Non-critical support is prioritized through [support.authzed.com][support] or [s
 
 ### Emergency
 
-For those that do not need all of the features of Gold Support, but do need response time SLAs for taking their services to production, we offer our Emergency plan.
+For those who do not need all of the features of Gold Support, but do need response time SLAs for taking their services to production, we offer our Emergency plan.
 This plan only includes those Response Time SLAs for critical and non-critical issues.
 
 Private communication channels are provided for critical support that are integrated with the AuthZed engineering on-call.

pages/authzed/concepts/security-embargo.mdx

@@ -22,7 +22,7 @@ You can find a listing of public vulnerabilities for SpiceDB on [GitHub], [NVD],
 A security embargo program is a defined process under which security issues are privately reported, analyzed for applicability, notice is given, and a resolution is created and distributed.
 The issue is only made public once those affected in the embargo program have enough time to address the issue or have accepted the risks.
 
-Security embargos are an industry best practice for ensuring that there are not critical software deployments with well documentated exploitation instructions.
+Security embargos are an industry best practice for ensuring that there are not critical software deployments with well documented exploitation instructions.
 
 ## Reporting a security issue
 
@@ -58,7 +58,7 @@ When vulnerabilities are reported, AuthZed works with the reporter to develop a
 Some vulnerabilities are reported by research firms that have strict policies to encourage a quick response and other reports are from individuals that may be more flexible with resolution time.
 
 Once a report has been verified and a timeline has been established, AuthZed customers are informed.
-In the absense of a strict deadline, vulnerabilities are made public once every possibly affected AuthZed customer has either resolved the issue or accepted the risk to continuing to operate.
+In the absence of a strict deadline, vulnerabilities are made public once every possibly affected AuthZed customer has either resolved the issue or accepted the risk to continuing to operate.
 
 ## What actions must users under embargo take?
 

pages/authzed/concepts/update-channels.mdx

@@ -3,7 +3,7 @@
 Update Channels dictate the flow of updates to running SpiceDB clusters.
 
 All channels offer a trade-off between feature availability and update churn.
-While each channel has a different qualification standards, all channels offer fully tested GA releases of SpiceDB.
+While each channel has different qualification standards, all channels offer fully tested GA releases of SpiceDB.
 
 While open source users of the [SpiceDB Operator] have a single update channel of open source releases, AuthZed maintains two configurable channels:
 

pages/spicedb/concepts/consistency.mdx

@@ -151,7 +151,7 @@ If a fixed-width column is preferred, we recommend `varchar(1024)`.
   [ccc-api]: https://authzed.com/zanzibar#annotations/intro/content-change-check
 </Callout>
 
-Data can be complex and designed with hierachies in mind.
+Data can be complex and designed with hierarchies in mind.
 In these scenarios, the parent resource must be referenced.
 
 A simpler alternative is to perform read-after-write queries to SpiceDB with full consistency.

pages/spicedb/concepts/zanzibar.mdx

@@ -23,7 +23,7 @@ This paper documented the design and success of the project that went on to hand
 Before landing on the name Zanzibar, the project was internally referred to as "Spice".
 At Google, their mission was to ensure the "ACLs must flow", a reference to ["the spice must flow"][spice-must-flow].
 This theme was chosen because Lea Kissner, one of the co-creators, is a [Dune fan][lea-dune].
-In homeage, AuthZed maintained a Dune-related naming scheme for their own projects.
+In homage, AuthZed maintained a Dune-related naming scheme for their own projects.
 
 [lea-dune]: https://twitter.com/LeaKissner/status/1304457030044794880
 [spice-must-flow]: https://fictionhorizon.com/the-meaning-of-dunes-the-spice-must-flow-quote/

pages/spicedb/getting-started/coming-from/cancancan.mdx

@@ -11,14 +11,14 @@ import SpiceDBDark from '@/public/images/ps-spicedb-dark.svg'
 This document is designed to cover the conceptual differences between SpiceDB and the popular Ruby on Rails gem CanCanCan.
 
 <Callout type="info" emoji="ℹ️">
-The focus of the content below is not intended to be a competitive anlaysis, but rather a bridge to understand SpiceDB for existing Rails users.
+The focus of the content below is not intended to be a competitive analysis, but rather a bridge to understand SpiceDB for existing Rails users.
 </Callout>
 
 ## SpiceDB vs CanCanCan
 
 Every complete permissions system is made up of three major components: *models*, *data*, and an *engine*.
 
-While comparing SpiceDB and CanCanCan is akin to comparing apples and oranges because they are fundamentally two different approaches, both can analyzed through the lens of these three components to understand the design of each.
+While comparing SpiceDB and CanCanCan is akin to comparing apples and oranges because they are fundamentally two different approaches, both can be analyzed through the lens of these three components to understand the design of each.
 
 A quick recap on the components and their purpose:
 

pages/spicedb/getting-started/coming-from/opa.mdx

@@ -11,14 +11,14 @@ import SpiceDBDark from '@/public/images/ps-spicedb-dark.svg'
 This document is designed to cover the conceptual differences between SpiceDB and Open Policy Agent (OPA).
 
 <Callout type="info" emoji="ℹ️">
-  The focus of the content below is not intended to be a competitive anlaysis, but rather a bridge to understand SpiceDB for existing OPA users.
+  The focus of the content below is not intended to be a competitive analysis, but rather a bridge to understand SpiceDB for existing OPA users.
 </Callout>
 
 ## SpiceDB vs OPA
 
 Every complete permissions system is made up of three major components: *models*, *data*, and an *engine*.
 
-While comparing SpiceDB and OPA is akin to comparing apples and oranges because they are fundamentally two different approaches, both can analyzed through the lens of these three components to understand the design of each.
+While comparing SpiceDB and OPA is akin to comparing apples and oranges because they are fundamentally two different approaches, both can be analyzed through the lens of these three components to understand the design of each.
 
 A quick recap on the components and their purpose: