Apply suggestions from code review
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
parent
9d8e17fb22
commit
c0d54ab4d9
2 changed files with 3 additions and 2 deletions
|
@ -434,7 +434,7 @@ shared by the other messages of that session.
|
|||
|
||||
In general, verification operates as follows:
|
||||
|
||||
- Alice requests a key verification with Bob by sending an key verification
|
||||
- Alice requests a key verification with Bob by sending a key verification
|
||||
request event. If the verification is being requested in a room, this will
|
||||
be an event with type `m.room.message` and `msgtype`
|
||||
`m.key.verification.request`; if the verification is being requested using
|
||||
|
|
|
@ -11,7 +11,7 @@ properties:
|
|||
body:
|
||||
type: string
|
||||
description: |-
|
||||
a fallback message to alert users that their client does not support
|
||||
A fallback message to alert users that their client does not support
|
||||
the key verification framework, and that they should use a different method
|
||||
to verify keys. For example, "Alice is requesting to verify keys with you.
|
||||
However, your client does not support this method, so you will need to use
|
||||
|
@ -58,6 +58,7 @@ properties:
|
|||
- from_device
|
||||
- methods
|
||||
- msgtype
|
||||
- to
|
||||
type: object
|
||||
type:
|
||||
enum:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue