From dac9908193c8952a5a1b2d0d999d826b1a38032e Mon Sep 17 00:00:00 2001 From: benkuly <12199167+benkuly@users.noreply.github.com> Date: Fri, 4 Nov 2022 09:27:21 +0100 Subject: [PATCH] Update proposals/3925-replace-aggregation-with-full-event.md Co-authored-by: Jonas Platte Signed-off-by: benkuly --- proposals/3925-replace-aggregation-with-full-event.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/3925-replace-aggregation-with-full-event.md b/proposals/3925-replace-aggregation-with-full-event.md index 66e3910bee1..0c2db03c068 100644 --- a/proposals/3925-replace-aggregation-with-full-event.md +++ b/proposals/3925-replace-aggregation-with-full-event.md @@ -1,7 +1,7 @@ # MSC3925: m.replace aggregation with full event The Matrix DAG has immutable PDUs forming an auth chain. The client representation of this PDUs are simply called events. -While this events also have been immutable until v1.3, since v1.4 they aren't. +While these events also have been immutable until v1.3, since v1.4 they aren't. When a client sends a `m.replace` relation, [the server should replace the content of the original event](https://spec.matrix.org/v1.4/client-server-api/#server-side-replacement-of-content). There are some issues with this requirement: