sites

commit ef2b9c7e8b495c7e070657d6777b20b7ed63aa5c
parent 684f29d1ed526853b7a519f555680612aa69d819
Author: Raf Czlonka <rczlonka@gmail.com>
Date:   Tue,  6 Mar 2018 03:29:25 +0000

Use "mailing list(s)" consistently.

Diffstat:
M
suckless.org/community.md
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/suckless.org/community.md b/suckless.org/community.md
@@ -11,8 +11,8 @@ Mailing lists
 
 ### Best practice
 
-When beginning a new discussion on the mailinglists, except for the wiki@
-mailinglist, prepend your subject with the project name you are referring to.
+When beginning a new discussion on the mailing lists, except for the wiki@
+mailing list, prepend your subject with the project name you are referring to.
 This makes it easier for project maintainers to answer your questions.
 
 
@@ -58,13 +58,13 @@ When sending a patch use the following commands:
 	git send-email --subject-prefix="$(basename $(pwd))][PATCH" \
 		--to hackers@suckless.org -1
 
-This will send the last commit of the repository to the mailinglist adding a
+This will send the last commit of the repository to the mailing list adding a
 prefix to the subject which includes the appropriate project name. This allows
 easier referencing and filtering of the e-mails for the maintainers subscribed
 to hackers@.
 
 Be sure to have setup your sender address in git and be subscribed to the
-mailinglist so you can see eventual comments on your patches.
+mailing list so you can see eventual comments on your patches.
 
 * `hackers+subscribe@MAILHOST` - subscribe to the mailing list (read/write)
 * `hackers+subscribe-digest@MAILHOST` - subscribe to the digest version of the mailing list (read/write)