From 06ee66d6b08b3162ca94df38f9b82b5e4a49860e Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Wed, 23 Oct 2019 15:30:07 +0100 Subject: [PATCH] Apply suggestions from code review Co-Authored-By: Kitsune Ral Co-Authored-By: David Baker --- proposals/2241-e2e-verification-in-dms.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/2241-e2e-verification-in-dms.md b/proposals/2241-e2e-verification-in-dms.md index ea813fdb..eccc36c2 100644 --- a/proposals/2241-e2e-verification-in-dms.md +++ b/proposals/2241-e2e-verification-in-dms.md @@ -78,9 +78,9 @@ case this proposal should follow suit. methods may use the device IDs as part of the verification process. Clients should ignore `m.key.verification.start` events that correspond to -verification requests that it did not send. +verification requests that they did not send. -Clients may use this event as a place in the room's timeline do display +Clients may use this event as a place in the room's timeline to display progress of the key verification process and to interact with the user as necessary. @@ -129,7 +129,7 @@ Clients should ignore events with an `m.relates_to` that have a `rel_type` of `m.reference` that refer to a verification where it is not the requester nor the accepter. -### SAS verification +### SAS verification The messages used in SAS verification are the same as those currently defined, except that instead of the `transaction_id` property, an `m.relates_to`