From fca945c8accd37404c1b6961a7d9ee61290f5a9e Mon Sep 17 00:00:00 2001 From: Tol Wassman Date: Sat, 11 Oct 2025 23:56:47 +0000 Subject: [PATCH] fix typo --- content/client-server-api/modules/rich_replies.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/client-server-api/modules/rich_replies.md b/content/client-server-api/modules/rich_replies.md index 37b8bc9e..4e1c67b7 100644 --- a/content/client-server-api/modules/rich_replies.md +++ b/content/client-server-api/modules/rich_replies.md @@ -20,9 +20,9 @@ Previously, a rich reply could only reference another `m.room.message` event. {{% boxes/note %}} {{% changed-in v="1.13" %}} In previous versions of the specification, rich replies could include a fallback -representation of the original message message in the `body` (using a prefix -sequence) and `formatted_body` (using a custom HTML element) for clients that do -not support rich replies. This is no longer the case, but clients SHOULD still +representation of the original message in the `body` (using a prefix sequence) +and `formatted_body` (using a custom HTML element) for clients that do not +support rich replies. This is no longer the case, but clients SHOULD still remove this fallback before rendering the event. To strip the fallback on the `body`, the client should iterate over each