Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in room versions 1 through 5 #2066

Merged
merged 2 commits into from
Jan 25, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Loading