Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-05-01 06:34:09 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Use consistent capitalisation of rules

Browse source
This commit is contained in:
David Robertson 2022-11-17 14:56:47 +00:00
parent 1b223e77e3
commit 6403d28310
No known key found for this signature in database
GPG key ID: 903ECE108A39DEDD
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/client-server-api/modules/push.md
View file

@ -144,16 +144,16 @@ the value of `kind`.
The different `kind`s of rule, in the order that they are checked, are: The different `kind`s of rule, in the order that they are checked, are:
1. **Override Rules (`override`).** 1. **Override rules (`override`).**
The highest priority rules are user-configured overrides. The highest priority rules are user-configured overrides.
1. **Content-specific Rules (`content`).** 1. **Content-specific rules (`content`).**
These configure behaviour for (unencrypted) messages that match certain These configure behaviour for (unencrypted) messages that match certain
patterns. Content rules take one parameter: `pattern`, that gives the patterns. Content rules take one parameter: `pattern`, that gives the
glob pattern to match against. This is treated in the same way as glob pattern to match against. This is treated in the same way as
`pattern` for `event_match`. `pattern` for `event_match`.
1. **Room-specific Rules (`room`).** 1. **Room-specific rules (`room`).**
These rules change the behaviour of all messages for a given room. The These rules change the behaviour of all messages for a given room. The
`rule_id` of a room rule is always the ID of the room that it affects. `rule_id` of a room rule is always the ID of the room that it affects.