Skip to content

Commit d9edb3f

Browse files
uhoregrichvdh
andauthored
Apply suggestions from code review
Co-authored-by: Richard van der Hoff <[email protected]>
1 parent 11d6e42 commit d9edb3f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

proposals/2874-single-ssss.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ decrypt different subsets of the secrets. However, the vast majority of users
77
do not need this feature.
88

99
This proposal defines how clients should behave if they only wish to support a
10-
single key by defining which key clients should use if multiple keys are
10+
single key, by defining which key clients should use if multiple keys are
1111
present. It also makes the `name` field in the `m.secret_storage.key.*` events
1212
optional, as this field was mainly added to allow a user to select between
1313
different keys.
@@ -48,7 +48,7 @@ None
4848
## Unstable prefix
4949

5050
An unstable prefix is not needed for a behaviour change in choosing the key to
51-
use as there are not event/endpoint changes.
51+
use as there are no event/endpoint changes.
5252

5353
Some clients already omit the `name` field (notably, matrix-js-sdk
5454
unintentionally does this -- mea culpa), and this does not seem to be causing

0 commit comments

Comments
 (0)