From d10deb028aacdc509a73c261cdfcef7bdee680cb Mon Sep 17 00:00:00 2001 From: Sumner Evans Date: Fri, 7 Jun 2024 10:44:36 -0600 Subject: [PATCH] fixup! e2ee/device verification: move general error handling under framework 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 64b97bb9..b83b3780 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -471,7 +471,7 @@ In general, verification operates as follows: that the verification was successful. Verifications can be cancelled by either device at any time by sending an -[`m.key.verification.cancel`](#mkeyverificationcancel) event with a `code` field +[m.key.verification.cancel](#mkeyverificationcancel) event with a `code` field that indicates the reason it was cancelled. The [Error handling during key verification](#error-handling-during-key-verification) section explains specific situations where cancellation messages should be sent.