</sect1>
<sect1 id="irc">
-<title>Mutt online resources</title>
+<title>Mutt Online Resources</title>
<variablelist>
</sect1>
<sect1 id="typo">
-<title>Typograhical conventions</title>
+<title>Typograhical Conventions</title>
<para>
This section lists typographical conventions followed throughout this
</para>
<sect1 id="core-concepts">
-<title>Core concepts</title>
+<title>Core Concepts</title>
<para>
Mutt is a text-based application which interacts with users through
</sect1>
<sect1 id="reading">
-<title>Reading Mail - The Index and Pager</title>
+<title>Reading Mail</title>
<para>
Similar to many other mail clients, there are two modes in which mail is
</sect2>
<sect2 id="edit-header">
-<title>Editing the message header</title>
+<title>Editing the Message Header</title>
<para>
When editing the header because of <link linkend="edit-headers">$edit_headers</link>
</para>
<sect3 id="fcc-header">
-<title>Fcc: pseudo header</title>
+<title>Fcc: Pseudo Header</title>
<para>
If you specify
</sect3>
<sect3 id="attach-header">
-<title>Attach: pseudo header</title>
+<title>Attach: Pseudo Header</title>
<para>
You can also attach files to your message by specifying
</sect3>
<sect3 id="pgp-header">
-<title>Pgp: pseudo header</title>
+<title>Pgp: Pseudo Header</title>
<para>
If you want to use PGP, you can specify
</sect3>
<sect3 id="in-reply-to-header">
-<title>In-Reply-To: header</title>
+<title>In-Reply-To: Header</title>
<para>
When replying to messages, the <emphasis>In-Reply-To:</emphasis> header contains the
</sect2>
<sect2 id="sending-crypto">
-<title>Sending cryptographically signed/encrypted messages</title>
+<title>Sending Cryptographically Signed/Encrypted Messages</title>
<para>
If you have told Mutt to PGP or S/MIME encrypt a message, it will guide you
</sect2>
<sect2 id="ff">
-<title>Sending format=flowed messages</title>
+<title>Sending Format=Flowed Messages</title>
<sect3 id="ff-concept">
<title>Concept</title>
</sect3>
<sect3 id="ff-support">
-<title>Mutt support</title>
+<title>Mutt Support</title>
<para>
Mutt only supports setting the required <literal>format=flowed</literal>
</sect3>
<sect3 id="ff-editor">
-<title>Editor considerations</title>
+<title>Editor Considerations</title>
<para>
As Mutt provides no additional features to compose <literal>f=f</literal>
<title>Configuration</title>
<sect1 id="configuration-files">
-<title>Location of initialization files</title>
+<title>Location of Initialization Files</title>
<para>
While the default configuration (or <quote>preferences</quote>) make Mutt
</sect1>
<sect1 id="addrgroup">
-<title>Address groups</title>
+<title>Address Groups</title>
<para>Usage:</para>
</sect1>
<sect1 id="alias">
-<title>Defining/Using aliases</title>
+<title>Defining/Using Aliases</title>
<para>Usage:</para>
</sect1>
<sect1 id="bind">
-<title>Changing the default key bindings</title>
+<title>Changing the Default Key Bindings</title>
<para>Usage:</para>
</sect1>
<sect1 id="charset-hook">
-
-<title>Defining aliases for character sets </title>
+<title>Defining Aliases for Character Sets</title>
<para>Usage:</para>
</sect1>
<sect1 id="folder-hook">
-<title>Setting variables based upon mailbox</title>
+<title>Setting Variables Based Upon Mailbox</title>
<para>Usage:</para>
</sect1>
<sect1 id="macro">
-<title>Keyboard macros</title>
+<title>Keyboard Macros</title>
<para>Usage:</para>
</sect1>
<sect1 id="color">
-<title>Using color and mono video attributes</title>
+<title>Using Color and Mono Video Attributes</title>
<para>Usage:</para>
</sect1>
<sect1 id="msg-hdr-display">
-<title>Message header display</title>
+<title>Message Header Display</title>
<sect2 id="ignore">
<title>Selecting Headers</title>
</sect1>
<sect1 id="alternates">
-<title>Alternative addresses</title>
+<title>Alternative Addresses</title>
<para>Usage:</para>
</sect1>
<sect1 id="lists">
-<title>Mailing lists</title>
+<title>Mailing Lists</title>
<anchor id="subscribe"/>
<para>Usage:</para>
</sect1>
<sect1 id="mbox-hook">
-<title>Using Multiple spool mailboxes</title>
+<title>Using Multiple Spool Mailboxes</title>
<para>Usage:</para>
</sect1>
<sect1 id="mailboxes">
-<title>Monitoring incoming mail</title>
+<title>Monitoring Incoming Mail</title>
<para>Usage:</para>
</sect1>
<sect1 id="my-hdr">
-<title>User defined headers</title>
+<title>User-Defined Headers</title>
<para>Usage:</para>
</sect1>
<sect1 id="save-hook">
-<title>Specify default save mailbox</title>
+<title>Specify Default Save Mailbox</title>
<para>Usage:</para>
</sect1>
<sect1 id="fcc-hook">
-<title>Specify default Fcc: mailbox when composing</title>
+<title>Specify Default Fcc: Mailbox When Composing</title>
<para>Usage:</para>
</sect1>
<sect1 id="fcc-save-hook">
-<title>Specify default save filename and default Fcc: mailbox at once</title>
+<title>Specify Default Save Filename and Default Fcc: Mailbox at Once</title>
<para>Usage:</para>
</sect1>
<sect1 id="send-hook">
-<title>Change settings based upon message recipients</title>
+<title>Change Settings Based Upon Message Recipients</title>
<anchor id="reply-hook"/>
<anchor id="send2-hook"/>
</sect1>
<sect1 id="message-hook">
-<title>Change settings before formatting a message</title>
+<title>Change Settings Before Formatting a Message</title>
<para>Usage:</para>
</sect1>
<sect1 id="crypt-hook">
-<title>Choosing the cryptographic key of the recipient</title>
+<title>Choosing the Cryptographic Key of the Recipient</title>
<para>Usage:</para>
</sect1>
<sect1 id="push">
-<title>Adding key sequences to the keyboard buffer</title>
+<title>Adding Key Sequences to the Keyboard Buffer</title>
<para>Usage:</para>
</sect1>
<sect1 id="exec">
-<title>Executing functions</title>
+<title>Executing Functions</title>
<para>Usage:</para>
</sect1>
<sect1 id="spam">
-<title>Spam detection</title>
+<title>Spam Detection</title>
<para>Usage:</para>
<title>Setting and Querying Variables</title>
<sect2 id="var-types">
-<title>Variable types</title>
+<title>Variable Types</title>
<para>
Mutt supports these types of configuration variables:
</sect2>
<sect2 id="set-myvar">
-<title>User-defined variables</title>
+<title>User-Defined Variables</title>
<sect3 id="set-myvar-intro">
<title>Introduction</title>
</sect1>
<sect1 id="source">
-<title>Reading initialization commands from another file</title>
+<title>Reading Initialization Commands From Another File</title>
<para>Usage:</para>
</sect1>
<sect1 id="unhook">
-<title>Removing hooks</title>
+<title>Removing Hooks</title>
<para>Usage:</para>
</sect1>
<sect1 id="editing-threads">
-<title>Editing threads</title>
+<title>Editing Threads</title>
<para>
Mutt has the ability to dynamically restructure threads that are broken
</para>
<sect2 id="link-threads">
-<title>Linking threads</title>
+<title>Linking Threads</title>
<para>
Some mailers tend to <quote>forget</quote> to correctly set the <quote>In-Reply-To:</quote> and
</sect2>
<sect2 id="break-threads">
-<title>Breaking threads</title>
+<title>Breaking Threads</title>
<para>
On mailing lists, some people are in the bad habit of starting a new
</para>
<sect2 id="mime-pager">
-<title>Viewing MIME messages in the pager</title>
+<title>Viewing MIME Messages in the Pager</title>
<para>
When you select a message from the index and view it in the pager, Mutt
</sect1>
<sect1 id="mime-types">
-<title>MIME Type configuration with <literal>mime.types</literal></title>
+<title>MIME Type Configuration with <literal>mime.types</literal></title>
<para>
When you add an attachment to your mail message, Mutt searches your
</sect1>
<sect1 id="mailcap">
-<title>MIME Viewer configuration with mailcap</title>
+<title>MIME Viewer Configuration with Mailcap</title>
<para>
Mutt supports RFC 1524 MIME Configuration, in particular the Unix
</para>
<sect2 id="mailcap-basics">
-<title>The Basics of the mailcap file</title>
+<title>The Basics of the Mailcap File</title>
<para>
A mailcap file consists of a series of lines which are comments, blank,
</sect2>
<sect2 id="secure-mailcap">
-<title>Secure use of mailcap</title>
+<title>Secure Use of Mailcap</title>
<para>
The interpretation of shell meta-characters embedded in MIME parameters
</sect2>
<sect2 id="advanced-mailcap">
-<title>Advanced mailcap Usage</title>
+<title>Advanced Mailcap Usage</title>
<sect3 id="optional-mailcap-fields">
<title>Optional Fields</title>
</sect2>
<sect2 id="mailcap-example">
-<title>Example mailcap files</title>
+<title>Example Mailcap Files</title>
<para>
This mailcap file is fairly simple and standard:
</chapter>
<chapter id="optionalfeatures">
-<title>Optional features</title>
+<title>Optional Features</title>
<sect1 id="optionalfeatures-notes">
-<title>General notes</title>
+<title>General Notes</title>
<sect2 id="compile-time-features">
-<title>Enabling/disabling features</title>
+<title>Enabling/Disabling Features</title>
<para>
Mutt supports several of optional features which can be enabled or
</sect2>
<sect2 id="url-syntax">
-<title>URL syntax</title>
+<title>URL Syntax</title>
<para>
Mutt optionally supports the IMAP, POP3 and SMTP protocols which require
</note>
<sect2 id="imap-browser">
-<title>The Folder Browser</title>
+<title>The IMAP Folder Browser</title>
<para>
As of version 1.2, Mutt supports browsing mailboxes on an IMAP
</sect1>
<sect1 id="account-hook">
-<title>Managing multiple accounts</title>
+<title>Managing Multiple Accounts</title>
<para>
If you happen to have accounts on multiple IMAP, POP and/or SMTP servers,
</sect1>
<sect1 id="caching">
-<title>Local caching</title>
+<title>Local Caching</title>
<para>
Mutt contains two types of local caching: <emphasis>(1)</emphasis>
</para>
<sect2 id="header-caching">
-<title>Header caching</title>
+<title>Header Caching</title>
<para>
Mutt provides optional support for caching message headers for the
</sect2>
<sect2 id="body-caching">
-<title>Body caching</title>
+<title>Body Caching</title>
<para>
Both cache methods can be combined using the same directory for storage
</sect1>
<sect1 id="exact-address">
-<title>Exact address generation</title>
+<title>Exact Address Generation</title>
<para>
Mutt supports the <quote>Name <user@host></quote> address syntax for reading and
<title>Information Leaks</title>
<sect2 id="security-leaks-mid">
-<title>Message-ID: headers</title>
+<title>Message-Id: headers</title>
<para>
Message-Id: headers contain a local part that is to be created in a
</sect2>
<sect2 id="security-leaks-mailto">
-<title><literal>mailto:</literal>-style links</title>
+<title><literal>mailto:</literal>-style Links</title>
<para>
As Mutt be can be set up to be the mail client to handle
</sect1>
<sect1 id="security-external">
-<title>External applications</title>
+<title>External Applications</title>
<para>
Mutt in many places has to rely on external applications or for
<chapter id="tuning">
-<title>Performance tuning</title>
+<title>Performance Tuning</title>
<sect1 id="tuning-mailboxes">
-<title>Reading and writing mailboxes</title>
+<title>Reading and Writing Mailboxes</title>
<para>
Mutt's performance when reading mailboxes can be improved in two ways:
</sect1>
<sect1 id="tuning-messages">
-<title>Reading messages from remote folders</title>
+<title>Reading Messages from Remote Folders</title>
<para>
Reading messages from remote folders such as IMAP an POP can be
</sect1>
<sect1 id="tuning-search">
-<title>Searching and limiting</title>
+<title>Searching and Limiting</title>
<para>
When searching mailboxes either via a search or a limit action, for
<title>Reference</title>
<sect1 id="commandline">
-<title>Command line options</title>
+<title>Command-Line Options</title>
<para>
Running <literal>mutt</literal> with no arguments will make Mutt attempt to read your spool
</sect1>
<sect1 id="variables">
-<title>Configuration variables</title>
+<title>Configuration Variables</title>