[Savannah-cvs] [457] fix markup

[ineiev]

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

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

Modified: trunk/sviki/FightingSpam.mdwn
===================================================================
--- trunk/sviki/FightingSpam.mdwn       2021-12-24 09:34:38 UTC (rev 456)
+++ trunk/sviki/FightingSpam.mdwn       2021-12-24 09:38:34 UTC (rev 457)
@@ -1,6 +1,8 @@
+# Fighting Spam in Trackers
+
 Savane provides several ways to protect trackers from spam.
 
-= Preventing Spam =
+## Preventing Spam
 
 Note: as of 2021, Savannah gets little spam in its trackers; the spammers
 seem to concentrate on adding unused accounts that are [[automatically
@@ -18,10 +20,10 @@
 
 * 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,
+- 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
+- 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).
 
@@ -34,7 +36,7 @@
 an item is closed, the item get additionnally locked. Obviously, this is
 useless on trackers where only project members can post.
 
-= Automatically Checking Potential Spam =
+## Automatically Checking Potential Spam
 
 Savane allows to *automatically check posted content with SpamAssassin*. (NB:
 not activated at Savannah).
@@ -44,10 +46,11 @@
 posted until it is checked in the following minutes.  If it is found
 to be spam, no notification will ever be sent, it will stay flagged as spam.
 
-= Removing Spam, Spam Scores =
+## Removing Spam, Spam Scores
 
-=== Spam Scores ===
+### Spam Scores
 
+
 Any logged-in user is able, when he sees content (comment or item) that he
 believes to be spam, to *flag it as spam*. This will increment the spam score
 of the item.
@@ -76,7 +79,7 @@
 means they can reset the spam score of some content if they think there is a
 mistake.
 
-=== Removing Spam ===
+### Removing Spam
 
 When a post is considered to be spam (spam score > 4), it is not removed from
 the database.  We do not want to loose data in case of false positives.