typos

1 files changed, 5 insertions, 5 deletions

diff --git a/examples/muck/muck.md b/examples/muck/muck.md
index 48f421f..c5c3ef8 100644
--- a/examples/muck/muck.md
+++ b/examples/muck/muck.md
@@ -14,10 +14,10 @@ Muck is intended for storing relatively small pieces of data securely,
 and accessing them quickly. Intended uses cases are:
 
 * storing user, client, application, and related data for an OpenID
-  Connect authenatication server
+  Connect authentication server
 * storing personally identifiable information of data subjects (in the
   GDPR sense) in a way that they can access and update, assuming
-  integration with a suitable authantication and authorization server
+  integration with a suitable authentication and authorization server
 * in general, storage for web applications of data that isn't large
   and fits easily into RAM
 
@@ -33,7 +33,7 @@ configured to accept.
 Access control is simplistic. Each resource is assigned an owner
 upon creation, and each user can access (see, update, delete) only
 their own resources. A use with "super" powers can access, update, and
-delete resources they don't own, but can't create resources for other.
+delete resources they don't own, but can't create resources for others.
 This will be improved later.
 
 Architecture
@@ -84,7 +84,7 @@ For Muck to access a token:
 * it specified an end-user (data subject)
 
 Every request to the Muck API must include a token, in the
-`Authorizatin` header as a bearer token. The request is denied if the
+`Authorization` header as a bearer token. The request is denied if the
 token does not pass all the above checks.
 
 Requirements
@@ -92,7 +92,7 @@ Requirements
 
 This chapter lists high level requirements for Muck.
 
-Each requirement here is given a unique mnemnoic id for easier
+Each requirement here is given a unique mnemonic id for easier
 reference in discussions.
 
 **SimpleOps**