From 0841f31ce48c2f337f5407991b1281b2934e4209 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Wed, 24 Mar 2021 10:24:06 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- proposals/2732-olm-fallback-keys.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2732-olm-fallback-keys.md b/proposals/2732-olm-fallback-keys.md index 7b060bec..5ab90117 100644 --- a/proposals/2732-olm-fallback-keys.md +++ b/proposals/2732-olm-fallback-keys.md @@ -50,7 +50,7 @@ marks that they have been used. A new response parameter, `device_unused_fallback_key_types`, is added to `/sync`. This is an array listing the key algorithms for which the server has -an unused fallback key for the user. If the client wants the server to have a +an unused fallback key for the device. If the client wants the server to have a fallback key for a given key algorithm, but that algorithm is not listed in `device_unused_fallback_key_types`, the client will upload a new key as above. @@ -65,7 +65,7 @@ Example: Response: -```json +```jsonc { // other fields... "device_unused_fallback_key_types": ["signed_curve25519"]