From edc4f38c84fd3ff1fd33ab4ceef685e06743080c Mon Sep 17 00:00:00 2001 From: Sumner Evans Date: Fri, 7 Jun 2024 10:29:27 -0600 Subject: [PATCH] fixup! e2ee/device verification: move general error handling under framework Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- 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 e93e54d3..4faa7efa 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -603,7 +603,7 @@ At any point the interactive verification can go wrong. The following describes what to do when an error happens: - Alice or Bob can cancel the verification at any time. An - `m.key.verification.cancel` message must be sent to signify the + [`m.key.verification.cancel`](#mkeyverificationcancel) message must be sent to signify the cancellation. - The verification can time out. Clients should time out a verification that does not complete within 10 minutes. Additionally, clients should expire a