diff --git a/changelogs/client_server/newsfragments/1363.clarification b/changelogs/client_server/newsfragments/1363.clarification
new file mode 100644
index 00000000..3ccb2333
--- /dev/null
+++ b/changelogs/client_server/newsfragments/1363.clarification
@@ -0,0 +1 @@
+Fix various typos throughout the specification.
diff --git a/content/client-server-api/modules/reference_relations.md b/content/client-server-api/modules/reference_relations.md
index 7dec9d3c..f623c67d 100644
--- a/content/client-server-api/modules/reference_relations.md
+++ b/content/client-server-api/modules/reference_relations.md
@@ -1,7 +1,7 @@
 
 ### Reference relations
 
-{{% added-in v="1.4" %}}
+{{% added-in v="1.5" %}}
 
 Generically referencing another event can be done with a `rel_type` of `m.reference`
 as a form of [relationship](#forming-relationships-between-events). There is no
diff --git a/data/api/client-server/openid.yaml b/data/api/client-server/openid.yaml
index a6adeb7f..28c28516 100644
--- a/data/api/client-server/openid.yaml
+++ b/data/api/client-server/openid.yaml
@@ -47,7 +47,7 @@ paths:
           type: string
           name: userId
           description: |-
-            The user to request and OpenID token for. Should be the user who
+            The user to request an OpenID token for. Should be the user who
             is authenticated for the request.
           required: true
           x-example: "@alice:example.com"
diff --git a/data/api/client-server/receipts.yaml b/data/api/client-server/receipts.yaml
index 7a8dc279..27825001 100644
--- a/data/api/client-server/receipts.yaml
+++ b/data/api/client-server/receipts.yaml
@@ -49,7 +49,7 @@ paths:
           name: receiptType
           description: |-
             The type of receipt to send. This can also be `m.fully_read` as an
-            alternative to [`/read_makers`](/client-server-api/#post_matrixclientv3roomsroomidread_markers).
+            alternative to [`/read_markers`](/client-server-api/#post_matrixclientv3roomsroomidread_markers).
 
             Note that `m.fully_read` does not appear under `m.receipt`: this endpoint
             effectively calls `/read_markers` internally when presented with a receipt