[Savannah-cvs] [458] further refinements

[ineiev]

Revision: 458
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=458
Author:   ineiev
Date:     2021-12-24 04:42:34 -0500 (Fri, 24 Dec 2021)
Log Message:
-----------
further refinements

Modified Paths:
--------------
    trunk/sviki/FightingSpam.mdwn

Modified: trunk/sviki/FightingSpam.mdwn
===================================================================
--- trunk/sviki/FightingSpam.mdwn       2021-12-24 09:38:34 UTC (rev 457)
+++ trunk/sviki/FightingSpam.mdwn       2021-12-24 09:42:34 UTC (rev 458)
@@ -10,22 +10,23 @@
 section may exclude potential contributions, so you shouldn't take them
 unless the real volume of spam you get is high.
 
-Savane can run *DNS blacklists* checks on all forms submitted by non-project
-members (NB: not activated at Savannah).
+Savane can run checks against DNS blacklists on all forms submitted
+by non-project members (NB: not activated at Savannah).
 
-Apart from that, there are a few options that can allow a project admin to
-prevent many spams.
+Apart from that, there are a few options that can allow a project admin
+to prevent spam.
 
-Spam are usually caused by anonymous robots.
+Spam is usually generated by anonymous robots.
 
 * A starting point to avoid spam is first to set
 tracker *Posting Restrictions* to a tough policy:
-- On every tracker that you feel dedicated to manage the project workflow,
-without end user's interaction, like the task tracker, set _project membership_
-as the minimal level of authentication.
-- On every tracker that need input from non-members, like the support
-tracker and the bug tracker, set _logged-in user_ as the minimal authentication
-level (it means that external contributors will have to create an account).
+  - On every tracker that you feel dedicated to manage the project workflow,
+  without end user's interaction, like the task tracker, set
+  _project membership_ as the minimal level of authentication.
+  - On every tracker that need input from non-members, like the support
+  tracker and the bug tracker, set _logged-in user_ as the minimal
+  authentication level (it means that external contributors will have to create
+  an account).
 
 * Another idea is too use the special *Lock Discussion* field. This field,
 that can be modified only by tracker managers, is complementary to the
@@ -38,8 +39,8 @@
 
 ## Automatically Checking Potential Spam
 
-Savane allows to *automatically check posted content with SpamAssassin*. (NB:
-not activated at Savannah).
+Savane allows to automatically check posts with SpamAssassin
+(not activated at Savannah).
 
 Any post that Savane feels need crosschecking by SpamAssassin (depends on
 site configuration) will be delayed, temporarily flagged as spam, when
@@ -62,7 +63,7 @@
 which the suspected spam have been posted, the spam score of the content will
 grow of 1.
 
-Any *item with a spam score greater than 4 is considered to be spam*.
+Any item with a spam score greater than 4 is considered to be spam.
 
 All users also have their own spam scores.  When users get one of their posts
 flagged as spam (spam score > 4), their score grows by 1.  User's spam score
@@ -93,5 +94,5 @@
 If spam is posted as an item, it is automatically set to _Locked_
 so further posts are blocked.
 
-If the site runs checks with SpamAssassin, *flagged spam will be used to
-improve Bayesian filtering*.
+If the site runs checks with SpamAssassin, flagged spam will be used to
+improve Bayesian filtering.