diff --git a/content/appendices.md b/content/appendices.md
index 2b6de33e..72ec546e 100644
--- a/content/appendices.md
+++ b/content/appendices.md
@@ -1194,7 +1194,7 @@ The event signing algorithm should emit the following signed event:
     "sender": "@u:domain",
     "signatures": {
         "domain": {
-            "ed25519:1": "Wm+VzmOUOz08Ds+0NTWb1d4CZrVsJSikkeRxh6aCcUwu6pNC78FunoD7KNWzqFn241eYHYMGCA5McEiVPdhzBA"
+            "ed25519:1": "Wm+VzmOUOz08Ds+0NTWb1d4CZrVsJSikkeRxh6aCcUwu6pNC78FunoD7KNWzqFn241eYHYMGCA5McEiVPdhzBY"
         }
     },
     "unsigned": {
diff --git a/content/client-server-api/modules/sso_login.md b/content/client-server-api/modules/sso_login.md
index 67d236a3..923d9cd1 100644
--- a/content/client-server-api/modules/sso_login.md
+++ b/content/client-server-api/modules/sso_login.md
@@ -244,7 +244,7 @@ re-enter their password, but for homeservers which delegate to an SSO
 server, this means redirecting to the authentication server during
 user-interactive auth.
 
-The implemementation of this is based on the [Fallback](#fallback) mechanism for
+The implementation of this is based on the [Fallback](#fallback) mechanism for
 user-interactive auth.
 
 #### Client behaviour
diff --git a/content/identity-service-api.md b/content/identity-service-api.md
index cf0536ab..aa648098 100644
--- a/content/identity-service-api.md
+++ b/content/identity-service-api.md
@@ -319,7 +319,7 @@ tables to mine the addresses. Similarly, clients which support the
 `none` algorithm should consider at least warning the user of the risks
 in sending identifiers in plain text to the identity server.
 
-Addresses are still potentially reversable using a calculated rainbow
+Addresses are still potentially reversible using a calculated rainbow
 table given some identifiers, such as phone numbers, common email
 address domains, and leaked addresses are easily calculated. For
 example, phone numbers can have roughly 12 digits to them, making them
diff --git a/content/rooms/v4.md b/content/rooms/v4.md
index 785dc664..eed6b2ed 100644
--- a/content/rooms/v4.md
+++ b/content/rooms/v4.md
@@ -42,7 +42,7 @@ Room version 4 uses the same algorithms defined in [room version
 Room version 3 generated event IDs that were difficult for client
 implementations which were not encoding the event ID to function in
 those rooms. It additionally raised concern due to the `/` character
-being interpretted differently by some reverse proxy software, and
+being interpreted differently by some reverse proxy software, and
 generally made administration harder.
 {{% /boxes/rationale %}}
 
diff --git a/content/rooms/v7.md b/content/rooms/v7.md
index 9ad8dd01..2c1816ad 100644
--- a/content/rooms/v7.md
+++ b/content/rooms/v7.md
@@ -32,7 +32,7 @@ as do the versions v6 is based upon.
 
 ### Authorization rules
 
-{{% added-in this=true %}} For checks perfomed upon `m.room.member` events, a
+{{% added-in this=true %}} For checks performed upon `m.room.member` events, a
 new point for `membership=knock` is added.
 
 Events must be signed by the server denoted by the `sender` key.