Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-02 17:54:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

wording tweaks

Browse source
This commit is contained in:
Hubert Chathi 2019-11-26 13:06:13 -05:00
parent abbba4788c
commit 5f5f99fcc1
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
proposals/2366-key-verification-accept.md
View file

@ -25,9 +25,9 @@ or an in-room event.
After the `m.key.verification.accept` event is sent, either party can send an 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 `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 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 verification method, then the event sent by the user whose user ID is the
is used, and the event sent by the user whose ID is the largest is ignored. In smallest is used, and the other `m.key.verification.start` event is ignored.
the case of a single user verifying two of their devices, the device ID is 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, compared instead. If both parties send an `m.key.verification.start` event,
but they specify different verification methods, the verification should be but they specify different verification methods, the verification should be
cancelled with a `code` of `m.unexpected_message`. cancelled with a `code` of `m.unexpected_message`.