From 9ad39c3782c3b2998680cf8a80587d88f1c42ce4 Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Fri, 20 Feb 2026 13:33:00 +0100 Subject: [PATCH 01/10] fix some typos, formatting and wording Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- content/client-server-api/_index.md | 2 +- content/client-server-api/modules/threading.md | 2 +- data/api/client-server/room_send.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index cb7e7391..0b913cc9 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -3413,7 +3413,7 @@ This specification describes the following relationship types: * [Event replacements](#event-replacements). * [Event annotations](#event-annotations-and-reactions). * [Threads](#threading). -* [References](#reference-relations) +* [References](#reference-relations). #### Aggregations of child events diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md index 9f87920a..e3365a0d 100644 --- a/content/client-server-api/modules/threading.md +++ b/content/client-server-api/modules/threading.md @@ -107,7 +107,7 @@ flag to `true`. ``` {{% boxes/note %}} -Clients which are acutely aware of threads (they do not render threads, but are otherwise +Clients which are aware of threads (they do not render threads, but are otherwise aware of the feature existing in the spec) can treat rich replies to an event with a `rel_type` of `m.thread` as a threaded reply, for conversation continuity on the threaded client's side. diff --git a/data/api/client-server/room_send.yaml b/data/api/client-server/room_send.yaml index 5c3d0019..7393d440 100644 --- a/data/api/client-server/room_send.yaml +++ b/data/api/client-server/room_send.yaml @@ -31,7 +31,7 @@ paths: The body of the request should be the content object of the event; the fields in this object will vary depending on the type of event. See - [Room Events](/client-server-api/#room-events) for the m. event specification. + [Room Events](/client-server-api/#room-events) for the `m.` event specification. Homeservers MUST allow clients to send `m.room.redaction` events with this endpoint for all room versions. In rooms with a version older than 11 they From 3cd366b1505ffbe0d0387a4d98a5bd29a1d99f7f Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Fri, 20 Feb 2026 13:38:52 +0100 Subject: [PATCH 02/10] fix inconsistent colon in tables Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- layouts/_partials/events/render-event.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/layouts/_partials/events/render-event.html b/layouts/_partials/events/render-event.html index 30a20974..b4988ae1 100644 --- a/layouts/_partials/events/render-event.html +++ b/layouts/_partials/events/render-event.html @@ -49,7 +49,7 @@ {{ if $state_key }} - State key + State key: {{ $state_key.description | markdownify }} {{ end }} From 55f1c15c2b14922dd926b4b77f033ef5ae3458cf Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Fri, 20 Feb 2026 14:02:13 +0100 Subject: [PATCH 03/10] format as code Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- data/event-schemas/schema/core-event-schema/event.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/event-schemas/schema/core-event-schema/event.yaml b/data/event-schemas/schema/core-event-schema/event.yaml index 422ecd53..8238642b 100644 --- a/data/event-schemas/schema/core-event-schema/event.yaml +++ b/data/event-schemas/schema/core-event-schema/event.yaml @@ -8,7 +8,7 @@ properties: type: object type: description: The type of event. This SHOULD be namespaced similar to Java package - naming conventions e.g. 'com.example.subdomain.event.type' + naming conventions e.g. `com.example.subdomain.event.type` type: string required: - type From 634acbcb89bdf38e6a0aab77f8de9d02190ed8e9 Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Fri, 20 Feb 2026 14:59:29 +0100 Subject: [PATCH 04/10] fix the name of the Foundation Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- config/_default/hugo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/_default/hugo.toml b/config/_default/hugo.toml index 76c3f9bb..8647c354 100644 --- a/config/_default/hugo.toml +++ b/config/_default/hugo.toml @@ -65,7 +65,7 @@ description = "Home of the Matrix specification for decentralised communication" # Everything below this are Site Params [params] -copyright = "The Matrix.org Foundation CIC" +copyright = "The Matrix.org Foundation C.I.C." [params.version] # must be one of "unstable", "current", "historical" From c12fbe45407bf859ea6a925c9c1c8cd49e70c426 Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Fri, 20 Feb 2026 15:01:34 +0100 Subject: [PATCH 05/10] add changelog Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- changelogs/client_server/newsfragments/2318.clarification | 1 + changelogs/internal/newsfragments/2318.clarification | 1 + 2 files changed, 2 insertions(+) create mode 100644 changelogs/client_server/newsfragments/2318.clarification create mode 100644 changelogs/internal/newsfragments/2318.clarification diff --git a/changelogs/client_server/newsfragments/2318.clarification b/changelogs/client_server/newsfragments/2318.clarification new file mode 100644 index 00000000..8b912430 --- /dev/null +++ b/changelogs/client_server/newsfragments/2318.clarification @@ -0,0 +1 @@ +Fix typos, formatting, wording. Contributed by @HarHarLinks. diff --git a/changelogs/internal/newsfragments/2318.clarification b/changelogs/internal/newsfragments/2318.clarification new file mode 100644 index 00000000..8b912430 --- /dev/null +++ b/changelogs/internal/newsfragments/2318.clarification @@ -0,0 +1 @@ +Fix typos, formatting, wording. Contributed by @HarHarLinks. From afa06ad330ce20a9d86e5d260e0b8067925454ad Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Mon, 23 Feb 2026 07:56:55 +0100 Subject: [PATCH 06/10] add comma Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- content/client-server-api/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 0b913cc9..ef08234e 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -3315,7 +3315,7 @@ PUT /rooms/!roomid:domain/state/m.room.bgd.color ### Redactions Since events are extensible it is possible for malicious users and/or -servers to add keys that are, for example offensive or illegal. Since +servers to add keys that are, for example, offensive or illegal. Since some events cannot be simply deleted, e.g. membership events, we instead 'redact' events. This involves removing all keys from an event that are not required by the protocol. This stripped down event is thereafter From 15a5cff2e047fb9de30ff30d2838422ff26c48a6 Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Tue, 24 Feb 2026 17:42:54 +0100 Subject: [PATCH 07/10] format some literals and keywords Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- data/api/client-server/definitions/event_filter.yaml | 6 +++--- .../client-server/definitions/room_event_filter.yaml | 2 +- data/api/client-server/definitions/sync_filter.yaml | 12 ++++++------ data/api/client-server/list_public_rooms.yaml | 4 ++-- data/api/client-server/login.yaml | 2 +- data/api/client-server/password_management.yaml | 2 +- data/api/client-server/registration.yaml | 6 +++--- data/api/server-server/public_rooms.yaml | 4 ++-- data/event-schemas/schema/m.room.server_acl.yaml | 2 +- 9 files changed, 20 insertions(+), 20 deletions(-) diff --git a/data/api/client-server/definitions/event_filter.yaml b/data/api/client-server/definitions/event_filter.yaml index d03c85da..ceb0d5bf 100644 --- a/data/api/client-server/definitions/event_filter.yaml +++ b/data/api/client-server/definitions/event_filter.yaml @@ -23,14 +23,14 @@ properties: not_senders: description: A list of sender IDs to exclude. If this list is absent then no senders are excluded. A matching sender will be excluded even if it is listed in the - `'senders'` filter. + `senders` filter. items: type: string type: array not_types: description: A list of event types to exclude. If this list is absent then no event types are excluded. A matching type will be excluded even if it is listed - in the `'types'` filter. A '*' can be used as a wildcard to match any sequence + in the `types` filter. A `*` can be used as a wildcard to match any sequence of characters. items: type: string @@ -43,7 +43,7 @@ properties: type: array types: description: A list of event types to include. If this list is absent then all - event types are included. A `'*'` can be used as a wildcard to match any sequence + event types are included. A `*` can be used as a wildcard to match any sequence of characters. items: type: string diff --git a/data/api/client-server/definitions/room_event_filter.yaml b/data/api/client-server/definitions/room_event_filter.yaml index ab8ef79e..6c9b705d 100644 --- a/data/api/client-server/definitions/room_event_filter.yaml +++ b/data/api/client-server/definitions/room_event_filter.yaml @@ -39,7 +39,7 @@ allOf: for more information. Defaults to `false`. not_rooms: description: A list of room IDs to exclude. If this list is absent then no rooms - are excluded. A matching room will be excluded even if it is listed in the `'rooms'` + are excluded. A matching room will be excluded even if it is listed in the `rooms` filter. items: type: string diff --git a/data/api/client-server/definitions/sync_filter.yaml b/data/api/client-server/definitions/sync_filter.yaml index 75544e94..f181aa22 100644 --- a/data/api/client-server/definitions/sync_filter.yaml +++ b/data/api/client-server/definitions/sync_filter.yaml @@ -17,15 +17,15 @@ properties: event_fields: description: List of event fields to include. If this list is absent then all fields are included. The entries are [dot-separated paths for each property](/appendices#dot-separated-property-paths) - to include. So ['content.body'] will include the 'body' field of the 'content' object. + to include. So `['content.body']` will include the `body` field of the `content` object. A server may include more fields than were requested. items: type: string type: array event_format: - description: The format to use for events. 'client' will return the events in - a format suitable for clients. 'federation' will return the raw event as received - over federation. The default is 'client'. + description: The format to use for events. `client` will return the events in + a format suitable for clients. `federation` will return the raw event as received + over federation. The default is `client`. enum: - client - federation @@ -45,7 +45,7 @@ properties: properties: not_rooms: description: A list of room IDs to exclude. If this list is absent then no rooms - are excluded. A matching room will be excluded even if it is listed in the `'rooms'` + are excluded. A matching room will be excluded even if it is listed in the `rooms` filter. This filter is applied before the filters in `ephemeral`, `state`, `timeline` or `account_data` items: @@ -65,7 +65,7 @@ properties: events that appear in the `ephemeral` property in the `/sync` response. include_leave: - description: Include rooms that the user has left in the sync, default false + description: Include rooms that the user has left in the sync. Defaults to `false`. type: boolean state: type: object diff --git a/data/api/client-server/list_public_rooms.yaml b/data/api/client-server/list_public_rooms.yaml index ef71ca63..c3e54403 100644 --- a/data/api/client-server/list_public_rooms.yaml +++ b/data/api/client-server/list_public_rooms.yaml @@ -226,7 +226,7 @@ paths: type: boolean description: |- Whether or not to include all known networks/protocols from - application services on the homeserver. Defaults to false. + application services on the homeserver. Defaults to `false`. example: false third_party_instance_id: type: string @@ -277,4 +277,4 @@ components: accessTokenQuery: $ref: definitions/security.yaml#/accessTokenQuery accessTokenBearer: - $ref: definitions/security.yaml#/accessTokenBearer \ No newline at end of file + $ref: definitions/security.yaml#/accessTokenBearer diff --git a/data/api/client-server/login.yaml b/data/api/client-server/login.yaml index 7251d4ff..a668a6bc 100644 --- a/data/api/client-server/login.yaml +++ b/data/api/client-server/login.yaml @@ -148,7 +148,7 @@ paths: known client device, a new device will be created. The given device ID must not be the same as a [cross-signing](/client-server-api/#cross-signing) key ID. - The server will auto-generate a device_id + The server will auto-generate a `device_id` if this is not specified. initial_device_display_name: type: string diff --git a/data/api/client-server/password_management.yaml b/data/api/client-server/password_management.yaml index b2d60559..3a1a570e 100644 --- a/data/api/client-server/password_management.yaml +++ b/data/api/client-server/password_management.yaml @@ -57,7 +57,7 @@ paths: type: boolean description: |- Whether the user's other access tokens, and their associated devices, should be - revoked if the request succeeds. Defaults to true. + revoked if the request succeeds. Defaults to `true`. When `false`, the server can still take advantage of the [soft logout method](/client-server-api/#soft-logout) for the user's remaining devices. diff --git a/data/api/client-server/registration.yaml b/data/api/client-server/registration.yaml index acb0b135..2813c0c2 100644 --- a/data/api/client-server/registration.yaml +++ b/data/api/client-server/registration.yaml @@ -126,7 +126,7 @@ paths: description: |- ID of the client device. If this does not correspond to a known client device, a new device will be created. The server - will auto-generate a device_id if this is not specified. + will auto-generate a `device_id` if this is not specified. example: GHTYAJCE initial_device_display_name: type: string @@ -139,11 +139,11 @@ paths: description: |- If true, an `access_token` and `device_id` should not be returned from this call, therefore preventing an automatic - login. Defaults to false. + login. Defaults to `false`. example: false refresh_token: type: boolean - description: If true, the client supports refresh tokens. + description: If `true`, the client supports refresh tokens. x-addedInMatrixVersion: "1.3" required: true responses: diff --git a/data/api/server-server/public_rooms.yaml b/data/api/server-server/public_rooms.yaml index 8beaecb2..41835f5a 100644 --- a/data/api/server-server/public_rooms.yaml +++ b/data/api/server-server/public_rooms.yaml @@ -49,7 +49,7 @@ paths: name: include_all_networks description: |- Whether or not to include all networks/protocols defined by application - services on the homeserver. Defaults to false. + services on the homeserver. Defaults to `false`. example: false schema: type: boolean @@ -121,7 +121,7 @@ paths: type: boolean description: |- Whether or not to include all known networks/protocols from - application services on the homeserver. Defaults to false. + application services on the homeserver. Defaults to `false`. example: false third_party_instance_id: type: string diff --git a/data/event-schemas/schema/m.room.server_acl.yaml b/data/event-schemas/schema/m.room.server_acl.yaml index c2ecf805..da490452 100644 --- a/data/event-schemas/schema/m.room.server_acl.yaml +++ b/data/event-schemas/schema/m.room.server_acl.yaml @@ -54,7 +54,7 @@ properties: type: boolean description: |- True to allow server names that are IP address literals. False to - deny. Defaults to true if missing or otherwise not a boolean. + deny. Defaults to `true` if missing or otherwise not a boolean. This is strongly recommended to be set to `false` as servers running with IP literal names are strongly discouraged in order to require From a34a6f8cc69508146f7e754cddaeca16630f0798 Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Wed, 25 Feb 2026 05:26:42 +0100 Subject: [PATCH 08/10] reference event type spec instead of duplicating Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- data/event-schemas/schema/core-event-schema/event.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/data/event-schemas/schema/core-event-schema/event.yaml b/data/event-schemas/schema/core-event-schema/event.yaml index 8238642b..119c984a 100644 --- a/data/event-schemas/schema/core-event-schema/event.yaml +++ b/data/event-schemas/schema/core-event-schema/event.yaml @@ -7,8 +7,7 @@ properties: When interacting with the REST API, this is the HTTP body. type: object type: - description: The type of event. This SHOULD be namespaced similar to Java package - naming conventions e.g. `com.example.subdomain.event.type` + description: The type of event, as defined by [the event type specification](#types-of-room-events). type: string required: - type From ddc6114159707ef28667e25d32d0afdca880431b Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Wed, 25 Feb 2026 05:31:33 +0100 Subject: [PATCH 09/10] update changelogs Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- changelogs/client_server/newsfragments/2318.clarification | 2 +- changelogs/internal/newsfragments/2318.clarification | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/changelogs/client_server/newsfragments/2318.clarification b/changelogs/client_server/newsfragments/2318.clarification index 8b912430..f8108646 100644 --- a/changelogs/client_server/newsfragments/2318.clarification +++ b/changelogs/client_server/newsfragments/2318.clarification @@ -1 +1 @@ -Fix typos, formatting, wording. Contributed by @HarHarLinks. +Fix various typos throughout the specification. Contributed by @HarHarLinks. diff --git a/changelogs/internal/newsfragments/2318.clarification b/changelogs/internal/newsfragments/2318.clarification index 8b912430..f8108646 100644 --- a/changelogs/internal/newsfragments/2318.clarification +++ b/changelogs/internal/newsfragments/2318.clarification @@ -1 +1 @@ -Fix typos, formatting, wording. Contributed by @HarHarLinks. +Fix various typos throughout the specification. Contributed by @HarHarLinks. From fa26eaab262b3f0d6d602e4fd6393b721eed769b Mon Sep 17 00:00:00 2001 From: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> Date: Wed, 25 Feb 2026 05:36:01 +0100 Subject: [PATCH 10/10] fix up link Signed-off-by: HarHarLinks <2803622+HarHarLinks@users.noreply.github.com> --- data/event-schemas/schema/core-event-schema/event.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/event-schemas/schema/core-event-schema/event.yaml b/data/event-schemas/schema/core-event-schema/event.yaml index 119c984a..291187ee 100644 --- a/data/event-schemas/schema/core-event-schema/event.yaml +++ b/data/event-schemas/schema/core-event-schema/event.yaml @@ -7,7 +7,7 @@ properties: When interacting with the REST API, this is the HTTP body. type: object type: - description: The type of event, as defined by [the event type specification](#types-of-room-events). + description: The type of event, as defined by [the event type specification](/client-server-api/#types-of-room-events). type: string required: - type