From 97a8b0bb1376f721604b9c8ba901b2de667967ba Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Mon, 17 Jan 2022 13:12:56 -0700 Subject: [PATCH] spelling --- proposals/2675-aggregations-server.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2675-aggregations-server.md b/proposals/2675-aggregations-server.md index 5808dbec..cead105c 100644 --- a/proposals/2675-aggregations-server.md +++ b/proposals/2675-aggregations-server.md @@ -101,7 +101,7 @@ with events they return: - `GET /rooms/{roomId}/context/{eventId}` - `GET /rooms/{roomId}/event/{eventId}` - `GET /sync`, only for room sections in the response where `limited` field - is `true`; this amounts to all rooms in the response if + is `true`; this amounts to all rooms in the response if the `since` request parameter was not passed, also known as an initial sync. - `GET /relations`, as proposed in this MSC. @@ -271,7 +271,7 @@ specifying the exact server behaviour to [MSC3570](https://github.com/matrix-org ### Servers might not be aware of all relations of an event The response of `/relations` might be incomplete because the homeserver -potentially doesn't have the full DAG of the room. The federation API doens't +potentially doesn't have the full DAG of the room. The federation API doesn't have an equivalent of the `/relations` API, so has no way but to fetch the full DAG over federation to assure itself that it is aware of all relations.