From 5f5f99fcc1c22ecdf919ef8a609c38625b83e5a9 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 26 Nov 2019 13:06:13 -0500 Subject: [PATCH] wording tweaks --- proposals/2366-key-verification-accept.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/2366-key-verification-accept.md b/proposals/2366-key-verification-accept.md index 75ffa2a4..cd48463d 100644 --- a/proposals/2366-key-verification-accept.md +++ b/proposals/2366-key-verification-accept.md @@ -25,9 +25,9 @@ or an in-room event. After the `m.key.verification.accept` event is sent, either party can send an `m.key.verification.start` event to begin the verification. If both parties send an `m.key.verification.start` event, and they both specify the same -verification method, then the event sent by the user whose ID is the smallest -is used, and the event sent by the user whose ID is the largest is ignored. In -the case of a single user verifying two of their devices, the device ID is +verification method, then the event sent by the user whose user ID is the +smallest is used, and the other `m.key.verification.start` event is ignored. +In the case of a single user verifying two of their devices, the device ID is compared instead. If both parties send an `m.key.verification.start` event, but they specify different verification methods, the verification should be cancelled with a `code` of `m.unexpected_message`.