svn commit: r421293 - /spamassassin/branches/3.1/sa-learn.raw

[jm...@apache.org]

Author: jm
Date: Wed Jul 12 08:39:50 2006
New Revision: 421293

URL: http://svn.apache.org/viewvc?rev=421293&view=rev
Log:
bug 4896: misspellings fixed in POD docs

Modified:
    spamassassin/branches/3.1/sa-learn.raw

Modified: spamassassin/branches/3.1/sa-learn.raw
URL: http://svn.apache.org/viewvc/spamassassin/branches/3.1/sa-learn.raw?rev=421293&r1=421292&r2=421293&view=diff
==============================================================================
--- spamassassin/branches/3.1/sa-learn.raw (original)
+++ spamassassin/branches/3.1/sa-learn.raw Wed Jul 12 08:39:50 2006
@@ -557,13 +557,13 @@
   --regexp <re>                    For dump only, specifies which tokens to
                                    dump based on a regular expression.
  -f file, --folders=file           Read list of files/directories from file
- --dir                             Ignored; historical compatability
- --file                            Ignored; historical compatability
+ --dir                             Ignored; historical compatibility
+ --file                            Ignored; historical compatibility
  --mbox                            Input sources are in mbox format
  --mbx                             Input sources are in mbx format
  --showdots                        Show progress using dots
  --progress                        Show progress using progress bar
- --no-sync                         Skip syncronizing the database and journal
+ --no-sync                         Skip synchronizing the database and journal
                                    after learning
  -L, --local                       Operate locally, no network accesses
  --import                          Migrate data from older version/non DB_File
@@ -665,7 +665,7 @@
 or not.  Note: This doesn't mean any tokens will actually expire.
 Please see the EXPIRATION section below.
 
-Note: C<--force-expire> also causes the journal data to be syncronized
+Note: C<--force-expire> also causes the journal data to be synchronized
 into the Bayes databases.
 
 =item B<--forget>
@@ -754,7 +754,7 @@
 
 =item B<--no-sync>
 
-Skip the slow syncronization step which normally takes place after
+Skip the slow synchronization step which normally takes place after
 changing database entries.  If you plan to learn from many folders in
 a batch, or to learn many individual messages one-by-one, it is faster
 to use this switch and run C<sa-learn --sync> once all the folders have
@@ -849,7 +849,7 @@
 readable, even if statistics make me break out in hives.
 
 The short semi-inaccurate version: Given training, a spam heuristics engine
-can take the most "spammy" and "hammy" words and apply probablistic
+can take the most "spammy" and "hammy" words and apply probabilistic
 analysis. Furthermore, once given a basis for the analysis, the engine can
 continue to learn iteratively by applying both the non-Bayesian and Bayesian
 rulesets together to create evolving "intelligence".
@@ -885,7 +885,7 @@
 it is fairly easy to understand why.
 
 With Bayesian analysis, it's all probabilities - "because the past says
-it is likely as this falls into a probablistic distribution common to past
+it is likely as this falls into a probabilistic distribution common to past
 spam in your systems". Tell that to your users!  Tell that to the client
 when he asks "what can I do to change this". (By the way, the answer in
 this case is "use whitelisting".)
@@ -1070,12 +1070,12 @@
 it uses in its calculations.  To avoid the contention of having each
 SpamAssassin process attempting to gain write access to the Bayes DB,
 the token timestamps are written to a 'journal' file which will later
-(either automatically or via C<sa-learn --sync>) be used to syncronize
+(either automatically or via C<sa-learn --sync>) be used to synchronize
 the Bayes DB.
 
 Also, through the use of C<bayes_learn_to_journal>, or when using the
 C<--no-sync> option with sa-learn, the actual learning data will take
-be placed into the journal for later syncronization.  This is typically
+be placed into the journal for later synchronization.  This is typically
 useful for high-traffic sites to avoid the same contention as stated
 above.
 
@@ -1213,7 +1213,7 @@
 =over 4
 
 =item C<bayes_auto_expire> is used to specify whether or not SpamAssassin
-ought to opportunistically attempt to expire the Bayes databaase.
+ought to opportunistically attempt to expire the Bayes database.
 The default is 1 (yes).
 
 =item C<bayes_expiry_max_db_size> specifies both the auto-expire token