From 6403d283104363490a91852da846bc0e55c7988c Mon Sep 17 00:00:00 2001 From: David Robertson Date: Thu, 17 Nov 2022 14:56:47 +0000 Subject: [PATCH] Use consistent capitalisation of `rules` --- content/client-server-api/modules/push.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/client-server-api/modules/push.md b/content/client-server-api/modules/push.md index 540b3cf9..b9e2096d 100644 --- a/content/client-server-api/modules/push.md +++ b/content/client-server-api/modules/push.md @@ -144,16 +144,16 @@ the value of `kind`. 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. -1. **Content-specific Rules (`content`).** +1. **Content-specific rules (`content`).** These configure behaviour for (unencrypted) messages that match certain patterns. Content rules take one parameter: `pattern`, that gives the glob pattern to match against. This is treated in the same way as `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 `rule_id` of a room rule is always the ID of the room that it affects.