diff --git a/api/server-server/definitions/invite_event.yaml b/api/server-server/definitions/invite_event.yaml index 1f8b29d05..674ef2c94 100644 --- a/api/server-server/definitions/invite_event.yaml +++ b/api/server-server/definitions/invite_event.yaml @@ -14,7 +14,7 @@ type: object title: Invite Event description: |- - An invite event. Note that events have a different version depending on the + An invite event. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. allOf: - type: object diff --git a/api/server-server/definitions/transaction.yaml b/api/server-server/definitions/transaction.yaml index a77f6f8a3..08f3738ab 100644 --- a/api/server-server/definitions/transaction.yaml +++ b/api/server-server/definitions/transaction.yaml @@ -33,7 +33,7 @@ properties: type: array description: |- List of persistent updates to rooms. Must not include more than 50 PDUs. Note that - events have a different version 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. items: type: object diff --git a/api/server-server/event_auth.yaml b/api/server-server/event_auth.yaml index 262ea2827..0db0d4015 100644 --- a/api/server-server/event_auth.yaml +++ b/api/server-server/event_auth.yaml @@ -59,7 +59,7 @@ paths: description: |- The full set of authorization events that make up the state of the room, and their authorization events, recursively. Note that - events have a different version depending on the room version - + events have a different format depending on the room version - check the `room version specification`_ for precise event formats. items: type: object @@ -109,7 +109,7 @@ paths: type: array description: |- The auth chain (the "remote auth"). Note that events have a different - version depending on the room version - check the `room version specification`_ + format depending on the room version - check the `room version specification`_ for precise event formats. items: type: object @@ -162,7 +162,7 @@ paths: description: |- The auth chain the receiver has, and used to determine the auth chain differences (the "local auth"). Note that events have a different - version depending on the room version - check the `room version specification`_ + format depending on the room version - check the `room version specification`_ for precise event formats. items: type: object diff --git a/api/server-server/events.yaml b/api/server-server/events.yaml index e7cb52cde..1f1a802dd 100644 --- a/api/server-server/events.yaml +++ b/api/server-server/events.yaml @@ -60,7 +60,7 @@ paths: description: |- The full set of authorization events that make up the state of the room, and their authorization events, recursively. Note that - events have a different version depending on the room version - + events have a different format depending on the room version - check the `room version specification`_ for precise event formats. items: type: object @@ -76,7 +76,7 @@ paths: type: array description: |- The fully resolved state of the room at the given event. Note that - events have a different version depending on the room version - + events have a different format depending on the room version - check the `room version specification`_ for precise event formats. items: type: object diff --git a/api/server-server/invites-v1.yaml b/api/server-server/invites-v1.yaml index f397fc91b..2ad0f2201 100644 --- a/api/server-server/invites-v1.yaml +++ b/api/server-server/invites-v1.yaml @@ -39,7 +39,7 @@ paths: which receive a v1 invite request must assume that the room version is either ``"1"`` or ``"2"``. - Note that events have a different version depending on the room version - check the + Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. **The request and response bodies here describe the common event fields in more detail and may be missing other required fields for a PDU.** @@ -151,7 +151,7 @@ paths: 200: description: |- The event with the invited server's signature added. All other fields of the events - should remain untouched. Note that events have a different version depending on the + should remain untouched. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. schema: type: array diff --git a/api/server-server/invites-v2.yaml b/api/server-server/invites-v2.yaml index d57a7ba29..c459a8485 100644 --- a/api/server-server/invites-v2.yaml +++ b/api/server-server/invites-v2.yaml @@ -43,7 +43,7 @@ paths: which receive a 400 or 404 response to this endpoint should retry using the v1 API as the server may be older, if the room version is "1" or "2". - Note that events have a different version depending on the room version - check the + Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. **The request and response bodies here describe the common event fields in more detail and may be missing other required fields for a PDU.** @@ -154,7 +154,7 @@ paths: 200: description: |- The event with the invited server's signature added. All other fields of the events - should remain untouched. Note that events have a different version depending on the + should remain untouched. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. schema: type: object diff --git a/api/server-server/joins.yaml b/api/server-server/joins.yaml index fca273b57..ad033001d 100644 --- a/api/server-server/joins.yaml +++ b/api/server-server/joins.yaml @@ -62,7 +62,7 @@ paths: 200: description: |- A template to be used for the rest of the `Joining Rooms`_ handshake. Note that - events have a different version 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.** @@ -77,7 +77,7 @@ paths: example: "2" event: description: |- - An unsigned template event. Note that events have a different version + An unsigned template event. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. type: object @@ -165,7 +165,7 @@ paths: description: |- 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 version 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 @@ -265,7 +265,7 @@ paths: auth_chain: type: array description: |- - The auth chain. Note that events have a different version depending on + The auth chain. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. items: diff --git a/api/server-server/leaving.yaml b/api/server-server/leaving.yaml index 6c0d49598..95ee68805 100644 --- a/api/server-server/leaving.yaml +++ b/api/server-server/leaving.yaml @@ -53,7 +53,7 @@ paths: 200: description: |- A template to be used to call ``/send_leave``. Note that - events have a different version 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.** @@ -69,7 +69,7 @@ paths: example: "2" event: description: |- - An unsigned template event. Note that events have a different version + An unsigned template event. Note that events have a different format depending on the room version - check the `room version specification`_ for precise event formats. type: object @@ -144,7 +144,7 @@ paths: description: |- 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 version 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 38073e408..9cc8be75d 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 version 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: