summary refs log tree commit diff
diff options
context:
space:
mode:
authorKim Brose <2803622+HarHarLinks@users.noreply.github.com>2025-04-30 15:27:08 +0200
committerGitHub <noreply@github.com>2025-04-30 14:27:08 +0100
commitf79811ed80bebaa5b187637af6d16d413b07166e (patch)
treed7b26e4d73aebcaff800384b42e7587325444503
parentMinor performance improvements to notifier/replication (#18367) (diff)
downloadsynapse-f79811ed80bebaa5b187637af6d16d413b07166e.tar.xz
Fix typo in docs about `push` (#18320)
-rw-r--r--changelog.d/18320.doc1
-rw-r--r--docs/usage/configuration/config_documentation.md2
2 files changed, 2 insertions, 1 deletions
diff --git a/changelog.d/18320.doc b/changelog.d/18320.doc
new file mode 100644

index 0000000000..d84c279940 --- /dev/null +++ b/changelog.d/18320.doc
@@ -0,0 +1 @@ +Fix typo in docs about the `push` config option. Contributed by @HarHarLinks. diff --git a/docs/usage/configuration/config_documentation.md b/docs/usage/configuration/config_documentation.md
index 73fd9622ce..19dc9dd356 100644 --- a/docs/usage/configuration/config_documentation.md +++ b/docs/usage/configuration/config_documentation.md
@@ -4018,7 +4018,7 @@ This option has a number of sub-options. They are as follows: * `include_content`: Clients requesting push notifications can either have the body of the message sent in the notification poke along with other details like the sender, or just the event ID and room ID (`event_id_only`). - If clients choose the to have the body sent, this option controls whether the + If clients choose to have the body sent, this option controls whether the notification request includes the content of the event (other details like the sender are still included). If `event_id_only` is enabled, it has no effect.