From: richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2>
Date: Sun, 11 May 2003 22:45:59 +0000 (+0000)
Subject: *** empty log message ***
X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=ba5ccdb568c57a8f67f9d436eb560a591486df56;p=roundup.git

*** empty log message ***


git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1715 57a73879-2fb5-44c3-a270-3262357dd7e2
---

diff --git a/doc/customizing.txt b/doc/customizing.txt
index 5711dff..d703663 100644
--- a/doc/customizing.txt
+++ b/doc/customizing.txt
@@ -2,7 +2,7 @@
 Customising Roundup
 ===================
 
-:Version: $Revision: 1.85 $
+:Version: $Revision: 1.86 $
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
    http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -88,19 +88,19 @@ The configuration variables available are:
 **MAILHOST** - ``'localhost'``
  The SMTP mail host that roundup will use to send e-mail.
 
-**MAILUSER - ``()``
+**MAILUSER** - ``()``
  If your SMTP mail host requires a username and password for access, then
  specify them here. eg. ``MAILUSER = ('username', 'password')``
 
-**MAILHOST_TLS - ``'no'``
+**MAILHOST_TLS** - ``'no'``
  If your SMTP mail host provides or requires TLS (Transport Layer
  Security) then set ``MAILHOST_TLS = 'yes'``
 
-**MAILHOST_TLS_KEYFILE - ``''``
+**MAILHOST_TLS_KEYFILE** - ``''``
  If you're using TLS, you may also set MAILHOST_TLS_KEYFILE to the name of
  a PEM formatted file that contains your private key.
 
-**MAILHOST_TLS_CERTFILE - ``''``
+**MAILHOST_TLS_CERTFILE** - ``''``
  If you're using TLS and have specified a MAILHOST_TLS_KEYFILE, you may
  also set MAILHOST_TLS_CERTFILE to the name of a PEM formatted certificate
  chain file.
diff --git a/doc/installation.txt b/doc/installation.txt
index 28f690b..f330aba 100644
--- a/doc/installation.txt
+++ b/doc/installation.txt
@@ -2,7 +2,7 @@
 Installing Roundup
 ==================
 
-:Version: $Revision: 1.50 $
+:Version: $Revision: 1.51 $
 
 .. contents::
 
@@ -241,7 +241,7 @@ There's several to choose from, each with benefits and limitations:
   dbm backends.
 **mysql**
   Backend for popular RDBMS MySQL. According to benchmarks, this backend works
-  much faster than any of *dbm ones, but slightly slower than metakit and
+  much faster than any of \*dbm ones, but slightly slower than metakit and
   sqlite. A good scalability is not a property of this backend for now,
   though. For more info on backend installation see doc/mysql.txt. 
 **metakit**