[deployment-guide/comm-rel: 344/727] Minor rephrasing.

[Jaromir Hradilek]

commit b03b5a8ab0de2c4f759a957d216246c648ce1962
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Wed Aug 11 17:45:26 2010 +0200

    Minor rephrasing.

 en-US/The_BIND_DNS_Server.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index b555201..c658d34 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -281,7 +281,7 @@
       </tgroup>
     </table>
     <para>
-      The <filename>/etc/named.conf</filename> file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <literal>{</literal> and <literal>}</literal>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <systemitem class="service">named</systemitem> service will not start. A typical configuration is organized as follows:
+      The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <literal>{</literal> and <literal>}</literal>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <systemitem class="service">named</systemitem> service will not start. A typical <filename>/etc/named.conf</filename> file is organized as follows:
     </para>
     <screen><replaceable>&lt;statement-1&gt;</replaceable> ["<replaceable>&lt;statement-1-name&gt;</replaceable>"] [<replaceable>&lt;statement-1-class&gt;</replaceable>] {
   <replaceable>&lt;option-1&gt;</replaceable>;