* Updates to V/W/X* config directives

refs/Variable

@@ -38,7 +38,9 @@ syntax:
 	unless found
 	</para></listitem>
 	<listitem><para>
-	Using the &tag-var; tag
+	Using the &tag-var; tag (Note: the &tag-var; tag is parsed together with 
+	all other tags, unlike the previous methods which are parsed separately,
+	before &glos-ITL; tag processing takes place)
 	</para></listitem>
 </itemizedlist>
 __END__

refs/VariableDatabase

@@ -35,9 +35,8 @@ is the same as:
 Database variables variables.txt TAB
 VariableDatabase variables
 </programlisting>
-So as you see, if you want to use a non-default &glos-database;, you must
-explicitly
-define it using the &conf-Database; directive and do so before the 
+But if you want to use a non-default &glos-database;, you must
+explicitly define it using the &conf-Database; directive and do so before the 
 &conf-VariableDatabase; line.
 __END__
 

refs/WritePermission

@@ -1,5 +1,5 @@
 __NAME__ purpose
-affect file mode (write permissions, specifically) on Interchange-generated files
+affect file mode (write permissions) on Interchange-generated files
 __END__
 
 

refs/XHTML

@@ -31,12 +31,12 @@ Making HTML output XHTML-compliant is extremely easy (basically, you only
 need to lowercase argument names, quote argument options, and include 
 <varname>$Vend::Xtrailer</varname> before the ending
 "<literal>&gt;</literal>" for standalone tags. That said, XHTML-compliance
-patches are gladly accepted to speed up the transition process.
+patches are gladly accepted to speed up the effort.
 __END__
 
 __NAME__ example: Enabling XHTML
 <programlisting>
-XHTML 1
+XHTML Yes
 </programlisting>
 __END__