Skip to content

Commit

Permalink
Fix typo in room versions 1 through 5 (#2066)
Browse files Browse the repository at this point in the history
Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
  • Loading branch information
zecakeh authored Jan 25, 2025
1 parent 9e0f2aa commit cabe846
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions changelogs/room_versions/newsfragments/2066.clarification
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Fix various typos throughout the specification.
2 changes: 1 addition & 1 deletion content/rooms/fragments/v1-auth-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ The rules are as follows:
does not match the `sender` domain of the create event, reject.
4. If type is `m.room.aliases`:
1. If event has no `state_key`, reject.
2. If sender's domain doesn't matches `state_key`, reject.
2. If sender's domain doesn't match `state_key`, reject.
3. Otherwise, allow.
5. If type is `m.room.member`:
1. If there is no `state_key` property, or no `membership` property in
Expand Down
2 changes: 1 addition & 1 deletion content/rooms/fragments/v3-auth-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ The complete list of rules, as of room version 3, is as follows:
does not match the `sender` domain of the create event, reject.
4. If type is `m.room.aliases`:
1. If event has no `state_key`, reject.
2. If sender's domain doesn't matches `state_key`, reject.
2. If sender's domain doesn't match `state_key`, reject.
3. Otherwise, allow.
5. If type is `m.room.member`:
1. If there is no `state_key` property, or no `membership` property in
Expand Down

0 comments on commit cabe846

Please sign in to comment.