diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md
index e0ca8a83..b1b55159 100644
--- a/content/client-server-api/_index.md
+++ b/content/client-server-api/_index.md
@@ -1938,14 +1938,14 @@ parent event, for example.
 {{% /boxes/note %}}
 
 To allow the server to aggregate and find child events for a parent, the `m.relates_to`
-key of an event MUST be included in the cleartext (unencrypted) part of the event. It cannot be
+key of an event MUST be included in the plaintext copy of the event. It cannot be
 exclusively recorded in the encrypted payload as the server cannot decrypt the event
 for processing.
 
 {{% boxes/warning %}}
 If an encrypted event contains an `m.relates_to` in its payload, it should be
-ignored and instead favour the cleartext `m.relates_to` copy (including when there
-is no cleartext copy). This is to ensure the client's behaviour matches the server's
+ignored and instead favour the plaintext `m.relates_to` copy (including when there
+is no plaintext copy). This is to ensure the client's behaviour matches the server's
 capability to handle relationships.
 {{% /boxes/warning %}}
 
diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md
index af85196c..52597abd 100644
--- a/content/client-server-api/modules/event_replacements.md
+++ b/content/client-server-api/modules/event_replacements.md
@@ -41,9 +41,9 @@ replacement events.
 an event's content property, such as `formatted_body` (see [`m.room.message`
 `msgtypes`](#mroommessage-msgtypes)).
 
-#### Validity of message edit events
+#### Validity of replacement events
 
-There are a number of requirements on message edit events, which must be satisfied for the replacement to be considered valid:
+There are a number of requirements on replacement events, which must be satisfied for the replacement to be considered valid:
 
  * As with all event relationships, the original event and replacement event
    must have the same `room_id` (i.e. you cannot send an event in