[deployment-guide/comm-rel: 205/727] modified Email chapter

[Jaromir Hradilek]

commit c12f555dd703e0766ec267fbb3871b4e253dc65d
Author: Martin Prpic <mprpic at redhat.com>
Date:   Fri Jul 30 11:36:32 2010 +0200

    modified Email chapter

 en-US/Email.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Email.xml b/en-US/Email.xml
index 1f04388..a5c9d39 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -179,7 +179,7 @@
       <para>While the delivery of messages between machines may seem rather straightforward, the entire process of deciding if a particular MTA can or should accept a message for delivery is quite complicated. In addition, due to problems from spam, use of a particular MTA is usually restricted by the MTA's configuration or the access configuration for the network on which the MTA resides.</para>
       <para>Many modern email client programs can act as an MTA when sending email. However, this action should not be confused with the role of a true MTA. The sole reason email client programs are capable of sending email like an MTA is because the host running the application does not have its own MTA. This is particularly true for email client programs on non-UNIX-based operating systems. However, these client programs only send outbound messages to an MTA they are authorized to use and do not directly deliver the message to the intended recipient's email server.</para>
       <para>Since &MAJOROS; installs two MTAs—Sendmail and Postfix—email client programs are often not required to act as an MTA. &MAJOROS; also includes a special purpose MTA called Fetchmail.</para>
-      <para>For more information on Sendmail, Postfix, and Fetchmail, refer to <xref
+      <para>For more information on Postfix, Sendmail, and Fetchmail, refer to <xref
           linkend="s1-email-mta"/>.</para>
     </section>
     <section