[deployment-guide/comm-rel: 390/727] Indexed the Comment Tags section.

[Jaromir Hradilek]

commit 3f1d6d8d08e0d27f3ed3d35def6deb3ea4d508d6
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 16:23:47 2010 +0200

    Indexed the Comment Tags section.

 en-US/The_BIND_DNS_Server.xml |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 4e4e043..4b74b35 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -911,7 +911,7 @@ options {
       <indexterm>
         <primary>BIND</primary>
         <secondary>configuration</secondary>
-        <tertiary>comment</tertiary>
+        <tertiary>comment tags</tertiary>
       </indexterm>
       <para>
         Additionally to statements, the <filename>/etc/named.conf</filename> file can also contain comments. Comments are ignored by the <systemitem class="service">named</systemitem> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
@@ -1427,6 +1427,11 @@ IN  NS  dns2.example.com.</screen>
     </section>
     <section id="s2-bind-zone-comm">
       <title>Comment Tags</title>
+      <indexterm>
+        <primary>BIND</primary>
+        <secondary>zones</secondary>
+        <tertiary>comment tags</tertiary>
+      </indexterm>
       <para>
         Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <systemitem class="service">named</systemitem> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, <literal>;</literal>) to the end of the line is considered a comment. For example:
       </para>