Fix typos.

* doc/texinfo/mailcap.texi, doc/texinfo/mailutils.texi
doc/texinfo/mom.texi, doc/texinfo/mu-mh.texi,
doc/texinfo/mu_message.texi, doc/texinfo/programs.texi,
doc/texinfo/sieve.texi: Fix typos.

+2008-11-09  Wojciech Polak  <polak@gnu.org>
+
+	Fix typos.
+	
+	* doc/texinfo/mailcap.texi, doc/texinfo/mailutils.texi
+	doc/texinfo/mom.texi, doc/texinfo/mu-mh.texi,
+	doc/texinfo/mu_message.texi, doc/texinfo/programs.texi,
+	doc/texinfo/sieve.texi: Fix typos.
+
 2008-11-09  Sergey Poznyakoff  <gray@gnu.org.ua>
 2008-11-09  Sergey Poznyakoff  <gray@gnu.org.ua>
 
 
 	Rewrite default mailbox format support to make sure it does not
 	Rewrite default mailbox format support to make sure it does not

 @c This is part of the GNU Mailutils manual.
 @c This is part of the GNU Mailutils manual.
 @c Copyright (C) 1999,2000,2001,2002,2003,2004,2006,
 @c Copyright (C) 1999,2000,2001,2002,2003,2004,2006,
-@c 2007 Free Software Foundation, Inc.
+@c 2007,2008 Free Software Foundation, Inc.
 @c See file mailutils.texi for copying conditions.
 @c See file mailutils.texi for copying conditions.
 @comment *******************************************************************
 @comment *******************************************************************
 
 
@@ -23,7 +23,7 @@ application/pgp; gpg < %s | metamail; needsterminal; \
 @end group
 @end group
 @end smallexample
 @end smallexample
 
 
