[deployment-guide/comm-rel: 364/727] Updated the `server' statement description.

[Jaromir Hradilek]

commit 2853f1833eee797caeb81aebee4eae0a848963bd
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Aug 13 16:15:36 2010 +0200

    Updated the `server' statement description.

 en-US/The_BIND_DNS_Server.xml |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 3dcfa68..4632e1c 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -869,10 +869,10 @@ options {
           <term><command>server</command></term>
           <listitem>
             <para>
-              Specifies options that affect how <command>named</command> should respond to remote nameservers, especially <!-- RHEL5:  in regards  -->with regard to notifications and zone transfers.
+              The <command>server</command> statement allows you to specify options that affect how the <systemitem class="service">named</systemitem> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
             </para>
             <para>
-              The <command>transfer-format</command> option controls whether one resource record is sent with each message (<command>one-answer</command>) or multiple resource records are sent with each message (<command>many-answers</command>). While <command>many-answers</command> is more efficient, only newer BIND nameservers understand it.
+              The <option>transfer-format</option> option controls the number of resource records that are sent with each message. It can be either <literal>one-answer</literal> (only one resource record), or <literal>many-answers</literal> (multiple resource records). Note that while the <literal>many-answers</literal> option is more efficient, it is not supported by older versions of BIND.
             </para>
           </listitem>
         </varlistentry>