wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix typo.

Browse source 
Co-authored-by: Matthew Hodgson <matthew@matrix.org>
This commit is contained in:
Patrick Cloke 2021-07-13 08:35:31 -04:00 • committed by Richard van der Hoff
parent 1f7481bfbd
commit 7aeca9ccb6
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
proposals/3083-restricted-rooms.md
View file

@ -128,7 +128,7 @@ as the `restricted` join rule value do not need unstable prefixes.
It may seem that just having the `allow` key with `public` join rules is enough It may seem that just having the `allow` key with `public` join rules is enough
(as originally suggested in [MSC2962](https://github.com/matrix-org/matrix-doc/pull/2962)), (as originally suggested in [MSC2962](https://github.com/matrix-org/matrix-doc/pull/2962)),
but there are concerns that changing the behaviour of a pre-existing a `public` but there are concerns that changing the behaviour of a pre-existing `public`
join rule may cause security issues in older implementations (that do not yet join rule may cause security issues in older implementations (that do not yet
understand the new behaviour). This could be solved by introducing a new room understand the new behaviour). This could be solved by introducing a new room
version, thus it seems clearer to introduce a new join rule -- `restricted`. version, thus it seems clearer to introduce a new join rule -- `restricted`.