<row><entry><Tab></entry><entry><literal><complete></literal></entry><entry>complete filename or alias</entry></row>
<row><entry>ˆT</entry><entry><literal><complete-query></literal></entry><entry>complete address with query</entry></row>
<row><entry>ˆK</entry><entry><literal><kill-eol></literal></entry><entry>delete to the end of the line</entry></row>
-<row><entry>Esc d</entry><entry><literal><kill-eow></literal></entry><entry>delete to the end ot the word</entry></row>
+<row><entry>Esc d</entry><entry><literal><kill-eow></literal></entry><entry>delete to the end of the word</entry></row>
<row><entry>ˆW</entry><entry><literal><kill-word></literal></entry><entry>kill the word in front of the cursor</entry></row>
<row><entry>ˆU</entry><entry><literal><kill-line></literal></entry><entry>delete entire line</entry></row>
<row><entry>ˆV</entry><entry><literal><quote-char></literal></entry><entry>quote the next typed key</entry></row>
<title>Message status flags</title>
<tgroup cols="2">
<thead>
-<row><entry>Flag</entry><entry>Desciption</entry></row>
+<row><entry>Flag</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>D</entry><entry>message is deleted (is marked for deletion)</entry></row>
<title>Message recipient flags</title>
<tgroup cols="2">
<thead>
-<row><entry>Flag</entry><entry>Desciption</entry></row>
+<row><entry>Flag</entry><entry>Description</entry></row>
</thead>
<tbody>
<row><entry>+</entry><entry>message is to you and you only</entry></row>
<emphasis role="bold">Note</emphasis> that mutt only support space-stuffing
for the first two types of lines but not for the third: It is impossible to
safely detect whether a leading <literal>></literal> character starts a
-quote or not. Futhermore, Mutt only applies space-stuffing
+quote or not. Furthermore, Mutt only applies space-stuffing
<emphasis>once</emphasis> after the initial edit is finished.
</para>
<itemizedlist>
<listitem><para>These variables should be set early in a configuration
-file with $charset preceeding $config_charset so Mutt
+file with $charset preceding $config_charset so Mutt
know what character set to convert to.</para></listitem>
<listitem><para>If $config_charset is set, it should be set
</para>
<para>
-These address groups can also be created implicitely by the
+These address groups can also be created implicitly by the
<link linkend="alias">alias</link>, <link linkend="lists">lists</link>,
<link linkend="lists">subscribe</link> and
<link linkend="alternates">alternates</link> commands by specifying the
</para>
<para>
-Some of the modifers are borrowed right out of C (though you might
-know them from Perl, Python, shell, or another langugage). These are
+Some of the modifiers are borrowed right out of C (though you might
+know them from Perl, Python, shell, or another language). These are
the [-]m.n modifiers, as in <literal>%-12.12s</literal>. As with
such programming languages, these modifiers allow you to specify the
-minumum and maximum size of the resulting string, as well as its
+minimum and maximum size of the resulting string, as well as its
justification. If the <quote>-</quote> sign follows the percent, the string will
be left-justified instead of right-justified. If there's a number
immediately following that, it's the minimum amount of space the
<para>
Without the quotes, the parenthesis wouldn't end.
-This would be seperated to two OR'd patterns: <emphasis>˜f me@(mutt\.org</emphasis>
+This would be separated to two OR'd patterns: <emphasis>˜f me@(mutt\.org</emphasis>
and <emphasis>cs\.hmc\.edu)</emphasis>. They are never what you want.
</para>
</para>
<para>
-Disposition is prefixed by either a + symbolor a - symbol. If it's
+Disposition is prefixed by either a + symbol or a - symbol. If it's
a +, you're saying that you want to allow this disposition and MIME
type to qualify. If it's a -, you're saying that this disposition
and MIME type is an exception to previous + rules. There are examples
to affect. A MIME type is always of the format "major/minor", where
"major" describes the broad category of document you're looking at, and
"minor" describes the specific type within that category. The major
-part of mim-type must be literal text (or the special token "*"), but
+part of mime-type must be literal text (or the special token "*"), but
the minor part may be a regular expression. (Therefore, "*/.*" matches
any MIME type.)
</para>
username for each folder: <literal>imap://username@imapserver[:port]/INBOX</literal>
or <literal>imap://username2@imapserver[:port]/path/to/folder</literal>.
Replacing <literal>imap://</literal> by <literal>imaps://</literal>
-would make mutt attempt to conect using SSL or TLS on a different port
+would make mutt attempt to connect using SSL or TLS on a different port
to encrypt the communication.
</para>
<para>
Even though a regular expression search is fast, it's several times
-slower than a pure string search which is noticable especially on large
+slower than a pure string search which is noticeable especially on large
folders. As a consequence, a string search should be used instead of a
regular expression search if the user already knows enough about the
search pattern.
however the special character \fB*\fP can be used to empty a group of all of
its contents.
.IP
-These address groups can also be created implicitely by the \fBalias\fP, \fBlists\fP,
+These address groups can also be created implicitly by the \fBalias\fP, \fBlists\fP,
\fBsubscribe\fP and \fBalternates\fP commands by specifying the optional \fI-group\fP
option.
.IP
.fi
.IP
If your terminal supports color, these commands can be used to
-assign \fIforeground\fP/\fIbackgound\fP combinations to certain
+assign \fIforeground\fP/\fIbackground\fP combinations to certain
objects. Valid objects are:
.BR attachment ", " body ", " bold ", " header ", "
.BR hdrdefault ", " index ", " indicator ", " markers ", "
.fi
.IP
These commands are used to set and manipulate configuration
-varibles.
+variables.
.IP
Mutt knows four basic types of variables: boolean, number, string
and quadoption. Boolean variables can be \fBset\fP (true),
duplicated messages (see $duplicate_threads)
.TP
~$
-unreferenced message (requries threaded view)
+unreferenced message (requires threaded view)
.TP
~(PATTERN)
messages in threads containing messages matching a certain pattern, e.g. all threads containing messages from you: ~(~P)
projects / mutt / commitdiff