e2ee/device verification/error handling: fix typo start -> request

It used to be possible to create a start request without a request, but this was deprecated. Signed-off-by: Sumner Evans <[email protected]>
matrix-org · May 28, 2024 · 2abb1fa · 2abb1fa
1 parent d4b30ef
commit 2abb1fa
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md
@@ -616,7 +616,7 @@ what to do when an error happens:
 -   When a device receives an unknown `transaction_id`, it should send an
     appropriate `m.key.verification.cancel` message to the other device
     indicating as such. This does not apply for inbound
-    `m.key.verification.start` or `m.key.verification.cancel` messages.
+    `m.key.verification.request` or `m.key.verification.cancel` messages.
 -   If the device receives a message out of sequence or that it was not
     expecting, it should notify the other device with an appropriate
     `m.key.verification.cancel` message.