diff options
author | Rocco Rutte <pdmef@gmx.net> | 2009-08-17 17:07:26 +0200 |
---|---|---|
committer | Rocco Rutte <pdmef@gmx.net> | 2009-08-17 17:07:26 +0200 |
commit | 79aca41922028f2b53af4a0f65da3070d1282a33 (patch) | |
tree | 05abd466fd0f108aaad4757aa860439ba0d23a3c /doc | |
parent | aef3948e8c5a3ca1331b00c854995f69e6b6f845 (diff) |
Doc: fix more typos
Diffstat (limited to 'doc')
-rw-r--r-- | doc/manual.xml.head | 12 | ||||
-rw-r--r-- | doc/muttrc.man.head | 4 |
2 files changed, 8 insertions, 8 deletions
diff --git a/doc/manual.xml.head b/doc/manual.xml.head index c50b2ee5..3d7721ff 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -357,7 +357,7 @@ its flags (new email, important email, email that has been forwarded or 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> @@ -722,8 +722,8 @@ linkend="to-chars">$to_chars</link> variable. </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> @@ -4647,7 +4647,7 @@ messages), all of these tools need to agree on a character set and 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> @@ -5616,7 +5616,7 @@ can select one or more addresses to be added to the prompt. <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 @@ -7991,7 +7991,7 @@ As Mutt be can be set up to be the mail client to handle 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 diff --git a/doc/muttrc.man.head b/doc/muttrc.man.head index 2e1d264d..38053973 100644 --- a/doc/muttrc.man.head +++ b/doc/muttrc.man.head @@ -401,7 +401,7 @@ when \(lq\fB*\fP\(rq is used as an argument. \fIhook-type\fP 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 @@ -606,7 +606,7 @@ lying in the 21st century (i.e., \(lq38\(rq means 2038 and not 1938, 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 |