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

Fix typos.

Browse source 
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Patrick Cloke 2021-06-24 08:20:44 -04:00 • committed by Richard van der Hoff
parent f4e2d925e3
commit 3377d55c28
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -81,7 +81,7 @@ enforced over federation by event authorisation).<sup id="a3">[3](#f3)</sup>
## Summary of the behaviour of join rules
See the [join rules](https://matrix.org/docs/spec/client_server/r0.6.1#m-room-join-rules)
specification for full details, the summary below is meant to highlight the differences
specification for full details; the summary below is meant to highlight the differences
between `public`, `invite`, and `restricted`.
* `public`: anyone can join, subject to `ban` and `server_acls`, as today.
@ -100,7 +100,7 @@ Increased trust to enforce the join rules during calls to `/join`, `/make_join`,
and `/send_join` is placed in the homeservers whose users can issue invites.
Although it is possible for those homeservers to issue a join event in bad faith,
there is no real-world benefit to doing this as those homeservers could easily
side-side the restriction by issuing an invite first anyway.
side-step the restriction by issuing an invite first anyway.
## Unstable prefix