From 69511f43330092d026bf90f94f2d93841fb2c96c Mon Sep 17 00:00:00 2001 From: David Baker Date: Wed, 8 Mar 2023 11:23:01 +0000 Subject: [PATCH] Typos Co-authored-by: Daniel Abramov --- doc/mid-based-signalling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/mid-based-signalling.md b/doc/mid-based-signalling.md index 52a6f3b9..b17eb56b 100644 --- a/doc/mid-based-signalling.md +++ b/doc/mid-based-signalling.md @@ -11,7 +11,7 @@ can be quite large,would have to be duplicated in the JSON. Therefore, there's a advantage to taking to opportunity to migrate to an extensible event format now. We use the same event types for call invites and answers, so it is important that these events -are only send via to device message directly to client known to support them. They must not be +are only sent via to-device messages directly to clients known to support them. They must not be sent in rooms not supporting extensible events. This outlines how a switch to mid + media UUID based signalling would work in more detail.