docs: fixes minor spelling mistakes

Signed-off-by: Nick Ufer <nick@ufer.dev>
authzed · Oct 2, 2021 · 0b66478 · 0b66478
1 parent ec097e4
commit 0b66478
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -19,7 +19,7 @@ Before creating an issue, please check that an issue reporting the same problem
 To make the issue accurate and easy to understand, please try to create issues that are:
 
 - Unique -- do not duplicate existing bug report.
-  Deuplicate bug reports will be closed.
+  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.
   Some issues might be hard to reproduce, so please do your best to include the steps that might lead to the problem.

diff --git a/README.md b/README.md
@@ -47,7 +47,7 @@ This becomes especially important as you introduce backwards-compatible changes
 
 ### Optimal Flexibility
 
-The SpiceDB schema langauge is built on top of the concept of a graph of relationships between objects.
+The SpiceDB schema language is built on top of the concept of a graph of relationships between objects.
 This ReBAC design is capable of efficiently supporting all popular access control models (such as [RBAC] and [ABAC]) and custom models that contain hybrid behavior.
 
 Modern solutions to developing permission systems all have a similar goal: to decouple _policy_ from the application.

diff --git a/e2e/newenemy/README.md b/e2e/newenemy/README.md
@@ -66,7 +66,7 @@ This means that in SpiceDB backed by CockroachDB, the new enemy problem is possi
 1. The writes in the `exclude write` and `direct write` must land in different ranges.
 2. The leader of the range for write 2 must not be on the same node as any follower for the range for write 1.
     - Otherwise, the timestamp cache for the two nodes will be in sync and the logical clock will properly order the transactions
-3. The writes are recieved by two different nodes in the cluster, one of which has a slower clock.
+3. The writes are received by two different nodes in the cluster, one of which has a slower clock.
 
 This is possible because the keys that are written in the transactions do not overlap.