From d9edb3fdf352c0d89cd7feaa8157dfb1eeb3fa84 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Tue, 19 Jan 2021 12:59:59 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- proposals/2874-single-ssss.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2874-single-ssss.md b/proposals/2874-single-ssss.md index f404a922..631fa156 100644 --- a/proposals/2874-single-ssss.md +++ b/proposals/2874-single-ssss.md @@ -7,7 +7,7 @@ decrypt different subsets of the secrets. However, the vast majority of users do not need this feature. This proposal defines how clients should behave if they only wish to support a -single key by defining which key clients should use if multiple keys are +single key, by defining which key clients should use if multiple keys are present. It also makes the `name` field in the `m.secret_storage.key.*` events optional, as this field was mainly added to allow a user to select between different keys. @@ -48,7 +48,7 @@ None ## Unstable prefix An unstable prefix is not needed for a behaviour change in choosing the key to -use as there are not event/endpoint changes. +use as there are no event/endpoint changes. Some clients already omit the `name` field (notably, matrix-js-sdk unintentionally does this -- mea culpa), and this does not seem to be causing