From 2abb1fa9f6102921b1676c60c089ab401203f131 Mon Sep 17 00:00:00 2001 From: Sumner Evans Date: Mon, 27 May 2024 18:04:52 -0600 Subject: [PATCH] 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 --- content/client-server-api/modules/end_to_end_encryption.md | 2 +- 1 file changed, 1 insertion(+), 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 index 9099a50ce..caef42b46 100644 --- 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.