[deployment-guide/comm-rel: 383/727] Updated the PTR resource record description.

[Jaromir Hradilek]

commit 896e8946737cf36f0038195d2f99c909f7b5bdf3
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 15:31:23 2010 +0200

    Updated the PTR resource record description.

 en-US/The_BIND_DNS_Server.xml |   21 +++++++++------------
 1 files changed, 9 insertions(+), 12 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index b72c79b..e797b2c 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1192,27 +1192,24 @@ www      IN  CNAME  server1</screen>
           <term><command>NS</command></term>
           <listitem>
             <para>
-              This refers to the NameServer record, which announces the authoritative nameservers for a particular zone.
+              The <firstterm>NameServer</firstterm> record announces authoritative nameservers for a particular zone. It takes the following form:
             </para>
+            <screen>IN NS <replaceable>nameserver-name</replaceable></screen>
             <para>
-              <!-- RHEL5:  This is an example  -->The following illustrates the layout of an <command>NS</command> record:
+              The <replaceable>nameserver-name</replaceable> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
             </para>
-            <screen> IN NS <replaceable>&lt;nameserver-name&gt;</replaceable></screen>
-            <para>
-              <!-- RHEL5:  The  -->Here, <replaceable>&lt;nameserver-name&gt;</replaceable> should be an FQDN.
-            </para>
-            <para>
-              Next, two nameservers are listed as authoritative for the domain. It is not important whether these nameservers are slaves or if one is a master; they are both still considered authoritative.
-            </para>
-            <screen>IN NS dns1.example.com.
-IN NS dns2.example.com.</screen>
+            <example id="example-bind-zone-rr-ns">
+              <title>Using the <command>NS</command> resource record</title>
+              <screen>IN  NS  dns1.example.com.
+IN  NS  dns2.example.com.</screen>
+            </example>
           </listitem>
         </varlistentry>
         <varlistentry>
           <term><command>PTR</command></term>
           <listitem>
             <para>
-              This refers to the PoinTeR record, which is designed to point to another part of the namespace.
+              The <firstterm>PoinTeR</firstterm> record points to another part of the namespace.
             </para>
             <para>
               <command>PTR</command> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <xref linkend="s2-bind-configuration-zone-reverse" /> for more examples of <command>PTR</command> records in use.