diff --git a/api/server-server/joins-v1.yaml b/api/server-server/joins-v1.yaml
index 8defda20..86dd1722 100644
--- a/api/server-server/joins-v1.yaml
+++ b/api/server-server/joins-v1.yaml
@@ -63,7 +63,7 @@ paths:
         200:
           description: |-
             A template to be used for the rest of the `Joining Rooms`_ handshake. Note that
-            events have a different format depending on the  room version - check the
+            events have a different format depending on the room version - check the
             `room version specification`_ for precise event formats. **The response body
             here describes the common event fields in more detail and may be missing other
             required fields for a PDU.**
@@ -172,7 +172,7 @@ paths:
 
         Submits a signed join event to the resident server for it
         to accept it into the room's graph. Note that events have
-        a different format depending on the  room version - check
+        a different format depending on the room version - check
         the `room version specification`_ for precise event formats.
         **The request and response body here describes the common
         event fields in more detail and may be missing other required
diff --git a/api/server-server/joins-v2.yaml b/api/server-server/joins-v2.yaml
index 585ab4b8..d9569684 100644
--- a/api/server-server/joins-v2.yaml
+++ b/api/server-server/joins-v2.yaml
@@ -44,7 +44,7 @@ paths:
 
         Submits a signed join event to the resident server for it
         to accept it into the room's graph. Note that events have
-        a different format depending on the  room version - check
+        a different format depending on the room version - check
         the `room version specification`_ for precise event formats.
         **The request and response body here describes the common
         event fields in more detail and may be missing other required
diff --git a/api/server-server/leaving-v1.yaml b/api/server-server/leaving-v1.yaml
index cd07406e..2d7785f6 100644
--- a/api/server-server/leaving-v1.yaml
+++ b/api/server-server/leaving-v1.yaml
@@ -54,7 +54,7 @@ paths:
         200:
           description: |-
             A template to be used to call ``/send_leave``. Note that
-            events have a different format depending on the  room version - check the
+            events have a different format depending on the room version - check the
             `room version specification`_ for precise event formats. **The response body
             here describes the common event fields in more detail and may be missing other
             required fields for a PDU.**
@@ -149,7 +149,7 @@ paths:
 
         Submits a signed leave event to the resident server for it
         to accept it into the room's graph. Note that events have
-        a different format depending on the  room version - check
+        a different format depending on the room version - check
         the `room version specification`_ for precise event formats.
         **The request and response body here describes the common
         event fields in more detail and may be missing other required
diff --git a/api/server-server/leaving-v2.yaml b/api/server-server/leaving-v2.yaml
index ed16773e..ac3111ed 100644
--- a/api/server-server/leaving-v2.yaml
+++ b/api/server-server/leaving-v2.yaml
@@ -44,7 +44,7 @@ paths:
 
         Submits a signed leave event to the resident server for it
         to accept it into the room's graph. Note that events have
-        a different format depending on the  room version - check
+        a different format depending on the room version - check
         the `room version specification`_ for precise event formats.
         **The request and response body here describes the common
         event fields in more detail and may be missing other required
diff --git a/api/server-server/transactions.yaml b/api/server-server/transactions.yaml
index 9cc8be75..b34c1902 100644
--- a/api/server-server/transactions.yaml
+++ b/api/server-server/transactions.yaml
@@ -38,7 +38,7 @@ paths:
         The sending server must wait and retry for a 200 OK response before sending a
         transaction with a different ``txnId`` to the receiving server.
 
-        Note that events have a different format depending on the  room version - check
+        Note that events have a different format depending on the room version - check
         the `room version specification`_ for precise event formats.
       operationId: sendTransaction
       security: