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] 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