From a6977f19c53e6ccd366b972d95e7ce4bef5eb5f8 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Mon, 28 Oct 2019 12:58:27 -0400 Subject: [PATCH] Update proposals/1219-storing-megolm-keys-serverside.md Co-Authored-By: aditsachde <23707194+aditsachde@users.noreply.github.com> --- proposals/1219-storing-megolm-keys-serverside.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/1219-storing-megolm-keys-serverside.md b/proposals/1219-storing-megolm-keys-serverside.md index ff74eb169..95430fe21 100644 --- a/proposals/1219-storing-megolm-keys-serverside.md +++ b/proposals/1219-storing-megolm-keys-serverside.md @@ -129,7 +129,7 @@ results in 0, and ensure that the total length of the decoded string is 35 bytes. Clients must then remove the first two bytes and the last byte, and use the resulting string as the private key to decrypt backups. -#### Enconding the recovery key for server-side storage via MSC1946 +#### Encoding the recovery key for server-side storage via MSC1946 If MSC1946 is used to store the key on the server, it must be stored using the `account_data` type `m.megolm_backup.v1`.