Apply suggestions from code review

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
pull/1271/head
Hubert Chathi 2 years ago committed by GitHub
parent 9d8e17fb22
commit c0d54ab4d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -434,7 +434,7 @@ shared by the other messages of that session.
In general, verification operates as follows: 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 request event. If the verification is being requested in a room, this will
be an event with type `m.room.message` and `msgtype` be an event with type `m.room.message` and `msgtype`
`m.key.verification.request`; if the verification is being requested using `m.key.verification.request`; if the verification is being requested using

@ -11,7 +11,7 @@ properties:
body: body:
type: string type: string
description: |- 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 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. 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 However, your client does not support this method, so you will need to use
@ -58,6 +58,7 @@ properties:
- from_device - from_device
- methods - methods
- msgtype - msgtype
- to
type: object type: object
type: type:
enum: enum:

Loading…
Cancel
Save