From 136cdf787c8f8f415262c44c944add9f0b885a41 Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Wed, 18 Jun 2008 18:43:27 +0000
Subject: [PATCH] Add some indexterms to docs/scripting.xml and
 docs/refguide.xml.

---
 docs/refguide.xml  | 4 +++-
 docs/scripting.xml | 4 ++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/docs/refguide.xml b/docs/refguide.xml
index f6fb29b57..4de42c3b4 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -1975,6 +1975,7 @@ way.</para>
 
 <listitem>
 <para>Runs a script scan (like <option>-sC</option>) with the scripts you have chosen rather than the defaults.  Arguments can be script categories, single scripts or directories with scripts which are to be run against the target hosts instead of the default set. Nmap will try to interpret the arguments at first as categories and afterwards as files or directories.  Absolute paths are used as is, relative paths are searched in the following places until found:
+<indexterm><primary>NMAPDIR environment variable</primary></indexterm>
 <filename>--datadir/</filename>; 
 <filename>$(NMAPDIR)/</filename>; 
 <filename>~user/nmap/</filename> (not searched on Windows); 
@@ -3454,7 +3455,8 @@ overwhelming requests.  Specify <option>--open</option> to only see
           searches these files in the directory specified with the
           <option>--datadir</option> option (if any). Any files not
           found there, are searched for in the directory specified by
-          the NMAPDIR environmental variable. Next comes <filename>~/.nmap</filename> for
+          the NMAPDIR environmental variable<indexterm><primary>NMAPDIR environment variable</primary></indexterm>.
+          Next comes <filename>~/.nmap</filename> for
           real and effective UIDs (POSIX systems only) or location of
           the Nmap executable (Win32 only), and then a compiled-in
           location such as <filename>/usr/local/share/nmap</filename> or <filename>/usr/share/nmap</filename>
diff --git a/docs/scripting.xml b/docs/scripting.xml
index 63469445d..4a6b1d915 100644
--- a/docs/scripting.xml
+++ b/docs/scripting.xml
@@ -2,6 +2,7 @@
     <title>Introduction</title>
 
     <indexterm><primary>Nmap Scripting Engine</primary></indexterm>
+    <indexterm><primary>scripting</primary><see>Nmap Scripting Engine</see></indexterm>
     <para>The Nmap Scripting Engine (NSE) is one of Nmap's most
     powerful and flexible features.  It allows users to write (and
     share) simple scripts to automate a wide variety of networking
@@ -354,6 +355,9 @@ are to be run against the target hosts instead of the default set. Nmap
 will try to interpret the arguments at first as categories and afterwards
 as files or directories.  Absolute paths are used as is, relative paths are
 searched in the following places until found:
+<indexterm><primary>data files</primary><secondary>directory search order</secondary></indexterm>
+<indexterm><primary>scripts</primary><secondary>directory locations</secondary></indexterm>
+<indexterm><primary>scripts</primary><secondary>directory locations</secondary></indexterm>
 <filename>--datadir/</filename>; 
 <filename>$(NMAPDIR)/</filename>; 
 <filename>~user/nmap/</filename> (not searched on Windows);