From 484a77757204c220ad1a46c94f3b6a434818d62c Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 2 Jul 2025 12:20:48 +0200 Subject: [PATCH] Fix typo (#2171) Signed-off-by: Johannes Marbach --- changelogs/client_server/newsfragments/2171.clarification | 1 + content/client-server-api/modules/event_replacements.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/2171.clarification diff --git a/changelogs/client_server/newsfragments/2171.clarification b/changelogs/client_server/newsfragments/2171.clarification new file mode 100644 index 00000000..3ccb2333 --- /dev/null +++ b/changelogs/client_server/newsfragments/2171.clarification @@ -0,0 +1 @@ +Fix various typos throughout the specification. diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md index 90c67ecf..c4563a88 100644 --- a/content/client-server-api/modules/event_replacements.md +++ b/content/client-server-api/modules/event_replacements.md @@ -364,7 +364,7 @@ property under `m.new_content`. A particular constraint applies to events which replace a [reply](#rich-replies): in contrast to the original reply, there should be no `m.in_reply_to` property -in the the `m.relates_to` object, since it would be redundant (see +in the `m.relates_to` object, since it would be redundant (see [Applying `m.new_content`](#applying-mnew_content) above, which notes that the original event's `m.relates_to` is preserved), as well as being contrary to the spirit of the event relationships mechanism which expects only one "parent" per