Update

git-svn-id: file:///svnroot/mailfromd/trunk@1507 7a8a7f39-df28-0410-adc6-e0d955640f24

1 files changed, 49 insertions, 49 deletions

diff --git a/doc/mailfromd.texi b/doc/mailfromd.texi
index 8d72ec45..1043082f 100644
--- a/doc/mailfromd.texi
+++ b/doc/mailfromd.texi
@@ -983,13 +983,13 @@ the corresponding section below.
   Upgrading to this version does not require any special efforts.  You
 can use your configuration files and filter scripts without any changes.
 Notice only the following major differences between 4.1 and 4.0:
 
 @itemize @bullet
 @item Input files are preprocessed before compilation.
-@xref{Preprocessor}, for the description.
+@xref{Preprocessor}, for more information.
 
 @item There is a way to discern between a not-supplied optional
 parameter, and a supplied one, having null value (@pxref{defined}).
 
 @item The version 4.1 implements @code{sprintf} function
 (@pxref{String formatting}) and @code{printf} macro
@@ -1050,18 +1050,18 @@ warning: `#pragma option ehlo' is deprecated,
 steps:
   
 @enumerate 1
 @item
   Change @code{#pragma option mailfrom @var{value}} to
 @code{set mailfrom_address @var{value}}.  Refer to
-@ref{mailfrom_address}, for the detailed discussion of this variable.
+@ref{mailfrom_address}, for a detailed discussion of this variable.
 
 @item
   Change @code{#pragma option ehlo @var{value}} to
 @code{set ehlo_domain @var{value}}.  Refer to
-@ref{ehlo_domain}, for the detailed discussion of this variable.
+@ref{ehlo_domain}, for a detailed discussion of this variable.
 
 @item
   Include @file{status.mfh}.  Add the following line to the top of
 your startup file:
 
 @smallexample
@@ -1078,26 +1078,26 @@ use the following @command{sed} expression: @samp{s/&\([a-z]\)/\1/g}.
 to the top of your script:
 
 @smallexample
 #require dns
 @end smallexample
 
-@xref{Modules}, for the detailed description of the module system.
+@xref{Modules}, for a detailed description of the module system.
 
 @item
   Replace all occurrences of @code{next} with @code{pass}. 
 
 @item
   If your code uses function @code{match_cidr}, add the following line
 to the top of your script:
 
 @smallexample
 #require match_cidr
 @end smallexample
 
-@xref{Modules}, for the description of @acronym{MFL} module system.
+@xref{Modules}, for a description of @acronym{MFL} module system.
 
 @end enumerate
 
 @node 30x-31x
 @section Upgrading from 3.0.x to 3.1
 @cindex upgrading from 3.0.x to 3.1
@@ -1603,13 +1603,13 @@ hostname($client_addr)
 hostname $client_addr
 @end smallexample
 
 @noindent
 However, such syntax creates several ambiguities, so use it sparingly
 if at all.  We recommend to always use parentheses when calling a
-function; @xref{Cautions}, for the detailed analysis of of this syntax.
+function; @xref{Cautions}, for a detailed analysis of of this syntax.
 
   When a function does not deliver a result, it should only be called
 as a statement.
 
   Functions may be recursive, even mutually recursive.
 
@@ -1792,13 +1792,13 @@ the remote host.
 @item I/O timeout
   Maximum amount of time for finishing an input/output
 operation with the remote @acronym{SMTP} server.
 @end table
 
   These three timeouts can be set using the following @dfn{pragmatic
-comments}@footnote{@xref{Pragmatic comments}, for the detailed
+comments}@footnote{@xref{Pragmatic comments}, for a detailed
 description of pragmatic comments.} in the script file:
 
 @smallexample
 @group
 #pragma option connect-timeout @var{interval}
 #pragma option initial-response-timeout @var{interval}
@@ -1980,13 +1980,13 @@ where @var{expr} is any valid @acronym{MFL} expression.
 declarations as well as outside of them.
 
   There are two kinds of @command{Mailfromd} variables: @dfn{global
 variables},  that are visible to all handlers and functions, and
 @dfn{automatic variables}, that are available only within the handler
 or function where they are declared.  For our purpose we need a global
-variable (@xref{Variables, Variable classes}, for the detailed description
+variable (@xref{Variables, Variable classes}, for detailed descriptions
 of both kinds of variables). 
 
   The following example illustrates the approach that allows to use
 the @code{HELO} domain name in any handler:
 
 @smallexample
@@ -2283,13 +2283,13 @@ to the reader.
 @anchor{whitelisting}
 @cindex whitelisting
   One special case is @dfn{whitelisting}, which is often used
 together with greylisting.  To implement it, @command{mailfromd}
 provides the function @code{dbmap}, which takes two mandatory arguments:
 @code{dbmap(@var{file}, @var{key})} (it also allows an optional third
-argument, see @ref{dbmap}, for the description of it).  The first argument is
+argument, see @ref{dbmap}, for more information on it).  The first argument is
 the name of the @acronym{DBM} file where to search for the key, the second one
 is the key to be searched.  Assuming you keep your whitelist database
 in file @file{/var/run/whitelist.db}, a more practical example will be:
 
 @smallexample
 @group
@@ -2870,13 +2870,13 @@ administrator is to make sure it is available by configuring
 @code{Sendmail} to export the macro @samp{i} to @command{mailfromd}.
 The rule of thumb is: make @samp{i} available to the very first
 handler @command{mailfromd} executes.  It is not necessary to export
 it to the rest of the handlers, since @command{mailfromd} will cache
 it.  For example, if your filter script contains @samp{envfrom} and
 @samp{envrcpt} handlers, export @samp{i} for @samp{envfrom}.
-@xref{Sendmail Configuration}, for the instructions on how to ensure
+@xref{Sendmail Configuration}, for instructions on how to ensure
 it. 
 
 @xopindex{debug, introduced}
 @cindex debugging level
 @cindex verbosity level
   To push the log verbosity further, use @code{#pragma option debug}
@@ -3039,13 +3039,13 @@ regular expression.  For example:
 @end table
 
 @anchor{uncaught exceptions}
 @subheading Uncaught exceptions
   Another kind of runtime errors are @dfn{uncaught exceptions},
 i.e. exceptional conditions for which no handler was installed
-(@xref{Exceptions}, for the information on exceptions and on how to
+(@xref{Exceptions}, for information on exceptions and on how to
 handle them).  These errors mean that the programmer (i.e. you), made
 no provision for some specific conditions.  For example, consider the
 following code:
 
 @smallexample
 @group
@@ -3604,13 +3604,13 @@ The following options control @acronym{I/O} operations over @acronym{TCP}.