diff --git a/changelogs/client_server/newsfragments/1853.clarification b/changelogs/client_server/newsfragments/1853.clarification
new file mode 100644
index 000000000..3ccb23339
--- /dev/null
+++ b/changelogs/client_server/newsfragments/1853.clarification
@@ -0,0 +1 @@
+Fix various typos throughout the specification.
diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md
index b0ce72896..71f92bec2 100644
--- a/content/client-server-api/_index.md
+++ b/content/client-server-api/_index.md
@@ -2316,7 +2316,7 @@ following endpoint.
 This endpoint is particularly useful if the client has lost context on the aggregation for
 a parent event and needs to rebuild/verify it.
 
-When using the `recurse` parameter, note that there no way for a client to
+When using the `recurse` parameter, note that there is no way for a client to
 control how far the server recurses. If the client decides that the server's
 recursion level is insufficient, it could, for example, perform the recursion
 itself, or disable whatever feature requires more recursion.
diff --git a/data/api/client-server/relations.yaml b/data/api/client-server/relations.yaml
index b033e88f4..3f3d5baa1 100644
--- a/data/api/client-server/relations.yaml
+++ b/data/api/client-server/relations.yaml
@@ -312,7 +312,7 @@ components:
         Whether to additionally include events which only relate indirectly to the
         given event, i.e. events related to the given event via two or more direct relationships.
 
-        If set to `false`, only events which have direct a relation with the given
+        If set to `false`, only events which have a direct relation with the given
         event will be included.
 
         If set to `true`, all events which relate to the given event, or relate to