Update 3925-replace-aggregation-with-full-event.md

typos

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

@@ -4,9 +4,9 @@ The Matrix DAG has immutable PDUs forming an auth chain. The client representati
 While this 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 requirment:
-* Changing the fundamental concept of immutable events is confusing. The server can response different event contents for the same `event_id`.
-* If an event with `m.replace` relation is deleted, the client would need to detect, if the content was replaced and possibly needs to fetch the original event.
+There are some issues with this requirement:
+* Changing the fundamental concept of immutable events is confusing. The server can respond with different event contents for the same `event_id`.
+* If an event with `m.replace` relation is deleted, the client would need to detect, if the original content was replaced and possibly needs to fetch the original content.
 * There is an additional server call needed, when the replacing event is encrypted, because the server cannot replace the original event content.
 * There are also some other issues with this spec paragraph, which are discussed [here](https://github.com/matrix-org/matrix-spec/issues/1299)