replied to, tagged email, ...), the date when email was sent, its
sender, the email size, and the subject. Additionally, the index also
shows thread hierarchies: when you reply to an email, and the other
-person replies back, you can see the other's person email in a
+person replies back, you can see the other person's email in a
"sub-tree" below. This is especially useful for personal email between
a group of people or when you've subscribed to mailing lists.
</para>
</thead>
<tbody>
<row><entry>+</entry><entry>message is to you and you only</entry></row>
-<row><entry>T</entry><entry>message is to you, but also to or cc'ed to others</entry></row>
-<row><entry>C</entry><entry>message is cc'ed to you</entry></row>
+<row><entry>T</entry><entry>message is to you, but also to or CC'ed to others</entry></row>
+<row><entry>C</entry><entry>message is CC'ed to you</entry></row>
<row><entry>F</entry><entry>message is from you</entry></row>
<row><entry>L</entry><entry>message is sent to a subscribed mailing list</entry></row>
</tbody>
encoding. There exists no way to reliably deduce the character set a
plain text file has. Interoperability is gained by the use of
well-defined environment variables. The full set can be printed by
-issueing <literal>locale</literal> on the command line.
+issuing <literal>locale</literal> on the command line.
</para>
<para>
<para>
Mutt supports reading and writing of four different local mailbox
-formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected,
+formats: mbox, MMDF, MH and Maildir. The mailbox type is auto detected,
so there is no need to use a flag for different mailbox types. When
creating new mailboxes, Mutt uses the default specified with the <link
linkend="mbox-type">$mbox_type</link> variable. A short description of
considerations, too. Arbitrary header fields can be embedded in these
links which could override existing header fields or attach arbitrary
files using <link linkend="attach-header">the Attach:
-psuedoheader</link>. This may be problematic if the <link
+pseudoheader</link>. This may be problematic if the <link
linkend="edit-headers">$edit-headers</link> variable is
<emphasis>unset</emphasis>, i.e. the user doesn't want to see header
fields while editing the message and doesn't pay enough attention to the
can be any of the \fB-hook\fP commands documented above.
.SH PATTERNS
.PP
-In various places with mutt, including some of the abovementioned
+In various places with mutt, including some of the above mentioned
\fBhook\fP commands, you can specify patterns to match messages.
.SS Constructing Patterns
.PP
and \(lq00\(rq is interpreted as 2000), and values
greater than or equal to 70 as lying in the 20th century.
.PP
-Note that this behaviour \fIis\fP Y2K compliant, but that mutt
+Note that this behavior \fIis\fP Y2K compliant, but that mutt
\fIdoes\fP have a Y2.07K problem.
.PP
If a date range consists of a single date, the operator in question
** When mutt is compiled with qdbm or tokyocabinet as header cache backend,
** this option determines whether the database will be compressed.
** Compression results in database files roughly being one fifth
- ** of the usual diskspace, but the uncompression can result in a
+ ** of the usual diskspace, but the decompression can result in a
** slower opening of cached folder(s) which in general is still
** much faster than opening non header cached folders.
*/