Convert SGML IDs to lower case

IDs in SGML are case insensitive, and we have accumulated a mix of upper
and lower case IDs, including different variants of the same ID.  In
XML, these will be case sensitive, so we need to fix up those
differences.  Going to all lower case seems most straightforward, and
the current build process already makes all anchors and lower case
anyway during the SGML->XML conversion, so this doesn't create any
difference in the output right now.  A future XML-only build process
would, however, maintain any mixed case ID spellings in the output, so
that is another reason to clean this up beforehand.

Author: Alexander Lakhin <[email protected]>

1 files changed, 2 insertions, 2 deletions

diff --git a/doc/src/sgml/btree-gist.sgml b/doc/src/sgml/btree-gist.sgml
index dcb939f1fbf..774442feeee 100644
--- a/doc/src/sgml/btree-gist.sgml
+++ b/doc/src/sgml/btree-gist.sgml
@@ -36,7 +36,7 @@
   In addition to the typical B-tree search operators, <filename>btree_gist</filename>
   also provides index support for <literal>&lt;&gt;</literal> (<quote>not
   equals</quote>). This may be useful in combination with an
-  <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion constraint</link>,
+  <link linkend="sql-createtable-exclude">exclusion constraint</link>,
   as described below.
  </para>
 
@@ -70,7 +70,7 @@ SELECT *, a &lt;-&gt; 42 AS dist FROM test ORDER BY a &lt;-&gt; 42 LIMIT 10;
 </programlisting>
 
   <para>
-   Use an <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion
+   Use an <link linkend="sql-createtable-exclude">exclusion
    constraint</link> to enforce the rule that a cage at a zoo
    can contain only one kind of animal:
   </para>