summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-04-01 12:59:21 (GMT)
committerJeroen van Meeuwen (Kolab Systems) <vanmeeuwen@kolabsys.com>2012-04-01 12:59:21 (GMT)
commitadd52305fc8cb050fd740d92a618fa5396eff383 (patch)
treee0e0e10a81ff152ac51060f6fdd31bebc2f037b0
parenta15f0bac02709e5ef8c8ca64f80120c1db9fecd6 (diff)
downloadkolab-docs-add52305fc8cb050fd740d92a618fa5396eff383.tar.gz
Tweak language in combating spam
-rw-r--r--Administrator_Guide/en-US/Combating_Spam.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/Administrator_Guide/en-US/Combating_Spam.xml b/Administrator_Guide/en-US/Combating_Spam.xml
index f5b6244..81e3225 100644
--- a/Administrator_Guide/en-US/Combating_Spam.xml
+++ b/Administrator_Guide/en-US/Combating_Spam.xml
@@ -15,7 +15,7 @@
A common deployment is to define deployment-wide user preferences and to use a single, deployment-wide set of rules for <application>SpamAssassin</application> to operate with -including Bayes database(s).
</para>
<para>
- The problems start when individual users mark legitimate email as spam, most notably the company newsletter or correspondation they have opted in for some time ago, but wish to no longer receive. Users tend to ignore the long-term effects of marking these message as spam, if at all they are aware of any, and just want such messages out of they way.
+ The problems start when individual users mark legitimate email as spam, most notably the company newsletter or correspondation they have opted in some time ago, but wish to no longer receive. Users tend to ignore the long-term effects of marking these message as spam, if at all they are aware of any, and just want such messages out of their way.
</para>
<para>
Common examples of the sort of messages that are often marked as spam while being legitimate traffic include: