~sircmpwn/sr.ht-docs

404f86cce1c23f0a4592d82bbf9cd883779e4ad3 — Ajay Raghavan 3 months ago 08862f3
user's -> users', changed sentence structure
1 files changed, 6 insertions(+), 6 deletions(-)

M lists.sr.ht/index.md
M lists.sr.ht/index.md => lists.sr.ht/index.md +6 -6
@@ 106,12 106,12 @@ fine-grained enough to support many access scenarios, here are some examples:

## Announcement lists

A list that only you can write to is useful for announcements. Remove all user's
"post" and "reply" permissions to prevent them from submitting — owners are
always able to post. You can optionally leave the "reply" permission enabled to
allow people to respond to announcements, but be aware that their responses will
be sent out to all subscribers, which is usually undesirable for low-volume
announcement lists.
A list that only you can write to is useful for announcements. To create such
a list, remove all users' "post" and "reply" permissions, to prevent them from
submitting. Owners are always able to post, of course. You could optionally
leave the "reply" permission enabled to allow people to respond to announcements,
but beware that their responses will be sent out to all subscribers, which is
usually undesirable for low-volume announcement lists.

## Write-only security lists