[deployment-guide/comm-rel: 397/727] Indexed the Example Usage section.

[Jaromir Hradilek]

commit 39037dc443f7a29d6ff678751abcb13694c77934
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 17:34:08 2010 +0200

    Indexed the Example Usage section.

 en-US/The_BIND_DNS_Server.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 2135076..c1b42af 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1450,8 +1450,8 @@ IN  NS  dns2.example.com.</screen>
         <title>A Simple Zone File</title>
         <indexterm>
           <primary>BIND</primary>
-          <secondary>configuration of</secondary>
-          <tertiary>zone file examples</tertiary>
+          <secondary>zones</secondary>
+          <tertiary>example usage</tertiary>
         </indexterm>
         <para>
           <xref linkend="example-bind-zone-examples-basic" /> demonstrates the use of standard directives and <command>SOA</command> values.
@@ -1519,8 +1519,8 @@ www       CNAME  services.example.com.
         <title>A Reverse Name Resolution Zone File</title>
         <indexterm>
           <primary>BIND</primary>
-          <secondary>configuration of</secondary>
-          <tertiary>reverse name resolution</tertiary>
+          <secondary>zones</secondary>
+          <tertiary>example usage</tertiary>
         </indexterm>
         <para>
           A reverse name resolution zone file is used to translate an IP address in a particular namespace into an fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <command>PTR</command> resource records are used to link the IP addresses to a fully qualified domain name as shown in <xref linkend="example-bind-zone-examples-reverse" />.