-A mailcap file consits of a set of mailcap entries per line, lines
+A mailcap file consists of a set of mailcap entries per line, lines
 beginning with @samp{#} are considered comments and ignored. Long
 beginning with @samp{#} are considered comments and ignored. Long
 mailcap entry may be continued on multiple lines if each line ends
 mailcap entry may be continued on multiple lines if each line ends
 with a backslash character @samp{\}, the multiline will be considered
 with a backslash character @samp{\}, the multiline will be considered
@@ -39,8 +39,8 @@ Newline = <newline as defined by OS convention>
 @end smallexample
 @end smallexample
 
 
 Each mailcap entry consists of a number of fields, separated
 Each mailcap entry consists of a number of fields, separated
-by semi-colons. The first two filds are required and must occur
-in the secified order, the remaining fields are optional.
+by semi-colons. The first two fields are required and must occur
+in the specified order, the remaining fields are optional.
 
 
 @smallexample
 @smallexample
 Mailcap-Entry = @var{typefield} ";" @var{view-command} ";" *[ ";" @var{field} ]
 Mailcap-Entry = @var{typefield} ";" @var{view-command} ";" *[ ";" @var{field} ]

@@ -66,7 +66,7 @@ Software Foundation raise funds for GNU development.''
 @titlepage
 @titlepage
 @title GNU Mailutils
 @title GNU Mailutils
 @subtitle version @value{VERSION}, @value{UPDATED}
 @subtitle version @value{VERSION}, @value{UPDATED}
-@author Alain Magloire, Sergey Pozbyakoff et al.
+@author Alain Magloire, Sergey Poznyakoff et al.
 @page
 @page
 @vskip 0pt plus 1filll
 @vskip 0pt plus 1filll
 @insertcopying
 @insertcopying

 @c This is part of the GNU Mailutils manual.
 @c This is part of the GNU Mailutils manual.
 @c Copyright (C) 1999,2000,2001,2002,2003,2004,
 @c Copyright (C) 1999,2000,2001,2002,2003,2004,
-@c 2007 Free Software Foundation, Inc.
+@c 2007,2008 Free Software Foundation, Inc.
 @c See file mailutils.texi for copying conditions.
 @c See file mailutils.texi for copying conditions.
 @comment *******************************************************************
 @comment *******************************************************************
 
 
@@ -21,7 +21,7 @@ extends it:
 struct _mu_object;
 struct _mu_object;
 typedef struct _mu_object* mu_object_t;
 typedef struct _mu_object* mu_object_t;
 
 
-/* Defintion of the interface for mu_object */
+/* Definition of the interface for mu_object */
 struct _mu_object_vtable
 struct _mu_object_vtable
 @{
 @{
   int  (*create)   (mu_object_t *object);
   int  (*create)   (mu_object_t *object);
@@ -58,8 +58,8 @@ Instead of using macros or the vtable directly.
 @section Implementing an Interface
 @section Implementing an Interface
 
 
 @comment ***********************************************************
 @comment ***********************************************************
-@comment This is not a very good/usefull example, we should do one using
-@comment header or message, something usefull that would clarify the concepts
+@comment This is not a very good/useful example, we should do one using
+@comment header or message, something usefully that would clarify the concepts
 @comment better and at the same could be reuse in code by clients.
 @comment better and at the same could be reuse in code by clients.
 @comment
 @comment
 @comment For example mime_t "extends" message_t, this is a good example
 @comment For example mime_t "extends" message_t, this is a good example

 @c This is part of the GNU Mailutils manual.
 @c This is part of the GNU Mailutils manual.
-@c Copyright (C) 2006, 2007 Free Software Foundation, Inc.
+@c Copyright (C) 2006, 2007, 2008 Free Software Foundation, Inc.
 @c See file mailutils.texi for copying conditions.
 @c See file mailutils.texi for copying conditions.
 @comment *******************************************************************
 @comment *******************************************************************
 
 
@@ -246,7 +246,7 @@ it must be enclosed in double-quotes. Dangling equal sign is an error,
 to set a string variable to the empty value assign it an empty string, e.g.:
 to set a string variable to the empty value assign it an empty string, e.g.:
 @code{overflowtext=""} (see the supplied @file{mhl.format} file).
 @code{overflowtext=""} (see the supplied @file{mhl.format} file).
 
 
-Ineractive prompting is not yet implemented.
+Interactive prompting is not yet implemented.
 
 
 @item mhn
 @item mhn
 
 

@@ -19,7 +19,7 @@ Destroys the message @var{mesg}.
 @deffn {Scheme procedure} mu-message-set-header mesg header value replace
 @deffn {Scheme procedure} mu-message-set-header mesg header value replace
 Sets new @var{value} to the header @var{header} of the message @var{mesg}.
 Sets new @var{value} to the header @var{header} of the message @var{mesg}.
 If @var{header} is already present in the message its value
 If @var{header} is already present in the message its value
-is replaced with the suplied one iff the optional @var{replace} is
+is replaced with the supplied one if the optional @var{replace} is
 #t. Otherwise, a new header is created and appended.
 #t. Otherwise, a new header is created and appended.
 @end deffn
 @end deffn
 
 
@@ -89,7 +89,7 @@ Return the value of the user attribute @var{flag} from the message @var{mesg}.
 
 
 @c snarfed from "mu_message.c":783
 @c snarfed from "mu_message.c":783
 @deffn {Scheme procedure} mu-message-set-user-flag mesg flag value
 @deffn {Scheme procedure} mu-message-set-user-flag mesg flag value
-Set the given user attribute @var{flag} in the message @var{mesg}. If optional argumen
+Set the given user attribute @var{flag} in the message @var{mesg}. If optional argument
 @var{value} is @samp{#f}, the attribute is unset.
 @var{value} is @samp{#f}, the attribute is unset.
 @end deffn
 @end deffn
 
 
@@ -129,7 +129,7 @@ Returns part #@var{part} from a multipart @acronym{MIME} message @var{mesg}.
 @c snarfed from "mu_message.c":957
 @c snarfed from "mu_message.c":957
 @deffn {Scheme procedure} mu-message-send mesg mailer from to
 @deffn {Scheme procedure} mu-message-send mesg mailer from to
 Sends the message @var{mesg}. Optional @var{mailer} overrides default mailer settings
 Sends the message @var{mesg}. Optional @var{mailer} overrides default mailer settings
-in mu-mailer. Optional @var{from} and @var{to} give sender and recever addresses.
+in mu-mailer. Optional @var{from} and @var{to} give sender and receiver addresses.
 
 
 @end deffn
 @end deffn
 
 

@@ -6,9 +6,9 @@
 
 
 GNU Mailutils provides a broad set of utilities for handling
 GNU Mailutils provides a broad set of utilities for handling
 electronic mail. These utilities address the needs of both system
 electronic mail. These utilities address the needs of both system
-adminsitrators and users.
+administrators and users.
 
 
-All utilities are built around a single core subsistem and share many
+All utilities are built around a single core subsystem and share many
 common aspects. All of them are able to work with almost any existing
 common aspects. All of them are able to work with almost any existing
 mailbox formats. They use a common configuration file syntax, and
 mailbox formats. They use a common configuration file syntax, and
 their configuration files are located in a single subdirectory.
 their configuration files are located in a single subdirectory.
@@ -235,7 +235,7 @@ Do not load user configuration file.
 @UNREVISED
 @UNREVISED
 
 
   Configuration files are the principal means of configuring any GNU
   Configuration files are the principal means of configuring any GNU
-Mailutil component. When started, each utility tries to load its
+Mailutils component. When started, each utility tries to load its
 configuration from the following locations, in that order:
 configuration from the following locations, in that order:
 
 
 @enumerate 1
 @enumerate 1
@@ -694,7 +694,7 @@ The most important debugging modules are:
 Debug access control lists. @FIXME-xref{Debugging ACLs}.
 Debug access control lists. @FIXME-xref{Debugging ACLs}.
 
 
 @item config
 @item config
-Debug configuration parser and/or lexical analizer. The following
+Debug configuration parser and/or lexical analyzer. The following
 levels are supported:
 levels are supported:
 
 
 @table @asis
 @table @asis
@@ -872,7 +872,7 @@ indexed directory structure.
 
 
 @cindex directory indexing
 @cindex directory indexing
 An @dfn{indexed directory structure} is a special way of storing
 An @dfn{indexed directory structure} is a special way of storing
-mailboxes, which allowes for faster access in case of very large
+mailboxes, which allows for faster access in case of very large
 number of users. 
 number of users. 
 
 
 By default, all user mailboxes are stored in a single directory and
 By default, all user mailboxes are stored in a single directory and
@@ -911,7 +911,7 @@ this case the file name of @samp{smith}'s mailbox is
 The @dfn{reverse} indexed structure uses the same principles, but the
 The @dfn{reverse} indexed structure uses the same principles, but the
 indexing letters are taken from the @emph{end} of the user name,
 indexing letters are taken from the @emph{end} of the user name,
 instead of from the beginning. For example, in the 2nd level reverse
 instead of from the beginning. For example, in the 2nd level reverse
-indexed structure, the @samp{smith}'s mailbix is located in
+indexed structure, the @samp{smith}'s mailbox is located in
 @file{@var{path}/h/t/smith}.
 @file{@var{path}/h/t/smith}.
 
 
 @cindex hashed indexing
 @cindex hashed indexing
@@ -920,7 +920,7 @@ Finally, the @dfn{hashed} structure consists of 256 subdirectories
 under @var{path}, named by 2-letter hex codes from @samp{00} to
 under @var{path}, named by 2-letter hex codes from @samp{00} to
 @samp{FF}. Mailboxes are stored in these subdirectories. The name
 @samp{FF}. Mailboxes are stored in these subdirectories. The name
 of the subdirectory is computed by hashing first @var{level} letters
 of the subdirectory is computed by hashing first @var{level} letters
-of the user name. The hashing alorithm is:
+of the user name. The hashing algorithm is:
 
 
 @enumerate 1
 @enumerate 1
 @item Take next letter from the user name
 @item Take next letter from the user name
@@ -1066,7 +1066,7 @@ Store the PID of the locking process in a lock file.
 @end deffn
 @end deffn
 
 
 @deffn {Configuration} retry-count @var{number}
 @deffn {Configuration} retry-count @var{number}
-Number of locking attemtps. The @samp{P} flag must be set for this to
+Number of locking attempts. The @samp{P} flag must be set for this to
 take effect.
 take effect.
 @end deffn
 @end deffn
 
 
@@ -1115,7 +1115,7 @@ can be regarded as a function that returns a tree-state value:
 @samp{True}, @samp{False} and @samp{Don't know}. When a
 @samp{True}, @samp{False} and @samp{Don't know}. When a
 remote party connects to the server, each of controls is tried in
 remote party connects to the server, each of controls is tried in
 turn. If a control returns @samp{False}, access is denied. If it
 turn. If a control returns @samp{False}, access is denied. If it
-retruns @samp{True}, access is allowed. If it returns @samp{Don't
+returns @samp{True}, access is allowed. If it returns @samp{Don't
 know}, then the next control is tried. It is unclear whether to allow
 know}, then the next control is tried. It is unclear whether to allow
 access if the last control in list returned @samp{Don't know}. GNU
 access if the last control in list returned @samp{Don't know}. GNU
 Mailutils @value{VERSION} issues a warning message and allows access.
 Mailutils @value{VERSION} issues a warning message and allows access.
@@ -1189,7 +1189,7 @@ families: @samp{AF_INET} and @samp{AF_UNIX}.
 
 
 @item address
 @item address
 Remote IP address (for @samp{AF_INET}) or socket name (for
 Remote IP address (for @samp{AF_INET}) or socket name (for
-@samp{AF_UNIX}). Notice that most Unices return empty string instead
+@samp{AF_UNIX}). Notice that most Unixes return empty string instead
 of the @samp{AF_UNIX} socket name, so do not rely on it.
 of the @samp{AF_UNIX} socket name, so do not rely on it.
 
 
 @item port
 @item port
@@ -1213,7 +1213,7 @@ above in your configuration files.
 
 
 @deffn {Configuration} exec [from] @var{cidr} @var{program}
 @deffn {Configuration} exec [from] @var{cidr} @var{program}
 If a connection from the @var{cidr} block is requested, execute
 If a connection from the @var{cidr} block is requested, execute
-the given @var{program}. Do not wait for it to teminate, and ignore
+the given @var{program}. Do not wait for it to terminate, and ignore
 its exit code.
 its exit code.
 @end deffn
 @end deffn
 
 
@@ -1450,7 +1450,7 @@ servers.
 
 
 @deffn {Configuration} transcript @var{bool};
 @deffn {Configuration} transcript @var{bool};
 Enable transcript of the client-server interaction. This may generate
 Enable transcript of the client-server interaction. This may generate
-exessive amounts of logging, which in turn may slow down the operation
+excessive amounts of logging, which in turn may slow down the operation
 considerably.
 considerably.
 
 
 Session transcripts are useful in fine-tuning your configurations and
 Session transcripts are useful in fine-tuning your configurations and
@@ -1755,20 +1755,20 @@ $INCLUDE dict/mailutils.dict
 Requests to use for authentication and authorization are
 Requests to use for authentication and authorization are
 configured using three statements: @code{auth}, @code{getpwnam} and
 configured using three statements: @code{auth}, @code{getpwnam} and
 @code{getpwuid}. Each statement takes a single argument: a string,
 @code{getpwuid}. Each statement takes a single argument: a string,
-containing a comma-separated list of assignements. An assignement
+containing a comma-separated list of assignments. An assignment
 specifies a particular @dfn{attribute-value pair} (@pxref{Overview,
 specifies a particular @dfn{attribute-value pair} (@pxref{Overview,
 RADIUS Attributes,, radius, GNU Radius Reference Manual}) to send to
 RADIUS Attributes,, radius, GNU Radius Reference Manual}) to send to
-the server. The left-hand side of the assignement is a symbolic attribute
+the server. The left-hand side of the assignment is a symbolic attribute
 name, as defined in one of Radius dictionaries (@pxref{dictionary
 name, as defined in one of Radius dictionaries (@pxref{dictionary
 file, Dictionary of Attributes,, radius, GNU Radius Reference
 file, Dictionary of Attributes,, radius, GNU Radius Reference
 Manual}). The value is specified by the right-hand side of
 Manual}). The value is specified by the right-hand side of
-assignement. For example:
+assignment. For example:
 
 
 @smallexample
 @smallexample
 "Service-Type = Authenticate-Only, NAS-Identifier = \"mail\""
 "Service-Type = Authenticate-Only, NAS-Identifier = \"mail\""
 @end smallexample
 @end smallexample
 
 
-An assignement may contain references to the following macro-variables
+An assignment may contain references to the following macro-variables
 (@FIXME-pxref{macro-variables}):
 (@FIXME-pxref{macro-variables}):
 
 
 @table @asis
 @table @asis
@@ -2081,7 +2081,7 @@ Prints only a count of messages in the mailbox and exit.
 
 
 @item -d
 @item -d
 @itemx --debug
 @itemx --debug
-Prints additional debugging outut.
+Prints additional debugging output.
 
 
 @item -s @var{string}
 @item -s @var{string}
 @itemx --sender=@var{string}
 @itemx --sender=@var{string}
@@ -3591,7 +3591,7 @@ set metamail="metamail -m mail -p"
 @*Default: Empty
 @*Default: Empty
 @vrindex mimenoask, mail variable
 @vrindex mimenoask, mail variable
 
 
-By default @command{mail} asks for comnfirmation before running
+By default @command{mail} asks for confirmation before running
 interpreter to view a part of the multi-part message. If this variable
 interpreter to view a part of the multi-part message. If this variable
 is set, its value is treated as a comma-separated list of MIME types
 is set, its value is treated as a comma-separated list of MIME types
 for which no confirmation is needed. Elements of this list may include
 for which no confirmation is needed. Elements of this list may include
@@ -4736,12 +4736,12 @@ Sometimes it is necessary to limit the maximum size of a user's
 mailbox. Such maximum size is called @dfn{mailbox quota} for this
 mailbox. Such maximum size is called @dfn{mailbox quota} for this
 user.
 user.
 
 
-When delivering a message, @command{mail.local} first cheks if
+When delivering a message, @command{mail.local} first checks if
 the mailbox quota is specified for the recipient. If so,
 the mailbox quota is specified for the recipient. If so,
 @command{mail.local} computes the difference between the quota
 @command{mail.local} computes the difference between the quota
 value and the actual size of the recipient's mailbox. This difference
 value and the actual size of the recipient's mailbox. This difference
 represents the maximum size of the message the receipient's mailbox is
 represents the maximum size of the message the receipient's mailbox is
-able to accomodate. Let's call it @var{msize}. Depending on its value,
+able to accommodate. Let's call it @var{msize}. Depending on its value,
 @command{mail.local} takes decision on whether to deliver the message.
 @command{mail.local} takes decision on whether to deliver the message.
 There are three possible cases:
 There are three possible cases:
 
 
@@ -4788,7 +4788,7 @@ The  quota database should have the following structure:
 @table @asis
 @table @asis
 @item Key
 @item Key
 Key represents the user name. Special key @samp{DEFAULT} means default
 Key represents the user name. Special key @samp{DEFAULT} means default
-quota value, i.e. the one to be used if the user is not explicitely
+quota value, i.e. the one to be used if the user is not explicitly
 listed in the database.
 listed in the database.
 
 
 @item Value
 @item Value
@@ -5035,8 +5035,8 @@ a @asis{tty} device.
 
 
 @item -n
 @item -n
 @itemx --dry-run
 @itemx --dry-run
-Do not do anything, just print what whould be done. Implies
-@option{--debug=1}, unless the debugging level is set up explicitely.
+Do not do anything, just print what would be done. Implies
+@option{--debug=1}, unless the debugging level is set up explicitly.
 
 
 @item -t @var{file}
 @item -t @var{file}
 @itemx --mimetypes @var{file}
 @itemx --mimetypes @var{file}

@@ -92,7 +92,7 @@ markers are taken verbatim. For example:
 
 
 @smallexample
 @smallexample
 text:
 text:
-** This is an authomatic response from my message **
+** This is an automatic response from my message **
 ** filtering program.                            **
 ** filtering program.                            **
 
 
 I can not attend your message right now. However it
 I can not attend your message right now. However it
@@ -1558,7 +1558,7 @@ may disappear from the subsequent releases.
 
 
 @item @code{fileinto} action
 @item @code{fileinto} action
 
 
-The @code{fileinto} action allows to specify permissons on the mailbox,
+The @code{fileinto} action allows to specify permissions on the mailbox,
 in case it is created (@pxref{fileinto}).
 in case it is created (@pxref{fileinto}).
 
 
 @item Match type optional argument.
 @item Match type optional argument.