MSC3925: m.replace aggregation with full event

proposals/3925-replace-aggregation-with-full-event.md

@@ -1,6 +1,5 @@
 # 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 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).
 
@@ -22,7 +21,7 @@ The additional server call is already needed for encrypted events and would be s
 
 ## Potential issues
 
-* There could be clients, which rely on the current behavior.
+* There could be clients which rely on the current behavior.
 * It is not as easy for clients like as in the current spec to get the current content of an event by just looking into `content.body`. While this true, it is also a relatively inconsistent behavior. Future replacements of the event would be rendered as "* new content". So the event with the replaced event does look different (without "*") despite the fact, that it is also replaced.
 
 ## Alternatives
@@ -35,4 +34,4 @@ The additional server call is already needed for encrypted events and would be s
 
 ## Unstable prefix
 
-I'm not sure, if we need an unstable prefix, because the aggregation would just be extended by additional fields.
+I'm not sure if we need an unstable prefix, because the aggregation would just be extended by additional fields.