Merge 19fa1c9cbf into fda3be5ee3

changelogs/client_server/newsfragments/2227.clarification

@@ -1 +0,0 @@
-Fix various typos throughout the specification.

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 in the `body` (using a prefix sequence)
+representation of the original message message in the `body` (using a prefix
-and `formatted_body` (using a custom HTML element) for clients that do not
+sequence) and `formatted_body` (using a custom HTML element) for clients that do
-support rich replies. This is no longer the case, but clients SHOULD still
+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