Clarify that verifications without a request only happens over to-dev…

…ice (#1345)
matrix-org · Nov 17, 2022 · 6492277 · 6492277
1 parent 1e393fb
commit 6492277
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/changelogs/client_server/newsfragments/1345.clarification b/changelogs/client_server/newsfragments/1345.clarification
@@ -0,0 +1 @@
+Clarify parts of the end-to-end encryption sections.
diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md
@@ -551,7 +551,8 @@ then the device IDs should be compared instead.  If the two
 method, then the verification should be cancelled with a `code` of
 `m.unexpected_message`.
 
-An `m.key.verification.start` message can also be sent independently of any
+When verifying using to-device messages, an `m.key.verification.start`
+message can also be sent independently of any
 request, specifying the verification method to use. This behaviour is
 deprecated, and new clients should not begin verifications in this way.
 However, clients should handle such verifications started by other clients.