From 943b5f72f4b921a0e2feb2dcb8e2b59065322456 Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Date: Tue, 23 Aug 2022 15:27:47 +0100
Subject: [PATCH] Update
 content/client-server-api/modules/event_replacements.md

---
 .../client-server-api/modules/event_replacements.md   | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md
index 9eb267f5..cac34fe8 100644
--- a/content/client-server-api/modules/event_replacements.md
+++ b/content/client-server-api/modules/event_replacements.md
@@ -131,10 +131,13 @@ ratchet entry should **not** be re-used.
 
 #### Applying `m.new_content`
 
-When applying a replacement, the `content` of the original event is replaced
-entirely by the `m.new_content` from the replacement event, with the exception
-of `m.relates_to`, which is left *unchanged*. (Any `m.relates_to` property
-within `m.new_content` should be ignored.)
+When applying a replacement, the `content` of the original event is treated as
+being overwritten entirely by `m.new_content`, with the exception of `m.relates_to`,
+which is left *unchanged*. Any `m.relates_to` property within `m.new_content`
+is ignored. (Note that server implementations must not *actually* overwrite
+the original event's `content`: instead the server presents it as being overwritten
+when it is served over the client-server API. See [Server-side replacement of content](#server-side-replacement-of-content)
+below.)
 
 For example, given a pair of events: