List:Commits« Previous MessageNext Message »
From:paul Date:January 3 2006 5:33am
Subject:svn commit - mysqldoc@docsrva: r646 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-03 06:33:23 +0100 (Tue, 03 Jan 2006)
New Revision: 646

Log:
 r5776@frost:  paul | 2006-01-02 23:14:49 -0600
 Fix <xref>s.


Modified:
   trunk/
   trunk/refman-4.1/apis.xml
   trunk/refman-4.1/charset.xml
   trunk/refman-4.1/client-side-scripts.xml
   trunk/refman-4.1/connector-odbc.xml
   trunk/refman-4.1/data-types.xml
   trunk/refman-4.1/database-administration.xml
   trunk/refman-4.1/extending-mysql.xml
   trunk/refman-4.1/functions.xml
   trunk/refman-4.1/innodb.xml
   trunk/refman-4.1/language-structure.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-4.1/optimization.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/replication.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-4.1/storage-engines.xml
   trunk/refman-4.1/tutorial.xml
   trunk/refman-5.0/apis.xml
   trunk/refman-5.0/client-side-scripts.xml
   trunk/refman-5.0/connector-odbc.xml
   trunk/refman-5.0/data-types.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/extending-mysql.xml
   trunk/refman-5.0/functions.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.0/language-structure.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/replication.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.0/storage-engines.xml
   trunk/refman-5.0/stored-procedures.xml
   trunk/refman-5.0/triggers.xml
   trunk/refman-5.0/tutorial.xml
   trunk/refman-5.1/apis.xml
   trunk/refman-5.1/client-side-scripts.xml
   trunk/refman-5.1/connector-odbc.xml
   trunk/refman-5.1/data-types.xml
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/extending-mysql.xml
   trunk/refman-5.1/functions.xml
   trunk/refman-5.1/innodb.xml
   trunk/refman-5.1/language-structure.xml
   trunk/refman-5.1/ndbcluster.xml
   trunk/refman-5.1/optimization.xml
   trunk/refman-5.1/partitioning.xml
   trunk/refman-5.1/problems.xml
   trunk/refman-5.1/replication.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-5.1/storage-engines.xml
   trunk/refman-5.1/stored-procedures.xml
   trunk/refman-5.1/triggers.xml
   trunk/refman-5.1/tutorial.xml
   trunk/refman-common/news-4.0.xml
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-5.1.xml
   trunk/refman-common/news-cluster.xml
   trunk/refman-common/what-is.en.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5774
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1848
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:5776
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1848

Modified: trunk/refman-4.1/apis.xml
===================================================================
--- trunk/refman-4.1/apis.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/apis.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -307,7 +307,7 @@
         program, use the <option>--defaults-file</option> option as one
         of the elements of the second argument of the
         <literal>mysql_server_init()</literal> function. See
-        <xref linkend="mysql-server-init"/> for more information on the
+        <xref linkend="mysql-server-init"/>, for more information on the
         <literal>mysql_server_init()</literal> function.
       </para>
 
@@ -4525,7 +4525,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -4555,7 +4555,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -7995,7 +7995,7 @@
       <para>
         <emphasis role="bold">Note</emphasis>: Some incompatible changes
         were made in MySQL 4.1.2. See
-        <xref linkend="c-api-prepared-statement-functions"/> for
+        <xref linkend="c-api-prepared-statement-functions"/>, for
         details.
       </para>
 
@@ -8530,7 +8530,7 @@
       <para>
         <emphasis role="bold">Note</emphasis>: Some incompatible changes
         were made in MySQL 4.1.2. See
-        <xref linkend="c-api-prepared-statement-functions"/> for
+        <xref linkend="c-api-prepared-statement-functions"/>, for
         details.
       </para>
 
@@ -9093,7 +9093,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-affected-rows"/> for additional
+          See <xref linkend="mysql-affected-rows"/>, for additional
           information on the return value.
         </para>
 
@@ -10743,7 +10743,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-insert-id"/> for more information.
+          See <xref linkend="mysql-insert-id"/>, for more information.
         </para>
 
         <para>
@@ -13044,7 +13044,7 @@
             downgrade to MySQL 4.0; switch to PHP 5 and the newer
             <literal>mysqli</literal> extension; or configure the MySQL
             server with <option>--old-passwords</option>. (See
-            <xref linkend="old-client"/> for more information.)
+            <xref linkend="old-client"/>, for more information.)
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/charset.xml
===================================================================
--- trunk/refman-4.1/charset.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/charset.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -2412,7 +2412,7 @@
 </programlisting>
 
     <para>
-      Use the table shown in <xref linkend="charset-map"/> to find old
+      Use the table shown in <xref linkend="charset-map"/>, to find old
       4.0 character set names and their 4.1 character set/collation pair
       equivalents.
     </para>

Modified: trunk/refman-4.1/client-side-scripts.xml
===================================================================
--- trunk/refman-4.1/client-side-scripts.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/client-side-scripts.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -29,7 +29,7 @@
     This chapter provides a brief overview of these programs and then a
     more detailed description of each one. The descriptions indicate how
     to invoke the programs and the options they understand. See
-    <xref linkend="using-mysql-programs"/> for general information on
+    <xref linkend="using-mysql-programs"/>, for general information on
     invoking programs and specifying program options.
   </para>
 
@@ -1430,7 +1430,7 @@
             <para>
               Execute the statement and quit. The default output format
               is like that produced with <option>--batch</option>. See
-              <xref linkend="command-line-options"/> for some examples.
+              <xref linkend="command-line-options"/>, for some examples.
             </para>
           </listitem>
 
@@ -1809,7 +1809,7 @@
               affect using key values. If you have set this option in an
               option file, you can override it by using
               <option>--safe-updates</option> on the command line. See
-              <xref linkend="mysql-tips"/> for more information about
+              <xref linkend="mysql-tips"/>, for more information about
               this option.
             </para>
           </listitem>

Modified: trunk/refman-4.1/connector-odbc.xml
===================================================================
--- trunk/refman-4.1/connector-odbc.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/connector-odbc.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1004,7 +1004,7 @@
 </programlisting>
 
       <para>
-        Then proceed on to <xref linkend="dsn-on-unix"/> to configure
+        Then proceed on to <xref linkend="dsn-on-unix"/>, to configure
         the DSN for MyODBC. For more information, refer to the
         <filename>INSTALL-BINARY</filename> file that comes with your
         distribution.
@@ -1950,7 +1950,7 @@
 
       <listitem>
         <para>
-          See <xref linkend="installing-source-tree"/> for instructions
+          See <xref linkend="installing-source-tree"/>, for instructions
           on how to download and install BitKeeper.
         </para>
       </listitem>
@@ -2376,7 +2376,7 @@
         The DSN configuration dialog also has an
         <literal>Options</literal> button. If you select it, the
         following options dialog appears displaying that control driver
-        behavior. Refer to <xref linkend="connection-parameters"/> for
+        behavior. Refer to <xref linkend="connection-parameters"/>, for
         information about the meaning of these options.
       </para>
 
@@ -5017,7 +5017,7 @@
 
       <para>
         A simple examples for the usage of ADO, DAO and RDO with VB can
-        be found her:
+        be found here:
       </para>
 
       <itemizedlist>
@@ -5402,13 +5402,13 @@
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-c-sharp-cp"/>
+            See <xref linkend="odbc-net-op-c-sharp-cp"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-vb-cp"/>
+            See <xref linkend="odbc-net-op-vb-cp"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/data-types.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1031,7 +1031,7 @@
             MySQL 4.1. For complete information on the differences with
             regard to this data type in MySQL 4.1 and later versions (as
             opposed to MySQL 4.0 and earlier versions), be sure to see
-            <xref linkend="timestamp-pre-4-1"/> and
+            <xref linkend="timestamp-pre-4-1"/>, and
             <xref linkend="timestamp-4-1"/>.
           </para>
 

Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/database-administration.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -302,7 +302,7 @@
             server named <command>mysqld-max</command>. The
             <literal>MySQL-Max</literal> RPM presupposes that you have
             installed the regular server RPM. See
-            <xref linkend="linux-rpm"/> for more information on the
+            <xref linkend="linux-rpm"/>, for more information on the
             Linux RPM packages.
           </para>
         </listitem>
@@ -1298,7 +1298,7 @@
             the <command>mysql.server</command> script will be installed
             in the <filename>/etc/init.d</filename> directory with the
             name <filename>mysql</filename>. You need not install it
-            manually. See <xref linkend="linux-rpm"/> for more
+            manually. See <xref linkend="linux-rpm"/>, for more
             information on the Linux RPM packages.
           </para>
 
@@ -2573,7 +2573,7 @@
               The binary log file. Log all queries that change data to
               this file. Used for backup and replication. See
               <xref linkend="binary-log"/>. It is recommended to specify
-              a filename (see <xref linkend="open-bugs"/> for the
+              a filename (see <xref linkend="open-bugs"/>, for the
               reason) otherwise MySQL uses
               <filename><replaceable>host_name</replaceable>-bin</filename>
               as the log file basename.
@@ -2870,7 +2870,7 @@
               is possible to point out the management server that
               distributes the cluster configuration by setting the
               connect string option. See
-              <xref linkend="mysql-cluster-connectstring"/> for syntax.
+              <xref linkend="mysql-cluster-connectstring"/>, for syntax.
             </para>
           </listitem>
 
@@ -4214,7 +4214,7 @@
         <para>
           You can view system variables and their values by using the
           <literal>SHOW VARIABLES</literal> statement. See
-          <xref linkend="system-variables"/> for more information.
+          <xref linkend="system-variables"/>, for more information.
         </para>
 
 <programlisting>
@@ -4936,7 +4936,7 @@
               <literal>MyISAM</literal> tables by starting the server
               with the <option>--myisam-recover</option> option (for
               example, <option>--myisam-recover=BACKUP,FORCE</option>).
-              See <xref linkend="server-options"/> and
+              See <xref linkend="server-options"/>, and
               <xref linkend="myisam-start"/>.
             </para>
 
@@ -6019,7 +6019,7 @@
               The number of simultaneous client connections allowed.
               Increasing this value increases the number of file
               descriptors that <command>mysqld</command> requires. See
-              <xref linkend="table-cache"/> for comments on file
+              <xref linkend="table-cache"/>, for comments on file
               descriptor limits. Also see
               <xref linkend="too-many-connections"/>.
             </para>
@@ -7178,7 +7178,7 @@
               implementation.) By examining the difference between the
               <literal>Connections</literal> and
               <literal>Threads_created</literal> status variables (see
-              <xref linkend="server-status-variables"/> for details) you
+              <xref linkend="server-status-variables"/>, for details) you
               can see how efficient the thread cache is. This variable
               was added in MySQL 3.23.16.
             </para>
@@ -9881,7 +9881,7 @@
         pre-4.1.1-style passwords, the encryption algorithm is less
         strong and with some effort a clever attacker who can sniff the
         traffic between the client and the server can crack the
-        password. (See <xref linkend="password-hashing"/> for a
+        password. (See <xref linkend="password-hashing"/>, for a
         discussion of the different password handling methods.) If the
         connection between the client and the server goes through an
         untrusted network, you should use an SSH tunnel to encrypt the
@@ -10539,7 +10539,7 @@
         If your privileges are changed (either by yourself or someone
         else) while you are connected, those changes do not necessarily
         take effect immediately for the next statement you issue. See
-        <xref linkend="privilege-changes"/> for details.
+        <xref linkend="privilege-changes"/>, for details.
       </para>
 
       <para>
@@ -12943,7 +12943,7 @@
 
           <para>
             For information on how to deal with this, see
-            <xref linkend="password-hashing"/> and
+            <xref linkend="password-hashing"/>, and
             <xref linkend="old-client"/>.
           </para>
         </listitem>
@@ -15337,7 +15337,7 @@
 </programlisting>
 
           <para>
-            <xref linkend="option-files"/> discusses option files in
+            <xref linkend="option-files"/>, discusses option files in
             more detail.
           </para>
         </listitem>
@@ -16220,7 +16220,7 @@
         backup. To get a consistent backup, do a <literal>LOCK
         TABLES</literal> on the relevant tables, followed by
         <literal>FLUSH TABLES</literal> for the tables. See
-        <xref linkend="lock-tables"/> and <xref linkend="flush"/>. You
+        <xref linkend="lock-tables"/>, and <xref linkend="flush"/>. You
         need only a read lock; this allows other clients to continue to
         query the tables while you are making a copy of the files in the
         database directory. The <literal>FLUSH TABLES</literal>
@@ -16235,14 +16235,14 @@
         the output file cannot previously exist. For <literal>BACKUP
         TABLE</literal>, the same is true as of MySQL 3.23.56 and
         4.0.12, because this would be a security risk. See
-        <xref linkend="select"/> and <xref linkend="backup-table"/>.
+        <xref linkend="select"/>, and <xref linkend="backup-table"/>.
       </para>
 
       <para>
         Another way to back up a database is to use the
         <command>mysqldump</command> program or the
         <command>mysqlhotcopy script</command>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <orderedlist>
@@ -16300,7 +16300,7 @@
       <para>
         For <literal>InnoDB</literal> tables, it is possible to perform
         an online backup that takes no locks on tables; see
-        <xref linkend="mysqldump"/>
+        <xref linkend="mysqldump"/>.
       </para>
 
       <para>
@@ -16318,7 +16318,7 @@
         should also rotate the binary log using <literal>FLUSH
         LOGS</literal>, <literal>mysqldump --flush-logs</literal>, or
         <literal>mysqlhotcopy --flushlogs</literal>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <para>
@@ -16373,7 +16373,7 @@
             logs, from certain positions (usually you want to re-run all
             binary logs from the date of the restored backup, excepting
             possibly some incorrect queries). See
-            <xref linkend="mysqlbinlog"/> for more information on the
+            <xref linkend="mysqlbinlog"/>, for more information on the
             <command>mysqlbinlog</command> utility and how to use it.
           </para>
 
@@ -17624,7 +17624,7 @@
             <literal>myisam_stats_method</literal> system variable. For
             more information, see the description of
             <literal>myisam_stats_method</literal> in
-            <xref linkend="server-system-variables"/> and
+            <xref linkend="server-system-variables"/>, and
             <xref linkend="myisam-index-statistics"/>.
             <literal>stats_method</literal> was added in MySQL
             4.1.15/5.0.14. For older versions, the statistics collection
@@ -18598,7 +18598,7 @@
             should) use the <literal>CHECK TABLE</literal> and
             <literal>REPAIR TABLE</literal> statements to check and
             repair <literal>MyISAM</literal> tables. See
-            <xref linkend="check-table"/> and
+            <xref linkend="check-table"/>, and
             <xref linkend="repair-table"/>.
           </para>
 
@@ -19017,7 +19017,7 @@
         repair <literal>MyISAM</literal> tables is with the
         <literal>CHECK TABLE</literal> and <literal>REPAIR
         TABLE</literal> statements. These are available starting with
-        MySQL 3.23.16. See <xref linkend="check-table"/> and
+        MySQL 3.23.16. See <xref linkend="check-table"/>, and
         <xref linkend="repair-table"/>.
       </para>
 
@@ -21158,7 +21158,7 @@
         <literal>-bin</literal>. If file name is given, but it does not
         contain a path, the file is written in the data directory. It is
         recommended to specify a filename, see
-        <xref linkend="open-bugs"/> for the reason.
+        <xref linkend="open-bugs"/>, for the reason.
       </para>
 
       <para>
@@ -21195,7 +21195,7 @@
         You can delete all binary log files with the <literal>RESET
         MASTER</literal> statement, or only some of them with
         <literal>PURGE MASTER LOGS</literal>. See
-        <xref linkend="reset"/> and
+        <xref linkend="reset"/>, and
         <xref linkend="replication-master-sql"/>.
       </para>
 
@@ -21461,7 +21461,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysqlbinlog"/> for more information on the
+        See <xref linkend="mysqlbinlog"/>, for more information on the
         <command>mysqlbinlog</command> utility and how to use it.
       </para>
 
@@ -22535,7 +22535,7 @@
       </para>
 
       <para>
-        <xref linkend="environment-variables"/> includes a list of other
+        <xref linkend="environment-variables"/>, includes a list of other
         environment variables you can use to affect
         <command>mysqld</command>.
       </para>
@@ -22800,7 +22800,7 @@
 
       <para>
         This section describes how the query cache works when it is
-        operational. <xref linkend="query-cache-configuration"/>
+        operational. <xref linkend="query-cache-configuration"/>,
         describes how to control whether or not it is operational.
       </para>
 

Modified: trunk/refman-4.1/extending-mysql.xml
===================================================================
--- trunk/refman-4.1/extending-mysql.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/extending-mysql.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -863,7 +863,7 @@
         constraints may change in future versions of the server, so it
         is possible that server upgrades will require revisions to UDFs
         that were originally written for older servers. For information
-        about these constraints, see <xref linkend="configure-options"/>
+        about these constraints, see <xref linkend="configure-options"/>,
         and <xref linkend="compilation-problems"/>.
       </para>
 
@@ -1150,7 +1150,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create a simple UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 
@@ -1313,7 +1313,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create an aggregate UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 

Modified: trunk/refman-4.1/functions.xml
===================================================================
--- trunk/refman-4.1/functions.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/functions.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -5880,7 +5880,7 @@
     <para>
       This section describes the functions that can be used to
       manipulate temporal values. See
-      <xref linkend="date-and-time-types"/> for a description of the
+      <xref linkend="date-and-time-types"/>, for a description of the
       range of values each date and time type has and the valid formats
       in which values may be specified.
     </para>
@@ -6096,7 +6096,7 @@
           <emphasis role="bold">Note</emphasis>: To use named time zones
           such as <literal>'MET'</literal> or
           <literal>'Europe/Moscow'</literal>, the time zone tables must
-          be properly set up. See <xref linkend="time-zone-support"/>
+          be properly set up. See <xref linkend="time-zone-support"/>,
           for instructions.
         </para>
 
@@ -8393,7 +8393,7 @@
         <para>
           For dates before 1582 (and possibly a later year in other
           locales), results from this function are not reliable. See
-          <xref linkend="mysql-calendar"/> for details.
+          <xref linkend="mysql-calendar"/>, for details.
         </para>
       </listitem>
 
@@ -9183,7 +9183,7 @@
     <para>
       It is also possible to perform a boolean search or a search with
       query expansion. These search types are described in
-      <xref linkend="fulltext-boolean"/> and
+      <xref linkend="fulltext-boolean"/>, and
       <xref linkend="fulltext-query-expansion"/>.
     </para>
 

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/innodb.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -170,7 +170,7 @@
       install MySQL-Max is to replace the executable
       <command>mysqld</command> server with the corresponding executable
       from the MySQL-Max distribution. MySQL and MySQL-Max differ only
-      in the server executable. See <xref linkend="installing-binary"/>
+      in the server executable. See <xref linkend="installing-binary"/>,
       and <xref linkend="mysqld-max"/>.
     </para>
 
@@ -509,7 +509,7 @@
     </para>
 
     <para>
-      See <xref linkend="innodb-init"/> for an example of what the
+      See <xref linkend="innodb-init"/>, for an example of what the
       information displayed by <literal>InnoDB</literal> should look
       like.
     </para>

Modified: trunk/refman-4.1/language-structure.xml
===================================================================
--- trunk/refman-4.1/language-structure.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/language-structure.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1593,7 +1593,7 @@
 
     <para>
       Further information about system startup options and system
-      variables can be found in <xref linkend="server-options"/> and
+      variables can be found in <xref linkend="server-options"/>, and
       <xref linkend="server-system-variables"/>. A list of the variables
       that can be set at runtime is given in
       <xref linkend="dynamic-system-variables"/>.

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -599,7 +599,7 @@
       <para>
         It is also possible to use the high-speed Scalable Coherent
         Interface (SCI) with MySQL Cluster, but this is not a
-        requirement. See <xref linkend="mysql-cluster-interconnects"/>
+        requirement. See <xref linkend="mysql-cluster-interconnects"/>,
         for more about this protocol and its use with MySQL Cluster.
       </para>
 
@@ -641,7 +641,7 @@
         use these rather than the binary files, be aware that you must
         install <emphasis>both</emphasis> the <literal>-server</literal>
         and <literal>-max</literal> packages on all machines that are to
-        host cluster nodes. (See <xref linkend="linux-rpm"/> for more
+        host cluster nodes. (See <xref linkend="linux-rpm"/>, for more
         information about installing MySQL using the RPMs.) After
         installing from RPM, you will still need to configure the
         cluster as discussed in <xref linkend="multi-config"/>.
@@ -986,7 +986,7 @@
       <para>
         For more detailed information about the available MySQL Cluster
         configuration parameters and their uses, see
-        <xref linkend="mysql-cluster-config-file"/> and
+        <xref linkend="mysql-cluster-config-file"/>, and
         <xref linkend="mysql-cluster-configuration"/>. For configuration
         of MySQL Cluster as relates to making backups, see
         <xref linkend="mysql-cluster-backup-configuration"/>.
@@ -1035,7 +1035,7 @@
             Note that <command>ndb_mgmd</command> must be told where to
             find its configuration file, using the <option>-f</option>
             or <option>--config-file</option> option. (See
-            <xref linkend="ndb-mgmd-process"/> for details.)
+            <xref linkend="ndb-mgmd-process"/>, for details.)
           </para>
         </listitem>
 
@@ -1116,7 +1116,7 @@
 
       <para>
         You should now be ready to work with databases, tables, and data
-        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>
+        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>,
         for a brief discussion.
       </para>
 
@@ -1612,7 +1612,7 @@
         In the next few sections, we assume that you are already
         familiar with installing MySQL, and here we cover only the
         differences between configuring MySQL Cluster and configuring
-        MySQL without clustering. (See <xref linkend="installing"/> if
+        MySQL without clustering. (See <xref linkend="installing"/>, if
         you require more information about the latter.)
       </para>
 
@@ -5363,7 +5363,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for more info
+        See <xref linkend="mysql-cluster-connectstring"/>, for more info
         on connectstrings.
       </para>
 
@@ -5550,7 +5550,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for additional
+        See <xref linkend="mysql-cluster-connectstring"/>, for additional
         information about this issue.
       </para>
 
@@ -5704,7 +5704,7 @@
 
       <para>
         Additional information about using <command>ndb_mgm</command>
-        can be found in <xref linkend="ndb-mgm-command-options"/> and
+        can be found in <xref linkend="ndb-mgm-command-options"/>, and
         <xref linkend="mgm-client-commands"/>.
       </para>
 
@@ -6119,7 +6119,7 @@
     <para>
       Managing a MySQL Cluster involves a number of tasks, the first of
       which is to configure and start MySQL Cluster. This is covered in
-      <xref linkend="mysql-cluster-configuration"/> and
+      <xref linkend="mysql-cluster-configuration"/>, and
       <xref linkend="mysql-cluster-process-management"/>.
     </para>
 
@@ -7932,7 +7932,7 @@
           shell using <command>ndb_mgm -e SHOW</command>). The switch
           <option>-c <replaceable>connectstring</replaceable></option>
           may be used to locate the MGM node (see
-          <xref linkend="mysql-cluster-connectstring"/> for information
+          <xref linkend="mysql-cluster-connectstring"/>, for information
           on connectstrings). The backup files must be present in the
           directory given as an argument to the restoration program.
         </para>
@@ -8763,7 +8763,7 @@
           <listitem>
             <para>
               Not all charsets and collations supported; see
-              <xref linkend="mysql-cluster-news-4-1-6"/> for a list of
+              <xref linkend="mysql-cluster-news-4-1-6"/>, for a list of
               those that are supported.
             </para>
           </listitem>
@@ -9028,7 +9028,7 @@
               <literal>READ_UNCOMMITTED</literal>,
               <literal>REPEATABLE_READ</literal>, and
               <literal>SERIALIZABLE</literal>.) See
-              <xref linkend="mysql-cluster-backup-troubleshooting"/> for
+              <xref linkend="mysql-cluster-backup-troubleshooting"/>, for
               information on how this can effect backup and restore of
               Cluster databases.
             </para>
@@ -9284,7 +9284,7 @@
         <para>
           The faster SCI protocol is also supported, but requires
           special hardware. See
-          <xref linkend="mysql-cluster-interconnects"/> for more
+          <xref linkend="mysql-cluster-interconnects"/>, for more
           information about SCI.
         </para>
       </listitem>
@@ -9597,7 +9597,7 @@
           binary has <literal>NDB</literal> support using either of the
           commands <literal>SHOW VARIABLES LIKE 'have_%';</literal> or
           <literal>SHOW ENGINES;</literal>. (See
-          <xref linkend="mysqld-max"/> for more information.)
+          <xref linkend="mysqld-max"/>, for more information.)
         </para>
 
         <para>
@@ -9642,7 +9642,7 @@
           To calculate the memory requirements more exactly requires
           determining, for each table in the cluster database, the
           storage space required per row (see
-          <xref linkend="storage-requirements"/> for details), and
+          <xref linkend="storage-requirements"/>, for details), and
           multiplying this by the number of rows. You must also remember
           to account for any column indexes as follows:
         </para>
@@ -9876,7 +9876,7 @@
 
           <listitem>
             <para>
-              <xref linkend="spatial-extensions"/> are not supported.
+              <xref linkend="spatial-extensions"/>, are not supported.
             </para>
           </listitem>
 
@@ -9948,7 +9948,7 @@
           convert existing tables using other storage engines to
           <literal>NDB Cluster</literal> using <literal>ALTER
           TABLE</literal>, but requires an additional workaround; see
-          <xref linkend="mysql-cluster-limitations-in-4-1"/> for
+          <xref linkend="mysql-cluster-limitations-in-4-1"/>, for
           details.
         </para>
       </listitem>
@@ -9967,7 +9967,7 @@
           high-speed (1 gigabit per second and higher),
           high-availability protocol used in building scalable
           multi-processor systems; it requires special hardware and
-          drivers. See <xref linkend="mysql-cluster-interconnects"/> for
+          drivers. See <xref linkend="mysql-cluster-interconnects"/>, for
           more about using SCI as a transport mechanism in MySQL
           Cluster.
         </para>
@@ -10020,7 +10020,7 @@
           remaining set to shut down. Arbitrator selection is controlled
           by the <literal>ArbitrationRank</literal> configuration
           parameter for MySQL Server and management server nodes. (See
-          <xref linkend="mysql-cluster-mgm-definition"/> for details.)
+          <xref linkend="mysql-cluster-mgm-definition"/>, for details.)
           It should also be noted that the role of arbitrator does not
           in and of itself impose any heavy demands upon the host so
           designated, and thus the arbitrator host does not need to be
@@ -10052,7 +10052,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-cluster-limitations-in-4-1"/> for
+          See <xref linkend="mysql-cluster-limitations-in-4-1"/>, for
           more information about these issues.
         </para>
       </listitem>
@@ -10132,7 +10132,7 @@
 
         <para>
           For more information, see
-          <xref linkend="mgm-client-commands"/> and
+          <xref linkend="mgm-client-commands"/>, and
           <xref linkend="multi-shutdown-restart"/>.
         </para>
       </listitem>
@@ -10281,7 +10281,7 @@
           Text files containing directives and information regarding the
           cluster, its hosts, and its nodes. These are read by the
           cluster's management nodes when the cluster is started. See
-          <xref linkend="mysql-cluster-config-file"/> for details.
+          <xref linkend="mysql-cluster-config-file"/>, for details.
         </para>
       </listitem>
 

Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/optimization.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -169,7 +169,7 @@
 
       <para>
         For more information about this, see
-        <xref linkend="constraints"/> and <xref linkend="insert"/> or
+        <xref linkend="constraints"/>, and <xref linkend="insert"/>, or
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -1290,7 +1290,7 @@
             optimizer choose better indexes. For
             <literal>MyISAM</literal> tables, <command>myisamchk
             --analyze</command> does the same. See
-            <xref linkend="analyze-table"/> and
+            <xref linkend="analyze-table"/>, and
             <xref linkend="table-maintenance"/>.
           </para>
         </listitem>
@@ -1900,7 +1900,7 @@
         tables should usually be done with indexes. You can use the
         <literal>EXPLAIN</literal> statement to determine which indexes
         are used for a <literal>SELECT</literal>. See
-        <xref linkend="mysql-indexes"/> and <xref linkend="explain"/>.
+        <xref linkend="mysql-indexes"/>, and <xref linkend="explain"/>.
       </para>
 
       <para>
@@ -2549,7 +2549,7 @@
             </para>
 
             <para>
-              See <xref linkend="range-access-single-part"/> for the
+              See <xref linkend="range-access-single-part"/>, for the
               definition of what is considered to be a constant.
             </para>
 
@@ -2676,7 +2676,7 @@
         </itemizedlist>
 
         <para>
-          <xref linkend="range-access-single-part"/> describes how
+          <xref linkend="range-access-single-part"/>, describes how
           optimizations are performed to combine or eliminate intervals
           for range conditions on single-part index. Analogous steps are
           performed for range conditions on multiple-part keys.
@@ -5023,7 +5023,7 @@
             If you encounter speed problems with table locks in MySQL,
             you may be able to improve performance by converting some of
             your tables to <literal>InnoDB</literal> or
-            <literal>BDB</literal> tables. See <xref linkend="innodb"/>
+            <literal>BDB</literal> tables. See <xref linkend="innodb"/>,
             and <xref linkend="bdb-storage-engine"/>.
           </para>
         </listitem>
@@ -5361,7 +5361,7 @@
         <literal>CHAR</literal>, <literal>VARCHAR</literal>, and
         <literal>TEXT</literal> columns. Indexing always takes place
         over the entire column and partial (prefix) indexing is not
-        supported. See <xref linkend="fulltext-search"/> for details.
+        supported. See <xref linkend="fulltext-search"/>, for details.
       </para>
 
       <para>
@@ -6134,7 +6134,7 @@
           <literal>keycache1.key_buffer_size</literal>,
           <literal>keycache1</literal> is the cache variable name and
           <literal>key_buffer_size</literal> is the cache component. See
-          <xref linkend="structured-system-variables"/> for a
+          <xref linkend="structured-system-variables"/>, for a
           description of the syntax used for referring to structured key
           cache system variables.
         </para>
@@ -6968,7 +6968,7 @@
         If the value is very large, even when you have not issued many
         <literal>FLUSH TABLES</literal> statements, you should increase
         the table cache size. See
-        <xref linkend="server-system-variables"/> and
+        <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 
@@ -7229,7 +7229,7 @@
 
       <para>
         You can find a full description for all system and status
-        variables in <xref linkend="server-system-variables"/> and
+        variables in <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/problems.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -3635,7 +3635,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="working-with-null"/> for additional
+        See <xref linkend="working-with-null"/>, for additional
         information and examples.
       </para>
 
@@ -3814,7 +3814,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="show-table-status"/> and
+        See <xref linkend="show-table-status"/>, and
         <xref linkend="show-create-table"/>.
       </para>
 
@@ -3846,7 +3846,7 @@
       </para>
 
       <para>
-        See <xref linkend="show-engines"/> and
+        See <xref linkend="show-engines"/>, and
         <xref linkend="show-variables"/>.
       </para>
 
@@ -4587,7 +4587,7 @@
         <listitem>
           <para>
             There are known issues in using temporary tables with
-            replication. See <xref linkend="replication-features"/> for 
+            replication. See <xref linkend="replication-features"/>, for 
             more information.
           </para>
         </listitem>
@@ -4629,7 +4629,7 @@
     <para>
       For information about platform-specific issues, see the
       installation and porting instructions in
-      <xref linkend="operating-system-specific-notes"/> and
+      <xref linkend="operating-system-specific-notes"/>, and
       <xref linkend="porting"/>.
     </para>
 

Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/replication.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -725,7 +725,7 @@
         <filename>relay-log.info</filename> by default. They contain
         information like that shown in the output of the <literal>SHOW
         SLAVE STATUS</literal> statement (see
-        <xref linkend="replication-slave-sql"/> for a description of
+        <xref linkend="replication-slave-sql"/>, for a description of
         this statement). As disk files, they survive a slave server's
         shutdown. The next time the slave starts up, it reads these
         files to determine how far it has proceeded in reading binary
@@ -956,7 +956,7 @@
     <para>
       If you want to administer a MySQL replication setup, we suggest
       that you read this entire chapter through and try all statements
-      mentioned in <xref linkend="replication-master-sql"/> and
+      mentioned in <xref linkend="replication-master-sql"/>, and
       <xref linkend="replication-slave-sql"/>. You should also
       familiarize yourself with replication startup options described in
       <xref linkend="replication-options"/>.
@@ -1441,7 +1441,7 @@
       <emphasis role="bold">Note</emphasis>: The content of
       <filename>master.info</filename> overrides some of the options
       specified on the command line or in <filename>my.cnf</filename>.
-      See <xref linkend="replication-options"/> for more details.
+      See <xref linkend="replication-options"/>, for more details.
     </para>
 
     <para>
@@ -1936,7 +1936,7 @@
           <literal>MEMORY</literal> table after startup, it notifies
           slaves that the table needs to be emptied by writing a
           <literal>DELETE FROM</literal> statement for that table to the
-          binary log. See <xref linkend="memory-storage-engine"/> for
+          binary log. See <xref linkend="memory-storage-engine"/>, for
           more information.
         </para>
       </listitem>
@@ -4206,7 +4206,7 @@
           it is a bug or you have encountered one of the known
           replication limitations described in
           <xref linkend="replication-features"/>. If it is a bug, see
-          <xref linkend="replication-bugs"/> for instructions on how to
+          <xref linkend="replication-bugs"/>, for instructions on how to
           report it.
         </para>
       </listitem>

Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/sql-syntax.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1898,7 +1898,7 @@
             <literal>VARCHAR</literal>, and <literal>TEXT</literal>
             columns. Indexing always happens over the entire column;
             partial indexing is not supported and any prefix length is
-            ignored if specified. See <xref linkend="fulltext-search"/>
+            ignored if specified. See <xref linkend="fulltext-search"/>,
             for details of operation.
           </para>
         </listitem>
@@ -2458,7 +2458,7 @@
             <option>--skip-symbolic-links</option> option. Your
             operating system must also have a working, thread-safe
             <literal>realpath()</literal> call. See
-            <xref linkend="symbolic-links-to-tables"/> for more complete
+            <xref linkend="symbolic-links-to-tables"/>, for more complete
             information.
           </para>
         </listitem>
@@ -3345,7 +3345,7 @@
         <command>myisamchk</command> utility to reorganize tables.
         <literal>OPTIMIZE TABLE</literal> is easier, but
         <command>myisamchk</command> is faster. See
-        <xref linkend="optimize-table"/> and
+        <xref linkend="optimize-table"/>, and
         <xref linkend="optimization"/>.
       </para>
 
@@ -4211,7 +4211,7 @@
         behave identically. The behavior of <literal>INSERT</literal>
         statements with respect to <literal>AUTO_INCREMENT</literal>
         columns is discussed further in
-        <xref linkend="information-functions"/> and
+        <xref linkend="information-functions"/>, and
         <xref linkend="mysql-insert-id"/>.
       </para>
 
@@ -5983,7 +5983,7 @@
         <literal>SELECT</literal> is used to retrieve rows selected from
         one or more tables. Support for <literal>UNION</literal>
         statements and subqueries is available as of MySQL 4.0 and 4.1,
-        respectively. See <xref linkend="union"/> and
+        respectively. See <xref linkend="union"/>, and
         <xref linkend="subqueries"/>.
       </para>
 
@@ -6191,7 +6191,7 @@
             or
             <replaceable>db_name</replaceable>.<replaceable>tbl_name</replaceable>
             prefix for a column reference unless the reference would be
-            ambiguous. See <xref linkend="legal-names"/> for examples of
+            ambiguous. See <xref linkend="legal-names"/>, for examples of
             ambiguity that require the more explicit column reference
             forms.
           </para>
@@ -11228,7 +11228,7 @@
               provided that you omit those columns for which you do not
               have the <literal>INSERT</literal> privilege. The omitted
               columns are set to their implicit default values.
-              <xref linkend="create-table"/> discusses implicit default
+              <xref linkend="create-table"/>, discusses implicit default
               values.
             </para>
           </listitem>
@@ -11317,7 +11317,7 @@
           to a MySQL 4.1 or later server using a pre-4.1 client program,
           do not use the preceding <literal>SET PASSWORD</literal> or
           <literal>UPDATE</literal> statement without reading
-          <xref linkend="password-hashing"/> first. The password format
+          <xref linkend="password-hashing"/>, first. The password format
           changed in MySQL 4.1, and under certain circumstances it is
           possible that if you change your password, you might not be
           able to connect to the server afterward.
@@ -15187,7 +15187,7 @@
           these variables using command-line options when
           <command>mysqld</command> starts or at runtime with the
           <literal>SET</literal> statement. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="set-option"/>.
         </para>
 
@@ -15804,7 +15804,7 @@
         </para>
 
         <para>
-          See also <xref linkend="reset"/> for information about how the
+          See also <xref linkend="reset"/>, for information about how the
           <literal>RESET</literal> statement is used with replication.
         </para>
 
@@ -16144,7 +16144,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing master replication
-        servers. <xref linkend="replication-slave-sql"/> discusses
+        servers. <xref linkend="replication-slave-sql"/>, discusses
         statements for managing slave servers.
       </para>
 
@@ -16404,7 +16404,7 @@
         <para>
           Lists the binary log files on the server. This statement is
           used as part of the procedure described in
-          <xref linkend="purge-master-logs"/> for determining which logs
+          <xref linkend="purge-master-logs"/>, for determining which logs
           can be purged.
         </para>
 
@@ -16533,7 +16533,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing slave replication
-        servers. <xref linkend="replication-master-sql"/> discusses
+        servers. <xref linkend="replication-master-sql"/>, discusses
         statements for managing master servers.
       </para>
 
@@ -16966,7 +16966,7 @@
           This is actually a function, not a statement. It is used to
           ensure that the slave has read and executed events up to a
           given position in the master's binary log. See
-          <xref linkend="miscellaneous-functions"/> for a full
+          <xref linkend="miscellaneous-functions"/>, for a full
           description.
         </para>
 

Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/storage-engines.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -235,7 +235,7 @@
   <para>
     This chapter describes each of the MySQL storage engines except for
     <literal>InnoDB</literal> and <literal>NDB Cluster</literal>, which
-    are covered in <xref linkend="innodb"/> and
+    are covered in <xref linkend="innodb"/>, and
     <xref linkend="ndbcluster"/>.
   </para>
 
@@ -286,7 +286,7 @@
 </programlisting>
 
   <para>
-    See <xref linkend="create-table"/> and
+    See <xref linkend="create-table"/>, and
     <xref linkend="alter-table"/>.
   </para>
 
@@ -1431,7 +1431,7 @@
           corruption is a result of the server dying. Otherwise,
           corruption may have occurred during normal operation. This is
           a bug. You should try to create a reproducible test case that
-          demonstrates the problem. See <xref linkend="crashing"/> and
+          demonstrates the problem. See <xref linkend="crashing"/>, and
           <xref linkend="reproduceable-test-case"/>.
         </para>
 
@@ -1553,7 +1553,7 @@
             <para>
               In general, it is a bad idea to share a data directory
               among multiple servers. See
-              <xref linkend="multiple-servers"/> for additional
+              <xref linkend="multiple-servers"/>, for additional
               discussion.
             </para>
           </listitem>
@@ -1910,7 +1910,7 @@
           used up does the storage engine need to read the next key
           block. This makes <literal>MERGE</literal> keys much slower on
           <literal>eq_ref</literal> searches, but not much slower on
-          <literal>ref</literal> searches. See <xref linkend="explain"/>
+          <literal>ref</literal> searches. See <xref linkend="explain"/>,
           for more information about <literal>eq_ref</literal> and
           <literal>ref</literal>.
         </para>
@@ -2334,7 +2334,7 @@
           statements such as <literal>INSERT INTO ... SELECT</literal>
           or <literal>LOAD DATA INFILE</literal> into this file in order
           to load the table from a persistent data source. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="load-data"/>.
         </para>
       </listitem>
@@ -2985,7 +2985,7 @@
             unexpectedly. It should not be fatal even if this number is
             not 100% correct. You can update the row count by using
             <literal>ANALYZE TABLE</literal> or <literal>OPTIMIZE
-            TABLE</literal>. See <xref linkend="analyze-table"/> and
+            TABLE</literal>. See <xref linkend="analyze-table"/>, and
             <xref linkend="optimize-table"/>.
           </para>
         </listitem>

Modified: trunk/refman-4.1/tutorial.xml
===================================================================
--- trunk/refman-4.1/tutorial.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-4.1/tutorial.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1146,7 +1146,7 @@
       <para>
         If the statement fails, it is likely that your MySQL
         installation does not have local file capability enabled by
-        default. See <xref linkend="load-data-local"/> for information
+        default. See <xref linkend="load-data-local"/>, for information
         on how to change this.
       </para>
 
@@ -2315,7 +2315,7 @@
 </programlisting>
 
         <para>
-          <xref linkend="regexp"/> provides more information about the
+          <xref linkend="regexp"/>, provides more information about the
           syntax for regular expressions.
         </para>
 
@@ -3902,7 +3902,7 @@
           <listitem>
             <para>
               How to assign the <literal>AUTO_INCREMENT</literal>
-              attribute to a column: <xref linkend="create-table"/> and
+              attribute to a column: <xref linkend="create-table"/>, and
               <xref linkend="alter-table"/>.
             </para>
           </listitem>

Modified: trunk/refman-5.0/apis.xml
===================================================================
--- trunk/refman-5.0/apis.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/apis.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -307,7 +307,7 @@
         program, use the <option>--defaults-file</option> option as one
         of the elements of the second argument of the
         <literal>mysql_server_init()</literal> function. See
-        <xref linkend="mysql-server-init"/> for more information on the
+        <xref linkend="mysql-server-init"/>, for more information on the
         <literal>mysql_server_init()</literal> function.
       </para>
 
@@ -4583,7 +4583,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -4613,7 +4613,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -9074,7 +9074,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-affected-rows"/> for additional
+          See <xref linkend="mysql-affected-rows"/>, for additional
           information on the return value.
         </para>
 
@@ -9129,7 +9129,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-stmt-attr-set"/> for a list of
+          See <xref linkend="mysql-stmt-attr-set"/>, for a list of
           options and option types.
         </para>
 
@@ -10761,7 +10761,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-insert-id"/> for more information.
+          See <xref linkend="mysql-insert-id"/>, for more information.
         </para>
 
         <para>
@@ -13005,7 +13005,7 @@
             downgrade to MySQL 4.0; switch to PHP 5 and the newer
             <literal>mysqli</literal> extension; or configure the MySQL
             server with <option>--old-passwords</option>. (See
-            <xref linkend="old-client"/> for more information.)
+            <xref linkend="old-client"/>, for more information.)
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/client-side-scripts.xml
===================================================================
--- trunk/refman-5.0/client-side-scripts.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/client-side-scripts.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -29,7 +29,7 @@
     This chapter provides a brief overview of these programs and then a
     more detailed description of each one. The descriptions indicate how
     to invoke the programs and the options they understand. See
-    <xref linkend="using-mysql-programs"/> for general information on
+    <xref linkend="using-mysql-programs"/>, for general information on
     invoking programs and specifying program options.
   </para>
 
@@ -1401,7 +1401,7 @@
             <para>
               Execute the statement and quit. The default output format
               is like that produced with <option>--batch</option>. See
-              <xref linkend="command-line-options"/> for some examples.
+              <xref linkend="command-line-options"/>, for some examples.
             </para>
           </listitem>
 
@@ -1779,7 +1779,7 @@
               affect using key values. If you have set this option in an
               option file, you can override it by using
               <option>--safe-updates</option> on the command line. See
-              <xref linkend="mysql-tips"/> for more information about
+              <xref linkend="mysql-tips"/>, for more information about
               this option.
             </para>
           </listitem>

Modified: trunk/refman-5.0/connector-odbc.xml
===================================================================
--- trunk/refman-5.0/connector-odbc.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/connector-odbc.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1004,7 +1004,7 @@
 </programlisting>
 
       <para>
-        Then proceed on to <xref linkend="dsn-on-unix"/> to configure
+        Then proceed on to <xref linkend="dsn-on-unix"/>, to configure
         the DSN for MyODBC. For more information, refer to the
         <filename>INSTALL-BINARY</filename> file that comes with your
         distribution.
@@ -1950,7 +1950,7 @@
 
       <listitem>
         <para>
-          See <xref linkend="installing-source-tree"/> for instructions
+          See <xref linkend="installing-source-tree"/>, for instructions
           on how to download and install BitKeeper.
         </para>
       </listitem>
@@ -2376,7 +2376,7 @@
         The DSN configuration dialog also has an
         <literal>Options</literal> button. If you select it, the
         following options dialog appears displaying that control driver
-        behavior. Refer to <xref linkend="connection-parameters"/> for
+        behavior. Refer to <xref linkend="connection-parameters"/>, for
         information about the meaning of these options.
       </para>
 
@@ -5017,7 +5017,7 @@
 
       <para>
         A simple examples for the usage of ADO, DAO and RDO with VB can
-        be found her:
+        be found here:
       </para>
 
       <itemizedlist>
@@ -5402,13 +5402,13 @@
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-c-sharp-cp"/>
+            See <xref linkend="odbc-net-op-c-sharp-cp"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-vb-cp"/>
+            See <xref linkend="odbc-net-op-vb-cp"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/data-types.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -2228,7 +2228,7 @@
       strict mode, these statements fail, and some or all of the values
       will not be inserted or changed, depending on whether the table is
       a transactional table and other factors. See
-      <xref linkend="server-sql-mode"/> for details.
+      <xref linkend="server-sql-mode"/>, for details.
     </para>
 
   </section>
@@ -2749,7 +2749,7 @@
             With strict mode enabled, invalid dates generate an error.
             To allow such dates, enable
             <literal>ALLOW_INVALID_DATES</literal>. See
-            <xref linkend="server-sql-mode"/> for more information.
+            <xref linkend="server-sql-mode"/>, for more information.
           </para>
 
           <para>
@@ -4664,7 +4664,7 @@
       data types, the record format is also variable length. When a
       table is created, MySQL may, under certain conditions, change a
       column from a variable-length type to a fixed-length type or vice
-      versa. See <xref linkend="silent-column-changes"/> for more
+      versa. See <xref linkend="silent-column-changes"/>, for more
       information.
     </para>
 

Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/database-administration.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -305,7 +305,7 @@
             server named <command>mysqld-max</command>. The
             <literal>MySQL-Max</literal> RPM presupposes that you have
             installed the regular server RPM. See
-            <xref linkend="linux-rpm"/> for more information on the
+            <xref linkend="linux-rpm"/>, for more information on the
             Linux RPM packages.
           </para>
         </listitem>
@@ -1280,7 +1280,7 @@
             the <command>mysql.server</command> script will be installed
             in the <filename>/etc/init.d</filename> directory with the
             name <filename>mysql</filename>. You need not install it
-            manually. See <xref linkend="linux-rpm"/> for more
+            manually. See <xref linkend="linux-rpm"/>, for more
             information on the Linux RPM packages.
           </para>
 
@@ -3394,7 +3394,7 @@
               The binary log file. Log all queries that change data to
               this file. Used for backup and replication. See
               <xref linkend="binary-log"/>. It is recommended to specify
-              a filename (see <xref linkend="open-bugs"/> for the
+              a filename (see <xref linkend="open-bugs"/>, for the
               reason) otherwise MySQL uses
               <filename><replaceable>host_name</replaceable>-bin</filename>
               as the log file basename.
@@ -3692,7 +3692,7 @@
               is possible to point out the management server that
               distributes the cluster configuration by setting the
               connect string option. See
-              <xref linkend="mysql-cluster-connectstring"/> for syntax.
+              <xref linkend="mysql-cluster-connectstring"/>, for syntax.
             </para>
           </listitem>
 
@@ -3970,7 +3970,7 @@
               resources for this storage engine only if
               <option>--skip-ndbcluster</option> is explicitly
               overridden using the <option>--ndbcluster</option> option.
-              See <xref linkend="mysql-cluster-quick"/> for an example
+              See <xref linkend="mysql-cluster-quick"/>, for an example
               of usage.
             </para>
           </listitem>
@@ -5272,7 +5272,7 @@
         <para>
           You can view system variables and their values by using the
           <literal>SHOW VARIABLES</literal> statement. See
-          <xref linkend="system-variables"/> for more information.
+          <xref linkend="system-variables"/>, for more information.
         </para>
 
 <programlisting>
@@ -6297,7 +6297,7 @@
               <literal>MyISAM</literal> tables by starting the server
               with the <option>--myisam-recover</option> option (for
               example, <option>--myisam-recover=BACKUP,FORCE</option>).
-              See <xref linkend="server-options"/> and
+              See <xref linkend="server-options"/>, and
               <xref linkend="myisam-start"/>.
             </para>
 
@@ -7419,7 +7419,7 @@
               The number of simultaneous client connections allowed.
               Increasing this value increases the number of file
               descriptors that <command>mysqld</command> requires. See
-              <xref linkend="table-cache"/> for comments on file
+              <xref linkend="table-cache"/>, for comments on file
               descriptor limits. Also see
               <xref linkend="too-many-connections"/>.
             </para>
@@ -8042,7 +8042,7 @@
               The default value is 0, which disables the query cache.
               Note that this amount of memory is allocated even if
               <literal>query_cache_type</literal> is set to 0. See
-              <xref linkend="query-cache-configuration"/> for more
+              <xref linkend="query-cache-configuration"/>, for more
               information.
             </para>
           </listitem>
@@ -8584,7 +8584,7 @@
               implementation.) By examining the difference between the
               <literal>Connections</literal> and
               <literal>Threads_created</literal> status variables (see
-              <xref linkend="server-status-variables"/> for details) you
+              <xref linkend="server-status-variables"/>, for details) you
               can see how efficient the thread cache is.
             </para>
           </listitem>
@@ -11832,7 +11832,7 @@
         algorithm is not as strong as the newer algorithm; with some
         effort a clever attacker who can sniff the traffic between the
         client and the server can crack the password. (See
-        <xref linkend="password-hashing"/> for a discussion of the
+        <xref linkend="password-hashing"/>, for a discussion of the
         different password handling methods.) If the connection between
         the client and the server goes through an untrusted network, you
         should use an SSH tunnel to encrypt the communication.
@@ -12483,7 +12483,7 @@
         If your privileges are changed (either by yourself or someone
         else) while you are connected, those changes do not necessarily
         take effect immediately for the next statement you issue. See
-        <xref linkend="privilege-changes"/> for details.
+        <xref linkend="privilege-changes"/>, for details.
       </para>
 
       <para>
@@ -15029,7 +15029,7 @@
 
           <para>
             For information on how to deal with this, see
-            <xref linkend="password-hashing"/> and
+            <xref linkend="password-hashing"/>, and
             <xref linkend="old-client"/>.
           </para>
         </listitem>
@@ -15166,7 +15166,7 @@
             <literal>CREATE USER</literal> statements, or the
             <command>mysqladmin password</command> command, all of which
             automatically use <literal>PASSWORD()</literal> to encrypt
-            the password. See <xref linkend="passwords"/> and
+            the password. See <xref linkend="passwords"/>, and
             <xref linkend="create-user"/>.
           </para>
         </listitem>
@@ -17414,7 +17414,7 @@
 </programlisting>
 
           <para>
-            <xref linkend="option-files"/> discusses option files in
+            <xref linkend="option-files"/>, discusses option files in
             more detail.
           </para>
         </listitem>
@@ -18433,7 +18433,7 @@
         backup. To get a consistent backup, do a <literal>LOCK
         TABLES</literal> on the relevant tables, followed by
         <literal>FLUSH TABLES</literal> for the tables. See
-        <xref linkend="lock-tables"/> and <xref linkend="flush"/>. You
+        <xref linkend="lock-tables"/>, and <xref linkend="flush"/>. You
         need only a read lock; this allows other clients to continue to
         query the tables while you are making a copy of the files in the
         database directory. The <literal>FLUSH TABLES</literal>
@@ -18448,14 +18448,14 @@
         the output file cannot previously exist. This is also true of
         <literal>BACKUP TABLE</literal>, since allowing extant files to
         be overwritten would constitute a security risk. See
-        <xref linkend="select"/> and <xref linkend="backup-table"/>.
+        <xref linkend="select"/>, and <xref linkend="backup-table"/>.
       </para>
 
       <para>
         Another technique for backing up a database is to use the
         <command>mysqldump</command> program or the
         <command>mysqlhotcopy script</command>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <orderedlist>
@@ -18512,7 +18512,7 @@
       <para>
         For <literal>InnoDB</literal> tables, it's possible to perform
         an online backup that takes no locks on tables; see
-        <xref linkend="mysqldump"/>
+        <xref linkend="mysqldump"/>.
       </para>
 
       <para>
@@ -18530,7 +18530,7 @@
         should also rotate the binary log using <literal>FLUSH
         LOGS</literal>, <literal>mysqldump --flush-logs</literal>, or
         <literal>mysqlhotcopy --flushlogs</literal>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <para>
@@ -18585,7 +18585,7 @@
             logs, from certain positions (usually you want to re-run all
             binary logs from the date of the restored backup, excepting
             possibly some incorrect queries). See
-            <xref linkend="mysqlbinlog"/> for more information on the
+            <xref linkend="mysqlbinlog"/>, for more information on the
             <command>mysqlbinlog</command> utility and how to use it.
           </para>
         </listitem>
@@ -19777,7 +19777,7 @@
             <literal>myisam_stats_method</literal> system variable. For
             more information, see the description of
             <literal>myisam_stats_method</literal> in
-            <xref linkend="server-system-variables"/> and
+            <xref linkend="server-system-variables"/>, and
             <xref linkend="myisam-index-statistics"/>. For MySQL
             &current-series;, <literal>stats_method</literal> was added
             in MySQL 5.0.14. For older versions, the statistics
@@ -20736,7 +20736,7 @@
             <literal>CHECK TABLE</literal> and <literal>REPAIR
             TABLE</literal> statements to check and repair
             <literal>MyISAM</literal> tables. See
-            <xref linkend="check-table"/> and
+            <xref linkend="check-table"/>, and
             <xref linkend="repair-table"/>.
           </para>
 
@@ -21152,7 +21152,7 @@
         rather than waiting for problems to occur. One way to check and
         repair <literal>MyISAM</literal> tables is with the
         <literal>CHECK TABLE</literal> and <literal>REPAIR
-        TABLE</literal> statements. See <xref linkend="check-table"/>
+        TABLE</literal> statements. See <xref linkend="check-table"/>,
         and <xref linkend="repair-table"/>.
       </para>
 
@@ -23114,7 +23114,7 @@
         <literal>-bin</literal>. If file name is given, but it doesn't
         contain a path, the file is written in the data directory. It is
         recommended to specify a filename, see
-        <xref linkend="open-bugs"/> for the reason.
+        <xref linkend="open-bugs"/>, for the reason.
       </para>
 
       <para>
@@ -23151,7 +23151,7 @@
         You can delete all binary log files with the <literal>RESET
         MASTER</literal> statement, or only some of them with
         <literal>PURGE MASTER LOGS</literal>. See
-        <xref linkend="reset"/> and
+        <xref linkend="reset"/>, and
         <xref linkend="replication-master-sql"/>.
       </para>
 
@@ -23415,7 +23415,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysqlbinlog"/> for more information on the
+        See <xref linkend="mysqlbinlog"/>, for more information on the
         <command>mysqlbinlog</command> utility and how to use it.
       </para>
 
@@ -24476,7 +24476,7 @@
       </para>
 
       <para>
-        <xref linkend="environment-variables"/> includes a list of other
+        <xref linkend="environment-variables"/>, includes a list of other
         environment variables you can use to affect
         <command>mysqld</command>.
       </para>
@@ -24739,7 +24739,7 @@
 
       <para>
         This section describes how the query cache works when it is
-        operational. <xref linkend="query-cache-configuration"/>
+        operational. <xref linkend="query-cache-configuration"/>,
         describes how to control whether or not it is operational.
       </para>
 

Modified: trunk/refman-5.0/extending-mysql.xml
===================================================================
--- trunk/refman-5.0/extending-mysql.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/extending-mysql.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -865,7 +865,7 @@
         constraints may change in future versions of the server, so it
         is possible that server upgrades will require revisions to UDFs
         that were originally written for older servers. For information
-        about these constraints, see <xref linkend="configure-options"/>
+        about these constraints, see <xref linkend="configure-options"/>,
         and <xref linkend="compilation-problems"/>.
       </para>
 
@@ -1148,7 +1148,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create a simple UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 
@@ -1324,7 +1324,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create an aggregate UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 

Modified: trunk/refman-5.0/functions.xml
===================================================================
--- trunk/refman-5.0/functions.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/functions.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -5970,7 +5970,7 @@
     <para>
       This section describes the functions that can be used to
       manipulate temporal values. See
-      <xref linkend="date-and-time-types"/> for a description of the
+      <xref linkend="date-and-time-types"/>, for a description of the
       range of values each date and time type has and the valid formats
       in which values may be specified.
     </para>
@@ -6180,7 +6180,7 @@
           <emphasis role="bold">Note</emphasis>: To use named time zones
           such as <literal>'MET'</literal> or
           <literal>'Europe/Moscow'</literal>, the time zone tables must
-          be properly set up. See <xref linkend="time-zone-support"/>
+          be properly set up. See <xref linkend="time-zone-support"/>,
           for instructions.
         </para>
       </listitem>
@@ -8499,7 +8499,7 @@
         <para>
           For dates before 1582 (and possibly a later year in other
           locales), results from this function are not reliable. See
-          <xref linkend="mysql-calendar"/> for details.
+          <xref linkend="mysql-calendar"/>, for details.
         </para>
       </listitem>
 
@@ -9248,7 +9248,7 @@
     <para>
       It is also possible to perform a boolean search or a search with
       query expansion. These search types are described in
-      <xref linkend="fulltext-boolean"/> and
+      <xref linkend="fulltext-boolean"/>, and
       <xref linkend="fulltext-query-expansion"/>.
     </para>
 
@@ -13551,7 +13551,7 @@
             use only. The server uses it when writing statements from
             stored routines that contain references to local routine
             variables, as described in
-            <xref linkend="stored-procedure-logging"/> You might see
+            <xref linkend="stored-procedure-logging"/>, You might see
             this function in the output from
             <command>mysqlbinlog</command>.
           </para>

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/innodb.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -430,7 +430,7 @@
     </para>
 
     <para>
-      See <xref linkend="innodb-init"/> for an example of what the
+      See <xref linkend="innodb-init"/>, for an example of what the
       information displayed by <literal>InnoDB</literal> should look
       like.
     </para>
@@ -5291,7 +5291,7 @@
       would be good to throttle new row operations, and allocate more
       resources to the purge thread. The startup option and settable
       global variable <literal>innodb_max_purge_lag</literal> exists for
-      exactly this purpose. See <xref linkend="innodb-start"/> for more
+      exactly this purpose. See <xref linkend="innodb-start"/>, for more
       information.
     </para>
 

Modified: trunk/refman-5.0/language-structure.xml
===================================================================
--- trunk/refman-5.0/language-structure.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/language-structure.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1580,7 +1580,7 @@
 
     <para>
       Further information about system startup options and system
-      variables can be found in <xref linkend="server-options"/> and
+      variables can be found in <xref linkend="server-options"/>, and
       <xref linkend="server-system-variables"/>. A list of the variables
       that can be set at runtime is given in
       <xref linkend="dynamic-system-variables"/>.

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -605,7 +605,7 @@
       <para>
         It is also possible to use the high-speed Scalable Coherent
         Interface (SCI) with MySQL Cluster, but this is not a
-        requirement. See <xref linkend="mysql-cluster-interconnects"/>
+        requirement. See <xref linkend="mysql-cluster-interconnects"/>,
         for more about this protocol and its use with MySQL Cluster.
       </para>
 
@@ -647,7 +647,7 @@
         aware that you must install <emphasis>both</emphasis> the
         <literal>-server</literal> and <literal>-max</literal> packages
         on all machines that are to host cluster nodes. (See
-        <xref linkend="linux-rpm"/> for more information about
+        <xref linkend="linux-rpm"/>, for more information about
         installing MySQL using the RPMs.) After installing from RPM, you
         will still need to configure the cluster as discussed in
         <xref linkend="multi-config"/>.
@@ -992,7 +992,7 @@
       <para>
         For more detailed information about the available MySQL Cluster
         configuration parameters and their uses, see
-        <xref linkend="mysql-cluster-config-file"/> and
+        <xref linkend="mysql-cluster-config-file"/>, and
         <xref linkend="mysql-cluster-configuration"/>. For configuration
         of MySQL Cluster as relates to making backups, see
         <xref linkend="mysql-cluster-backup-configuration"/>.
@@ -1041,7 +1041,7 @@
             Note that <command>ndb_mgmd</command> must be told where to
             find its configuration file, using the <option>-f</option>
             or <option>--config-file</option> option. (See
-            <xref linkend="ndb-mgmd-process"/> for details.)
+            <xref linkend="ndb-mgmd-process"/>, for details.)
           </para>
         </listitem>
 
@@ -1122,7 +1122,7 @@
 
       <para>
         You should now be ready to work with databases, tables, and data
-        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>
+        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>,
         for a brief discussion.
       </para>
 
@@ -1621,7 +1621,7 @@
         In the next few sections, we assume that you are already
         familiar with installing MySQL, and here we cover only the
         differences between configuring MySQL Cluster and configuring
-        MySQL without clustering. (See <xref linkend="installing"/> if
+        MySQL without clustering. (See <xref linkend="installing"/>, if
         you require more information about the latter.)
       </para>
 
@@ -5374,7 +5374,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for more info
+        See <xref linkend="mysql-cluster-connectstring"/>, for more info
         on connectstrings.
       </para>
 
@@ -5544,7 +5544,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for additional
+        See <xref linkend="mysql-cluster-connectstring"/>, for additional
         information about this issue.
       </para>
 
@@ -5690,7 +5690,7 @@
 
       <para>
         Additional information about using <command>ndb_mgm</command>
-        can be found in <xref linkend="ndb-mgm-command-options"/> and
+        can be found in <xref linkend="ndb-mgm-command-options"/>, and
         <xref linkend="mgm-client-commands"/>.
       </para>
 
@@ -6093,7 +6093,7 @@
     <para>
       Managing a MySQL Cluster involves a number of tasks, the first of
       which is to configure and start MySQL Cluster. This is covered in
-      <xref linkend="mysql-cluster-configuration"/> and
+      <xref linkend="mysql-cluster-configuration"/>, and
       <xref linkend="mysql-cluster-process-management"/>.
     </para>
 
@@ -7906,7 +7906,7 @@
           shell using <command>ndb_mgm -e SHOW</command>). The switch
           <option>-c <replaceable>connectstring</replaceable></option>
           may be used to locate the MGM node (see
-          <xref linkend="mysql-cluster-connectstring"/> for information
+          <xref linkend="mysql-cluster-connectstring"/>, for information
           on connectstrings). The backup files must be present in the
           directory given as an argument to the restoration program.
         </para>
@@ -9007,7 +9007,7 @@
               <literal>READ_COMMITTED</literal>,
               <literal>REPEATABLE_READ</literal>, and
               <literal>SERIALIZABLE</literal>.) See
-              <xref linkend="mysql-cluster-backup-troubleshooting"/> for
+              <xref linkend="mysql-cluster-backup-troubleshooting"/>, for
               information on how this can effect backup and restore of
               Cluster databases.
             </para>
@@ -9361,7 +9361,7 @@
         <listitem>
           <para>
             <emphasis role="bold">Query Cache Enabled for MySQL
-            Cluster</emphasis>: See <xref linkend="query-cache"/> for
+            Cluster</emphasis>: See <xref linkend="query-cache"/>, for
             information on configuring ans using the query cache.
           </para>
         </listitem>
@@ -9561,7 +9561,7 @@
         <para>
           The faster SCI protocol is also supported, but requires
           special hardware. See
-          <xref linkend="mysql-cluster-interconnects"/> for more
+          <xref linkend="mysql-cluster-interconnects"/>, for more
           information about SCI.
         </para>
       </listitem>
@@ -9876,7 +9876,7 @@
           server has NDB support using either of the commands
           <literal>SHOW VARIABLES LIKE 'have_%';</literal> or
           <literal>SHOW ENGINES;</literal>. (See
-          <xref linkend="mysqld-max"/> for more information.)
+          <xref linkend="mysqld-max"/>, for more information.)
         </para>
 
         <para>
@@ -9928,7 +9928,7 @@
           To calculate the memory requirements more exactly requires
           determining, for each table in the cluster database, the
           storage space required per row (see
-          <xref linkend="storage-requirements"/> for details), and
+          <xref linkend="storage-requirements"/>, for details), and
           multiplying this by the number of rows. You must also remember
           to account for any column indexes as follows:
         </para>
@@ -10164,7 +10164,7 @@
 
           <listitem>
             <para>
-              <xref linkend="spatial-extensions"/> are not supported.
+              <xref linkend="spatial-extensions"/>, are not supported.
             </para>
           </listitem>
 
@@ -10235,7 +10235,7 @@
           convert existing tables using other storage engines to
           <literal>NDB Cluster</literal> using <literal>ALTER
           TABLE</literal>, but requires an additional workaround; see
-          <xref linkend="mysql-cluster-limitations"/> for details.
+          <xref linkend="mysql-cluster-limitations"/>, for details.
         </para>
       </listitem>
 
@@ -10253,7 +10253,7 @@
           high-speed (1 gigabit per second and higher),
           high-availability protocol used in building scalable
           multi-processor systems; it requires special hardware and
-          drivers. See <xref linkend="mysql-cluster-interconnects"/> for
+          drivers. See <xref linkend="mysql-cluster-interconnects"/>, for
           more about using SCI as a transport mechanism in MySQL
           Cluster.
         </para>
@@ -10306,7 +10306,7 @@
           remaining set to shut down. Arbitrator selection is controlled
           by the <literal>ArbitrationRank</literal> configuration
           parameter for MySQL Server and management server nodes. (See
-          <xref linkend="mysql-cluster-mgm-definition"/> for details.)
+          <xref linkend="mysql-cluster-mgm-definition"/>, for details.)
           It should also be noted that the role of arbitrator does not
           in and of itself impose any heavy demands upon the host so
           designated, and thus the arbitrator host does not need to be
@@ -10338,7 +10338,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-cluster-limitations"/> for more
+          See <xref linkend="mysql-cluster-limitations"/>, for more
           information about these issues.
         </para>
       </listitem>
@@ -10418,7 +10418,7 @@
 
         <para>
           For more information, see
-          <xref linkend="mgm-client-commands"/> and
+          <xref linkend="mgm-client-commands"/>, and
           <xref linkend="multi-shutdown-restart"/>.
         </para>
       </listitem>
@@ -10566,7 +10566,7 @@
           Text files containing directives and information regarding the
           cluster, its hosts, and its nodes. These are read by the
           cluster's management nodes when the cluster is started. See
-          <xref linkend="mysql-cluster-config-file"/> for details.
+          <xref linkend="mysql-cluster-config-file"/>, for details.
         </para>
       </listitem>
 

Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/optimization.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -174,7 +174,7 @@
 
       <para>
         For more information about this, see
-        <xref linkend="constraints"/> and <xref linkend="insert"/> or
+        <xref linkend="constraints"/>, and <xref linkend="insert"/>, or
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -1304,7 +1304,7 @@
             optimizer choose better indexes. For
             <literal>MyISAM</literal> tables, <command>myisamchk
             --analyze</command> does the same. See
-            <xref linkend="analyze-table"/> and
+            <xref linkend="analyze-table"/>, and
             <xref linkend="table-maintenance"/>.
           </para>
         </listitem>
@@ -1431,7 +1431,7 @@
                 use a <literal>range</literal> or
                 <literal>index_merge</literal> access method to retrieve
                 rows. The applicability criteria are as described in
-                <xref linkend="range-optimization"/> and
+                <xref linkend="range-optimization"/>, and
                 <xref linkend="index-merge-optimization"/>, with the
                 exception that all column values for the preceding table
                 are known and considered to be constants.
@@ -1521,7 +1521,7 @@
               <para>
                 These indicate how index scans are merged for the
                 <literal>index_merge</literal> join type. See
-                <xref linkend="index-merge-optimization"/> for more
+                <xref linkend="index-merge-optimization"/>, for more
                 information.
               </para>
             </listitem>
@@ -2072,7 +2072,7 @@
         tables should usually be done with indexes. You can use the
         <literal>EXPLAIN</literal> statement to determine which indexes
         are used for a <literal>SELECT</literal>. See
-        <xref linkend="mysql-indexes"/> and <xref linkend="explain"/>.
+        <xref linkend="mysql-indexes"/>, and <xref linkend="explain"/>.
       </para>
 
       <para>
@@ -2721,7 +2721,7 @@
             </para>
 
             <para>
-              See <xref linkend="range-access-single-part"/> for the
+              See <xref linkend="range-access-single-part"/>, for the
               definition of what is considered to be a constant.
             </para>
 
@@ -2848,7 +2848,7 @@
         </itemizedlist>
 
         <para>
-          <xref linkend="range-access-single-part"/> describes how
+          <xref linkend="range-access-single-part"/>, describes how
           optimizations are performed to combine or eliminate intervals
           for range conditions on single-part index. Analogous steps are
           performed for range conditions on multiple-part keys.
@@ -4766,7 +4766,7 @@
           clause, a loose index scan reads as many keys as the number of
           groups, which may be a much smaller number than that of all
           keys. If the <literal>WHERE</literal> clause contains range
-          predicates (see the discussion in <xref linkend="explain"/> of
+          predicates (see the discussion in <xref linkend="explain"/>, of
           the <literal>range</literal> join type), a loose index scan
           looks up the first key of each group that satisfies the range
           conditions, and again reads the least possible number of keys.
@@ -5718,8 +5718,8 @@
           <para>
             Stored procedures or UDFs (user-defined functions) may be a
             good way to gain performance for some tasks. See
-            <xref linkend="stored-procedures"/> and
-            <xref linkend="adding-functions"/> for more information
+            <xref linkend="stored-procedures"/>, and
+            <xref linkend="adding-functions"/>, for more information
             about these.
           </para>
         </listitem>
@@ -6488,7 +6488,7 @@
             If you encounter speed problems with table locks in MySQL,
             you may be able to improve performance by converting some of
             your tables to <literal>InnoDB</literal> or
-            <literal>BDB</literal> tables. See <xref linkend="innodb"/>
+            <literal>BDB</literal> tables. See <xref linkend="innodb"/>,
             and <xref linkend="bdb-storage-engine"/>.
           </para>
         </listitem>
@@ -6858,7 +6858,7 @@
         <literal>CHAR</literal>, <literal>VARCHAR</literal>, and
         <literal>TEXT</literal> columns. Indexing always takes place
         over the entire column and partial (prefix) indexing is not
-        supported. See <xref linkend="fulltext-search"/> for details.
+        supported. See <xref linkend="fulltext-search"/>, for details.
       </para>
 
       <para>
@@ -7600,7 +7600,7 @@
           <literal>keycache1.key_buffer_size</literal>,
           <literal>keycache1</literal> is the cache variable name and
           <literal>key_buffer_size</literal> is the cache component. See
-          <xref linkend="structured-system-variables"/> for a
+          <xref linkend="structured-system-variables"/>, for a
           description of the syntax used for referring to structured key
           cache system variables.
         </para>
@@ -8438,7 +8438,7 @@
         If the value is very large, even when you have not issued many
         <literal>FLUSH TABLES</literal> statements, you should increase
         the table cache size. See
-        <xref linkend="server-system-variables"/> and
+        <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 
@@ -8768,7 +8768,7 @@
 
       <para>
         You can find a full description for all system and status
-        variables in <xref linkend="server-system-variables"/> and
+        variables in <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/problems.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -3634,7 +3634,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="working-with-null"/> for additional
+        See <xref linkend="working-with-null"/>, for additional
         information and examples.
       </para>
 
@@ -3809,7 +3809,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="show-table-status"/> and
+        See <xref linkend="show-table-status"/>, and
         <xref linkend="show-create-table"/>.
       </para>
 
@@ -3840,7 +3840,7 @@
       </para>
 
       <para>
-        See <xref linkend="show-engines"/> and
+        See <xref linkend="show-engines"/>, and
         <xref linkend="show-variables"/>.
       </para>
 
@@ -4547,7 +4547,7 @@
         <listitem>
           <para>
             There are known issues in using temporary tables with
-            replication. See <xref linkend="replication-features"/> for 
+            replication. See <xref linkend="replication-features"/>, for 
             more information.
           </para>
         </listitem>
@@ -4589,7 +4589,7 @@
     <para>
       For information about platform-specific issues, see the
       installation and porting instructions in
-      <xref linkend="operating-system-specific-notes"/> and
+      <xref linkend="operating-system-specific-notes"/>, and
       <xref linkend="porting"/>.
     </para>
 

Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/replication.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -710,7 +710,7 @@
         <filename>relay-log.info</filename> by default. They contain
         information like that shown in the output of the <literal>SHOW
         SLAVE STATUS</literal> statement (see
-        <xref linkend="replication-slave-sql"/> for a description of
+        <xref linkend="replication-slave-sql"/>, for a description of
         this statement). As disk files, they survive a slave server's
         shutdown. The next time the slave starts up, it reads these
         files to determine how far it has proceeded in reading binary
@@ -895,7 +895,7 @@
     <para>
       If you want to administer a MySQL replication setup, we suggest
       that you read this entire chapter through and try all statements
-      mentioned in <xref linkend="replication-master-sql"/> and
+      mentioned in <xref linkend="replication-master-sql"/>, and
       <xref linkend="replication-slave-sql"/>. You should also
       familiarize yourself with replication startup options described in
       <xref linkend="replication-options"/>.
@@ -1367,7 +1367,7 @@
       <emphasis role="bold">Note</emphasis>: The content of
       <filename>master.info</filename> overrides some of the options
       specified on the command line or in <filename>my.cnf</filename>.
-      See <xref linkend="replication-options"/> for more details.
+      See <xref linkend="replication-options"/>, for more details.
     </para>
 
     <para>
@@ -1862,7 +1862,7 @@
           <literal>MEMORY</literal> table after startup, it notifies the
           slaves that the table needs to be emptied by writing a
           <literal>DELETE FROM</literal> statement for that table to the
-          binary log. See <xref linkend="memory-storage-engine"/> for
+          binary log. See <xref linkend="memory-storage-engine"/>, for
           more information.
         </para>
       </listitem>
@@ -4068,7 +4068,7 @@
           it is a bug or you have encountered one of the known
           replication limitations described in
           <xref linkend="replication-features"/>. If it is a bug, see
-          <xref linkend="replication-bugs"/> for instructions on how to
+          <xref linkend="replication-bugs"/>, for instructions on how to
           report it.
         </para>
       </listitem>

Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/sql-syntax.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1983,7 +1983,7 @@
             <literal>VARCHAR</literal>, and <literal>TEXT</literal>
             columns. Indexing always happens over the entire column;
             partial indexing is not supported and any prefix length is
-            ignored if specified. See <xref linkend="fulltext-search"/>
+            ignored if specified. See <xref linkend="fulltext-search"/>,
             for details of operation.
           </para>
         </listitem>
@@ -2507,7 +2507,7 @@
             <option>--skip-symbolic-links</option> option. Your
             operating system must also have a working, thread-safe
             <literal>realpath()</literal> call. See
-            <xref linkend="symbolic-links-to-tables"/> for more complete
+            <xref linkend="symbolic-links-to-tables"/>, for more complete
             information.
           </para>
         </listitem>
@@ -3380,7 +3380,7 @@
         <command>myisamchk</command> utility to reorganize tables.
         <literal>OPTIMIZE TABLE</literal> is easier, but
         <command>myisamchk</command> is faster. See
-        <xref linkend="optimize-table"/> and
+        <xref linkend="optimize-table"/>, and
         <xref linkend="optimization"/>.
       </para>
 
@@ -4219,7 +4219,7 @@
         behave identically. The behavior of <literal>INSERT</literal>
         statements with respect to <literal>AUTO_INCREMENT</literal>
         columns is discussed further in
-        <xref linkend="information-functions"/> and
+        <xref linkend="information-functions"/>, and
         <xref linkend="mysql-insert-id"/>.
       </para>
 
@@ -6049,7 +6049,7 @@
       <para>
         <literal>SELECT</literal> is used to retrieve rows selected from
         one or more tables, and can include <literal>UNION</literal>
-        statements and subqueries. See <xref linkend="union"/> and
+        statements and subqueries. See <xref linkend="union"/>, and
         <xref linkend="subqueries"/>.
       </para>
 
@@ -6257,7 +6257,7 @@
             or
             <replaceable>db_name</replaceable>.<replaceable>tbl_name</replaceable>
             prefix for a column reference unless the reference would be
-            ambiguous. See <xref linkend="legal-names"/> for examples of
+            ambiguous. See <xref linkend="legal-names"/>, for examples of
             ambiguity that require the more explicit column reference
             forms.
           </para>
@@ -12399,8 +12399,8 @@
               columns are set to their implicit default values if strict
               SQL mode is not enabled. In strict mode, the statement is
               rejected if any of the omitted columns have no default
-              value. <xref linkend="server-sql-mode"/> discusses strict
-              mode. <xref linkend="create-table"/> discusses implicit
+              value. <xref linkend="server-sql-mode"/>, discusses strict
+              mode. <xref linkend="create-table"/>, discusses implicit
               default values.
             </para>
 
@@ -12558,7 +12558,7 @@
           to a MySQL 4.1 or later server using a pre-4.1 client program,
           do not use the preceding <literal>SET PASSWORD</literal> or
           <literal>UPDATE</literal> statement without reading
-          <xref linkend="password-hashing"/> first. The password format
+          <xref linkend="password-hashing"/>, first. The password format
           changed in MySQL 4.1, and under certain circumstances it is
           possible that if you change your password, you might not be
           able to connect to the server afterward.
@@ -16680,7 +16680,7 @@
           these variables using command-line options when
           <command>mysqld</command> starts or at runtime with the
           <literal>SET</literal> statement. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="set-option"/>.
         </para>
 
@@ -17314,7 +17314,7 @@
         </para>
 
         <para>
-          See also <xref linkend="reset"/> for information about how the
+          See also <xref linkend="reset"/>, for information about how the
           <literal>RESET</literal> statement is used with replication.
         </para>
 
@@ -17670,7 +17670,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing master replication
-        servers. <xref linkend="replication-slave-sql"/> discusses
+        servers. <xref linkend="replication-slave-sql"/>, discusses
         statements for managing slave servers.
       </para>
 
@@ -17931,7 +17931,7 @@
         <para>
           Lists the binary log files on the server. This statement is
           used as part of the procedure described in
-          <xref linkend="purge-master-logs"/> for determining which logs
+          <xref linkend="purge-master-logs"/>, for determining which logs
           can be purged.
         </para>
 
@@ -18061,7 +18061,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing slave replication
-        servers. <xref linkend="replication-master-sql"/> discusses
+        servers. <xref linkend="replication-master-sql"/>, discusses
         statements for managing master servers.
       </para>
 
@@ -18480,7 +18480,7 @@
           This is actually a function, not a statement. It is used to
           ensure that the slave has read and executed events up to a
           given position in the master's binary log. See
-          <xref linkend="miscellaneous-functions"/> for a full
+          <xref linkend="miscellaneous-functions"/>, for a full
           description.
         </para>
 

Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/storage-engines.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -303,7 +303,7 @@
 </programlisting>
 
   <para>
-    See <xref linkend="create-table"/> and
+    See <xref linkend="create-table"/>, and
     <xref linkend="alter-table"/>.
   </para>
 
@@ -1454,7 +1454,7 @@
           corruption is a result of the server dying. Otherwise,
           corruption may have occurred during normal operation. This is
           a bug. You should try to create a reproducible test case that
-          demonstrates the problem. See <xref linkend="crashing"/> and
+          demonstrates the problem. See <xref linkend="crashing"/>, and
           <xref linkend="reproduceable-test-case"/>.
         </para>
 
@@ -1576,7 +1576,7 @@
             <para>
               In general, it is a bad idea to share a data directory
               among multiple servers. See
-              <xref linkend="multiple-servers"/> for additional
+              <xref linkend="multiple-servers"/>, for additional
               discussion.
             </para>
           </listitem>
@@ -1924,7 +1924,7 @@
           used up does the storage engine need to read the next key
           block. This makes <literal>MERGE</literal> keys much slower on
           <literal>eq_ref</literal> searches, but not much slower on
-          <literal>ref</literal> searches. See <xref linkend="explain"/>
+          <literal>ref</literal> searches. See <xref linkend="explain"/>,
           for more information about <literal>eq_ref</literal> and
           <literal>ref</literal>.
         </para>
@@ -2315,7 +2315,7 @@
           statements such as <literal>INSERT INTO ... SELECT</literal>
           or <literal>LOAD DATA INFILE</literal> into this file in order
           to load the table from a persistent data source. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="load-data"/>.
         </para>
       </listitem>
@@ -2978,7 +2978,7 @@
             unexpectedly. It should not be fatal even if this number is
             not 100% correct. You can update the row count by using
             <literal>ANALYZE TABLE</literal> or <literal>OPTIMIZE
-            TABLE</literal>. See <xref linkend="analyze-table"/> and
+            TABLE</literal>. See <xref linkend="analyze-table"/>, and
             <xref linkend="optimize-table"/>.
           </para>
         </listitem>

Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/stored-procedures.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -349,8 +349,8 @@
         Compound statements can contain declarations, loops, and other
         control structure statements. The syntax for these statements is
         described later in this chapter. See, for example,
-        <xref linkend="declare"/> and
-        <xref linkend="flow-control-constructs"/>
+        <xref linkend="declare"/>, and
+        <xref linkend="flow-control-constructs"/>.
       </para>
 
       <remark role="help-description-end"/>

Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/triggers.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -517,7 +517,7 @@
       or newer, you must drop all triggers <emphasis>before
       upgrading</emphasis> and re-create them afterwards, or else
       <literal>DROP TRIGGER</literal> does not work after the upgrade.
-      See <xref linkend="upgrading-from-4-1"/> for a suggested upgrade
+      See <xref linkend="upgrading-from-4-1"/>, for a suggested upgrade
       procedure.
     </para>
 
@@ -555,7 +555,7 @@
       To create a trigger or drop a trigger, use the <literal>CREATE
       TRIGGER</literal> or <literal>DROP TRIGGER</literal> statement.
       The syntax for these statements is described in
-      <xref linkend="create-trigger"/> and
+      <xref linkend="create-trigger"/>, and
       <xref linkend="drop-trigger"/>.
     </para>
 

Modified: trunk/refman-5.0/tutorial.xml
===================================================================
--- trunk/refman-5.0/tutorial.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.0/tutorial.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1150,7 +1150,7 @@
       <para>
         If the statement fails, it is likely that your MySQL
         installation does not have local file capability enabled by
-        default. See <xref linkend="load-data-local"/> for information
+        default. See <xref linkend="load-data-local"/>, for information
         on how to change this.
       </para>
 
@@ -2302,7 +2302,7 @@
 </programlisting>
 
         <para>
-          <xref linkend="regexp"/> provides more information about the
+          <xref linkend="regexp"/>, provides more information about the
           syntax for regular expressions.
         </para>
 
@@ -3742,7 +3742,7 @@
           <listitem>
             <para>
               How to assign the <literal>AUTO_INCREMENT</literal>
-              attribute to a column: <xref linkend="create-table"/> and
+              attribute to a column: <xref linkend="create-table"/>, and
               <xref linkend="alter-table"/>.
             </para>
           </listitem>

Modified: trunk/refman-5.1/apis.xml
===================================================================
--- trunk/refman-5.1/apis.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/apis.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -307,7 +307,7 @@
         program, use the <option>--defaults-file</option> option as one
         of the elements of the second argument of the
         <literal>mysql_server_init()</literal> function. See
-        <xref linkend="mysql-server-init"/> for more information on the
+        <xref linkend="mysql-server-init"/>, for more information on the
         <literal>mysql_server_init()</literal> function.
       </para>
 
@@ -4579,7 +4579,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -4608,7 +4608,7 @@
         </para>
 
         <para>
-          See <xref linkend="c-api-function-overview"/> for usage
+          See <xref linkend="c-api-function-overview"/>, for usage
           information.
         </para>
 
@@ -9078,7 +9078,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-affected-rows"/> for additional
+          See <xref linkend="mysql-affected-rows"/>, for additional
           information on the return value.
         </para>
 
@@ -9133,7 +9133,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-stmt-attr-set"/> for a list of
+          See <xref linkend="mysql-stmt-attr-set"/>, for a list of
           options and option types.
         </para>
 
@@ -10765,7 +10765,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-insert-id"/> for more information.
+          See <xref linkend="mysql-insert-id"/>, for more information.
         </para>
 
         <para>
@@ -13008,7 +13008,7 @@
             downgrade to MySQL 4.0; switch to PHP 5 and the newer
             <literal>mysqli</literal> extension; or configure the MySQL
             server with <option>--old-passwords</option>. (See
-            <xref linkend="old-client"/> for more information.)
+            <xref linkend="old-client"/>, for more information.)
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/client-side-scripts.xml
===================================================================
--- trunk/refman-5.1/client-side-scripts.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/client-side-scripts.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -29,7 +29,7 @@
     This chapter provides a brief overview of these programs and then a
     more detailed description of each one. The descriptions indicate how
     to invoke the programs and the options they understand. See
-    <xref linkend="using-mysql-programs"/> for general information on
+    <xref linkend="using-mysql-programs"/>, for general information on
     invoking programs and specifying program options.
   </para>
 
@@ -1401,7 +1401,7 @@
             <para>
               Execute the statement and quit. The default output format
               is like that produced with <option>--batch</option>. See
-              <xref linkend="command-line-options"/> for some examples.
+              <xref linkend="command-line-options"/>, for some examples.
             </para>
           </listitem>
 
@@ -1779,7 +1779,7 @@
               affect using key values. If you have set this option in an
               option file, you can override it by using
               <option>--safe-updates</option> on the command line. See
-              <xref linkend="mysql-tips"/> for more information about
+              <xref linkend="mysql-tips"/>, for more information about
               this option.
             </para>
           </listitem>

Modified: trunk/refman-5.1/connector-odbc.xml
===================================================================
--- trunk/refman-5.1/connector-odbc.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/connector-odbc.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1004,7 +1004,7 @@
 </programlisting>
 
       <para>
-        Then proceed on to <xref linkend="dsn-on-unix"/> to configure
+        Then proceed on to <xref linkend="dsn-on-unix"/>, to configure
         the DSN for MyODBC. For more information, refer to the
         <filename>INSTALL-BINARY</filename> file that comes with your
         distribution.
@@ -1950,7 +1950,7 @@
 
       <listitem>
         <para>
-          See <xref linkend="installing-source-tree"/> for instructions
+          See <xref linkend="installing-source-tree"/>, for instructions
           on how to download and install BitKeeper.
         </para>
       </listitem>
@@ -2376,7 +2376,7 @@
         The DSN configuration dialog also has an
         <literal>Options</literal> button. If you select it, the
         following options dialog appears displaying that control driver
-        behavior. Refer to <xref linkend="connection-parameters"/> for
+        behavior. Refer to <xref linkend="connection-parameters"/>, for
         information about the meaning of these options.
       </para>
 
@@ -5017,7 +5017,7 @@
 
       <para>
         A simple examples for the usage of ADO, DAO and RDO with VB can
-        be found her:
+        be found here:
       </para>
 
       <itemizedlist>
@@ -5402,13 +5402,13 @@
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-c-sharp-cp"/>
+            See <xref linkend="odbc-net-op-c-sharp-cp"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            See <xref linkend="odbc-net-op-vb-cp"/>
+            See <xref linkend="odbc-net-op-vb-cp"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/data-types.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -2136,7 +2136,7 @@
       strict mode, these statements fail, and some or all of the values
       will not be inserted or changed, depending on whether the table is
       a transactional table and other factors. See
-      <xref linkend="server-sql-mode"/> for details.
+      <xref linkend="server-sql-mode"/>, for details.
     </para>
 
   </section>
@@ -2656,7 +2656,7 @@
             With strict mode enabled, invalid dates generate an error.
             To allow such dates, enable
             <literal>ALLOW_INVALID_DATES</literal>. See
-            <xref linkend="server-sql-mode"/> for more information.
+            <xref linkend="server-sql-mode"/>, for more information.
           </para>
         </listitem>
 
@@ -4505,7 +4505,7 @@
       data types, the record format is also variable length. When a
       table is created, MySQL may, under certain conditions, change a
       column from a variable-length type to a fixed-length type or vice
-      versa. See <xref linkend="silent-column-changes"/> for more
+      versa. See <xref linkend="silent-column-changes"/>, for more
       information.
     </para>
 

Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/database-administration.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -305,7 +305,7 @@
             server named <command>mysqld-max</command>. The
             <literal>MySQL-Max</literal> RPM presupposes that you have
             installed the regular server RPM. See
-            <xref linkend="linux-rpm"/> for more information on the
+            <xref linkend="linux-rpm"/>, for more information on the
             Linux RPM packages.
           </para>
         </listitem>
@@ -1280,7 +1280,7 @@
             the <command>mysql.server</command> script will be installed
             in the <filename>/etc/init.d</filename> directory with the
             name <filename>mysql</filename>. You need not install it
-            manually. See <xref linkend="linux-rpm"/> for more
+            manually. See <xref linkend="linux-rpm"/>, for more
             information on the Linux RPM packages.
           </para>
 
@@ -3375,7 +3375,7 @@
               The binary log file. Log all queries that change data to
               this file. Used for backup and replication. See
               <xref linkend="binary-log"/>. It is recommended to specify
-              a filename (see <xref linkend="open-bugs"/> for the
+              a filename (see <xref linkend="open-bugs"/>, for the
               reason) otherwise MySQL uses
               <filename><replaceable>host_name</replaceable>-bin</filename>
               as the log file basename.
@@ -3648,7 +3648,7 @@
               is possible to point out the management server that
               distributes the cluster configuration by setting the
               connect string option. See
-              <xref linkend="mysql-cluster-connectstring"/> for syntax.
+              <xref linkend="mysql-cluster-connectstring"/>, for syntax.
             </para>
           </listitem>
 
@@ -3927,7 +3927,7 @@
               resources for this storage engine only if
               <option>--skip-ndbcluster</option> is explicitly
               overridden using the <option>--ndbcluster</option> option.
-              See <xref linkend="mysql-cluster-quick"/> for an example
+              See <xref linkend="mysql-cluster-quick"/>, for an example
               of usage.
             </para>
           </listitem>
@@ -5218,7 +5218,7 @@
         <para>
           You can view system variables and their values by using the
           <literal>SHOW VARIABLES</literal> statement. See
-          <xref linkend="system-variables"/> for more information.
+          <xref linkend="system-variables"/>, for more information.
         </para>
 
 <programlisting>
@@ -6263,7 +6263,7 @@
               <literal>MyISAM</literal> tables by starting the server
               with the <option>--myisam-recover</option> option (for
               example, <option>--myisam-recover=BACKUP,FORCE</option>).
-              See <xref linkend="server-options"/> and
+              See <xref linkend="server-options"/>, and
               <xref linkend="myisam-start"/>.
             </para>
 
@@ -7361,7 +7361,7 @@
               The number of simultaneous client connections allowed.
               Increasing this value increases the number of file
               descriptors that <command>mysqld</command> requires. See
-              <xref linkend="table-cache"/> for comments on file
+              <xref linkend="table-cache"/>, for comments on file
               descriptor limits. Also see
               <xref linkend="too-many-connections"/>.
             </para>
@@ -7988,7 +7988,7 @@
               The default value is 0, which disables the query cache.
               Note that this amount of memory is allocated even if
               <literal>query_cache_type</literal> is set to 0. See
-              <xref linkend="query-cache-configuration"/> for more
+              <xref linkend="query-cache-configuration"/>, for more
               information.
             </para>
           </listitem>
@@ -8552,7 +8552,7 @@
               implementation.) By examining the difference between the
               <literal>Connections</literal> and
               <literal>Threads_created</literal> status variables (see
-              <xref linkend="server-status-variables"/> for details) you
+              <xref linkend="server-status-variables"/>, for details) you
               can see how efficient the thread cache is.
             </para>
           </listitem>
@@ -11783,7 +11783,7 @@
         algorithm is not as strong as the newer algorithm; with some
         effort a clever attacker who can sniff the traffic between the
         client and the server can crack the password. (See
-        <xref linkend="password-hashing"/> for a discussion of the
+        <xref linkend="password-hashing"/>, for a discussion of the
         different password handling methods.) If the connection between
         the client and the server goes through an untrusted network, you
         should use an SSH tunnel to encrypt the communication.
@@ -12433,7 +12433,7 @@
         If your privileges are changed (either by yourself or someone
         else) while you are connected, those changes do not necessarily
         take effect immediately for the next statement you issue. See
-        <xref linkend="privilege-changes"/> for details.
+        <xref linkend="privilege-changes"/>, for details.
       </para>
 
       <para>
@@ -14958,7 +14958,7 @@
 
           <para>
             For information on how to deal with this, see
-            <xref linkend="password-hashing"/> and
+            <xref linkend="password-hashing"/>, and
             <xref linkend="old-client"/>.
           </para>
         </listitem>
@@ -15095,9 +15095,8 @@
             statements, or the <command>mysqladmin password</command>
             command, all of which automatically use
             <literal>PASSWORD()</literal> to encrypt the password. See
-            <xref linkend="passwords"/> and
-            <xref
-              linkend="create-user"/>.
+            <xref linkend="passwords"/>, and
+            <xref linkend="create-user"/>.
           </para>
         </listitem>
 
@@ -17339,7 +17338,7 @@
 </programlisting>
 
           <para>
-            <xref linkend="option-files"/> discusses option files in
+            <xref linkend="option-files"/>, discusses option files in
             more detail.
           </para>
         </listitem>
@@ -18358,7 +18357,7 @@
         backup. To get a consistent backup, do a <literal>LOCK
         TABLES</literal> on the relevant tables, followed by
         <literal>FLUSH TABLES</literal> for the tables. See
-        <xref linkend="lock-tables"/> and <xref linkend="flush"/>. You
+        <xref linkend="lock-tables"/>, and <xref linkend="flush"/>. You
         need only a read lock; this allows other clients to continue to
         query the tables while you are making a copy of the files in the
         database directory. The <literal>FLUSH TABLES</literal>
@@ -18373,14 +18372,14 @@
         the output file cannot previously exist. This is also true of
         <literal>BACKUP TABLE</literal>, since allowing extant files to
         be overwritten would constitute a security risk. See
-        <xref linkend="select"/> and <xref linkend="backup-table"/>.
+        <xref linkend="select"/>, and <xref linkend="backup-table"/>.
       </para>
 
       <para>
         Another technique for backing up a database is to use the
         <command>mysqldump</command> program or the
         <command>mysqlhotcopy script</command>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <orderedlist>
@@ -18437,7 +18436,7 @@
       <para>
         For <literal>InnoDB</literal> tables, it's possible to perform
         an online backup that takes no locks on tables; see
-        <xref linkend="mysqldump"/>
+        <xref linkend="mysqldump"/>.
       </para>
 
       <para>
@@ -18455,7 +18454,7 @@
         should also rotate the binary log using <literal>FLUSH
         LOGS</literal>, <literal>mysqldump --flush-logs</literal>, or
         <literal>mysqlhotcopy --flushlogs</literal>. See
-        <xref linkend="mysqldump"/> and <xref linkend="mysqlhotcopy"/>.
+        <xref linkend="mysqldump"/>, and <xref linkend="mysqlhotcopy"/>.
       </para>
 
       <para>
@@ -18510,7 +18509,7 @@
             logs, from certain positions (usually you want to re-run all
             binary logs from the date of the restored backup, excepting
             possibly some incorrect queries). See
-            <xref linkend="mysqlbinlog"/> for more information on the
+            <xref linkend="mysqlbinlog"/>, for more information on the
             <command>mysqlbinlog</command> utility and how to use it.
           </para>
         </listitem>
@@ -19702,7 +19701,7 @@
             <literal>myisam_stats_method</literal> system variable. For
             more information, see the description of
             <literal>myisam_stats_method</literal> in
-            <xref linkend="server-system-variables"/> and
+            <xref linkend="server-system-variables"/>, and
             <xref linkend="myisam-index-statistics"/>.
           </para>
 
@@ -20657,7 +20656,7 @@
             <literal>CHECK TABLE</literal> and <literal>REPAIR
             TABLE</literal> statements to check and repair
             <literal>MyISAM</literal> tables. See
-            <xref linkend="check-table"/> and
+            <xref linkend="check-table"/>, and
             <xref linkend="repair-table"/>.
           </para>
 
@@ -21073,7 +21072,7 @@
         rather than waiting for problems to occur. One way to check and
         repair <literal>MyISAM</literal> tables is with the
         <literal>CHECK TABLE</literal> and <literal>REPAIR
-        TABLE</literal> statements. See <xref linkend="check-table"/>
+        TABLE</literal> statements. See <xref linkend="check-table"/>,
         and <xref linkend="repair-table"/>.
       </para>
 
@@ -23035,7 +23034,7 @@
         <literal>-bin</literal>. If file name is given, but it doesn't
         contain a path, the file is written in the data directory. It is
         recommended to specify a filename, see
-        <xref linkend="open-bugs"/> for the reason.
+        <xref linkend="open-bugs"/>, for the reason.
       </para>
 
       <para>
@@ -23072,7 +23071,7 @@
         You can delete all binary log files with the <literal>RESET
         MASTER</literal> statement, or only some of them with
         <literal>PURGE MASTER LOGS</literal>. See
-        <xref linkend="reset"/> and
+        <xref linkend="reset"/>, and
         <xref linkend="replication-master-sql"/>.
       </para>
 
@@ -23336,7 +23335,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysqlbinlog"/> for more information on the
+        See <xref linkend="mysqlbinlog"/>, for more information on the
         <command>mysqlbinlog</command> utility and how to use it.
       </para>
 
@@ -24397,7 +24396,7 @@
       </para>
 
       <para>
-        <xref linkend="environment-variables"/> includes a list of other
+        <xref linkend="environment-variables"/>, includes a list of other
         environment variables you can use to affect
         <command>mysqld</command>.
       </para>
@@ -24660,7 +24659,7 @@
 
       <para>
         This section describes how the query cache works when it is
-        operational. <xref linkend="query-cache-configuration"/>
+        operational. <xref linkend="query-cache-configuration"/>,
         describes how to control whether or not it is operational.
       </para>
 

Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/extending-mysql.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1106,7 +1106,7 @@
         is possible that server upgrades will require revisions to
         plugins that were originally written for older servers. For
         information about these constraints, see
-        <xref linkend="configure-options"/> and
+        <xref linkend="configure-options"/>, and
         <xref linkend="compilation-problems"/>.
       </para>
 
@@ -1668,7 +1668,7 @@
               of zero indicates no weight adjustment. Values greater
               than or less than zero mean higher or lower weight,
               respectively. The examples at
-              <xref linkend="fulltext-boolean"/> that use the
+              <xref linkend="fulltext-boolean"/>, that use the
               <literal>&lt;</literal> and <literal>&gt;</literal>
               operators illustrate how weighting works.
             </para>
@@ -2663,7 +2663,7 @@
         constraints may change in future versions of the server, so it
         is possible that server upgrades will require revisions to UDFs
         that were originally written for older servers. For information
-        about these constraints, see <xref linkend="configure-options"/>
+        about these constraints, see <xref linkend="configure-options"/>,
         and <xref linkend="compilation-problems"/>.
       </para>
 
@@ -2946,7 +2946,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create a simple UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 
@@ -3122,7 +3122,7 @@
         <para>
           This section describes the different functions that you need
           to define when you create an aggregate UDF.
-          <xref linkend="adding-udf"/> describes the order in which
+          <xref linkend="adding-udf"/>, describes the order in which
           MySQL calls these functions.
         </para>
 

Modified: trunk/refman-5.1/functions.xml
===================================================================
--- trunk/refman-5.1/functions.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/functions.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -5930,7 +5930,7 @@
     <para>
       This section describes the functions that can be used to
       manipulate temporal values. See
-      <xref linkend="date-and-time-types"/> for a description of the
+      <xref linkend="date-and-time-types"/>, for a description of the
       range of values each date and time type has and the valid formats
       in which values may be specified.
     </para>
@@ -6140,7 +6140,7 @@
           <emphasis role="bold">Note</emphasis>: To use named time zones
           such as <literal>'MET'</literal> or
           <literal>'Europe/Moscow'</literal>, the time zone tables must
-          be properly set up. See <xref linkend="time-zone-support"/>
+          be properly set up. See <xref linkend="time-zone-support"/>,
           for instructions.
         </para>
       </listitem>
@@ -8443,7 +8443,7 @@
         <para>
           For dates before 1582 (and possibly a later year in other
           locales), results from this function are not reliable. See
-          <xref linkend="mysql-calendar"/> for details.
+          <xref linkend="mysql-calendar"/>, for details.
         </para>
       </listitem>
 
@@ -9192,7 +9192,7 @@
     <para>
       It is also possible to perform a boolean search or a search with
       query expansion. These search types are described in
-      <xref linkend="fulltext-boolean"/> and
+      <xref linkend="fulltext-boolean"/>, and
       <xref linkend="fulltext-query-expansion"/>.
     </para>
 
@@ -13440,7 +13440,7 @@
             use only. The server uses it when writing statements from
             stored routines that contain references to local routine
             variables, as described in
-            <xref linkend="stored-procedure-logging"/> You might see
+            <xref linkend="stored-procedure-logging"/>, You might see
             this function in the output from
             <command>mysqlbinlog</command>.
           </para>

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/innodb.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -430,7 +430,7 @@
     </para>
 
     <para>
-      See <xref linkend="innodb-init"/> for an example of what the
+      See <xref linkend="innodb-init"/>, for an example of what the
       information displayed by <literal>InnoDB</literal> should look
       like.
     </para>
@@ -5251,7 +5251,7 @@
       would be good to throttle new row operations, and allocate more
       resources to the purge thread. The startup option and settable
       global variable <literal>innodb_max_purge_lag</literal> exists for
-      exactly this purpose. See <xref linkend="innodb-start"/> for more
+      exactly this purpose. See <xref linkend="innodb-start"/>, for more
       information.
     </para>
 

Modified: trunk/refman-5.1/language-structure.xml
===================================================================
--- trunk/refman-5.1/language-structure.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/language-structure.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1580,7 +1580,7 @@
 
     <para>
       Further information about system startup options and system
-      variables can be found in <xref linkend="server-options"/> and
+      variables can be found in <xref linkend="server-options"/>, and
       <xref linkend="server-system-variables"/>. A list of the variables
       that can be set at runtime is given in
       <xref linkend="dynamic-system-variables"/>.

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -605,7 +605,7 @@
       <para>
         It is also possible to use the high-speed Scalable Coherent
         Interface (SCI) with MySQL Cluster, but this is not a
-        requirement. See <xref linkend="mysql-cluster-interconnects"/>
+        requirement. See <xref linkend="mysql-cluster-interconnects"/>,
         for more about this protocol and its use with MySQL Cluster.
       </para>
 
@@ -647,7 +647,7 @@
         aware that you must install <emphasis>both</emphasis> the
         <literal>-server</literal> and <literal>-max</literal> packages
         on all machines that are to host cluster nodes. (See
-        <xref linkend="linux-rpm"/> for more information about
+        <xref linkend="linux-rpm"/>, for more information about
         installing MySQL using the RPMs.) After installing from RPM, you
         will still need to configure the cluster as discussed in
         <xref linkend="multi-config"/>.
@@ -992,7 +992,7 @@
       <para>
         For more detailed information about the available MySQL Cluster
         configuration parameters and their uses, see
-        <xref linkend="mysql-cluster-config-file"/> and
+        <xref linkend="mysql-cluster-config-file"/>, and
         <xref linkend="mysql-cluster-configuration"/>. For configuration
         of MySQL Cluster as relates to making backups, see
         <xref linkend="mysql-cluster-backup-configuration"/>.
@@ -1041,7 +1041,7 @@
             Note that <command>ndb_mgmd</command> must be told where to
             find its configuration file, using the <option>-f</option>
             or <option>--config-file</option> option. (See
-            <xref linkend="ndb-mgmd-process"/> for details.)
+            <xref linkend="ndb-mgmd-process"/>, for details.)
           </para>
         </listitem>
 
@@ -1122,7 +1122,7 @@
 
       <para>
         You should now be ready to work with databases, tables, and data
-        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>
+        in MySQL Cluster. See <xref linkend="multi-load-data-queries"/>,
         for a brief discussion.
       </para>
 
@@ -1621,7 +1621,7 @@
         In the next few sections, we assume that you are already
         familiar with installing MySQL, and here we cover only the
         differences between configuring MySQL Cluster and configuring
-        MySQL without clustering. (See <xref linkend="installing"/> if
+        MySQL without clustering. (See <xref linkend="installing"/>, if
         you require more information about the latter.)
       </para>
 
@@ -5374,7 +5374,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for more info
+        See <xref linkend="mysql-cluster-connectstring"/>, for more info
         on connectstrings.
       </para>
 
@@ -5544,7 +5544,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="mysql-cluster-connectstring"/> for additional
+        See <xref linkend="mysql-cluster-connectstring"/>, for additional
         information about this issue.
       </para>
 
@@ -5690,7 +5690,7 @@
 
       <para>
         Additional information about using <command>ndb_mgm</command>
-        can be found in <xref linkend="ndb-mgm-command-options"/> and
+        can be found in <xref linkend="ndb-mgm-command-options"/>, and
         <xref linkend="mgm-client-commands"/>.
       </para>
 
@@ -6093,7 +6093,7 @@
     <para>
       Managing a MySQL Cluster involves a number of tasks, the first of
       which is to configure and start MySQL Cluster. This is covered in
-      <xref linkend="mysql-cluster-configuration"/> and
+      <xref linkend="mysql-cluster-configuration"/>, and
       <xref linkend="mysql-cluster-process-management"/>.
     </para>
 
@@ -7906,7 +7906,7 @@
           shell using <command>ndb_mgm -e SHOW</command>). The switch
           <option>-c <replaceable>connectstring</replaceable></option>
           may be used to locate the MGM node (see
-          <xref linkend="mysql-cluster-connectstring"/> for information
+          <xref linkend="mysql-cluster-connectstring"/>, for information
           on connectstrings). The backup files must be present in the
           directory given as an argument to the restoration program.
         </para>
@@ -8207,7 +8207,7 @@
         Note that in many cases it is not possible to replicate to a slave
         running a version of MySQL with a lower version number than that
         of the master &mdash; see 
-        <xref linkend="replication-compatibility"/> for details.
+        <xref linkend="replication-compatibility"/>, for details.
       </para>
     
       <para>
@@ -8274,7 +8274,7 @@
       </itemizedlist>
       
       <para>
-        See <xref linkend="mysql-cluster-replication-schema-discovery"/>
+        See <xref linkend="mysql-cluster-replication-schema-discovery"/>,
         for more information about the first two items listed above, as
         well as some examples illustrating how to handle applicable
         situations.
@@ -8502,7 +8502,7 @@
   </programlisting>
         
           <para>
-            See <xref linkend="replication-options"/> for additional
+            See <xref linkend="replication-options"/>, for additional
             options that can be set in <filename>my.cnf</filename> for
             replication slaves.
           </para>
@@ -8513,7 +8513,7 @@
             <option>ndb-connectstring</option> option to the slave's
             <filename>my.cnf</filename> file prior to starting the
             replication process. See 
-            <xref linkend="mysql-cluster-replication-backups"/> for
+            <xref linkend="mysql-cluster-replication-backups"/>, for
             details.
           </para>
         </listitem>
@@ -8591,7 +8591,7 @@
             set either in the master server's <filename>my.cnf</filename>
             file, or on the command line when starting the master
             <command>mysqld</command> process. See 
-            <xref linkend="mysql-cluster-replication-starting"/> for
+            <xref linkend="mysql-cluster-replication-starting"/>, for
             information regarding the latter option.
           </para>
         </listitem>
@@ -8672,7 +8672,7 @@
             binary log from the log's starting point. Otherwise &mdash;
             that is, if you are loading data from the master using a
             backup mdash; see 
-            <xref linkend="mysql-cluster-replication-failover"/> for
+            <xref linkend="mysql-cluster-replication-failover"/>, for
             information on how to obtain the correct values to use for
             <literal>MASTER_LOG_FILE</literal> and
             <literal>MASTER_LOG_POS</literal> in such cases.
@@ -8946,7 +8946,7 @@
         This discussion discusses making beackups and restoring from them
         using MySQL Cluster replication. We assume that the replication
         servers have already been configured as covered previously (see 
-        <xref linkend="mysql-cluster-replication-preparation"/> and the
+        <xref linkend="mysql-cluster-replication-preparation"/>, and the
         sections immediately following). This having been done, the
         procedure for making a backup and then restoring from it is as
         follows: 
@@ -8984,7 +8984,7 @@
                 master cluster, and <replaceable>port</replaceable> is the
                 management server's port number. Note that the port number
                 needs to be specified only if the default port (1186) is
-                not being used. (See <xref linkend="multi-config"/> for
+                not being used. (See <xref linkend="multi-config"/>, for
                 more information about ports and port allocation in MySQL
                 Cluster.)
               </para>
@@ -10618,7 +10618,7 @@
               <literal>READ_COMMITTED</literal>,
               <literal>REPEATABLE_READ</literal>, and
               <literal>SERIALIZABLE</literal>.) See
-              <xref linkend="mysql-cluster-backup-troubleshooting"/> for
+              <xref linkend="mysql-cluster-backup-troubleshooting"/>, for
               information on how this can effect backup and restore of
               Cluster databases.
             </para>
@@ -10941,7 +10941,7 @@
         <listitem>
           <para>
             <emphasis role="bold">Query Cache Enabled for MySQL
-            Cluster</emphasis>: See <xref linkend="query-cache"/> for
+            Cluster</emphasis>: See <xref linkend="query-cache"/>, for
             information on configuring ans using the query cache.
           </para>
         </listitem>
@@ -11141,7 +11141,7 @@
         <para>
           The faster SCI protocol is also supported, but requires
           special hardware. See
-          <xref linkend="mysql-cluster-interconnects"/> for more
+          <xref linkend="mysql-cluster-interconnects"/>, for more
           information about SCI.
         </para>
       </listitem>
@@ -11456,7 +11456,7 @@
           server has NDB support using either of the commands
           <literal>SHOW VARIABLES LIKE 'have_%';</literal> or
           <literal>SHOW ENGINES;</literal>. (See
-          <xref linkend="mysqld-max"/> for more information.)
+          <xref linkend="mysqld-max"/>, for more information.)
         </para>
 
         <para>
@@ -11508,7 +11508,7 @@
           To calculate the memory requirements more exactly requires
           determining, for each table in the cluster database, the
           storage space required per row (see
-          <xref linkend="storage-requirements"/> for details), and
+          <xref linkend="storage-requirements"/>, for details), and
           multiplying this by the number of rows. You must also remember
           to account for any column indexes as follows:
         </para>
@@ -11744,7 +11744,7 @@
 
           <listitem>
             <para>
-              <xref linkend="spatial-extensions"/> are not supported.
+              <xref linkend="spatial-extensions"/>, are not supported.
             </para>
           </listitem>
 
@@ -11815,7 +11815,7 @@
           convert existing tables using other storage engines to
           <literal>NDB Cluster</literal> using <literal>ALTER
           TABLE</literal>, but requires an additional workaround; see
-          <xref linkend="mysql-cluster-limitations"/> for details.
+          <xref linkend="mysql-cluster-limitations"/>, for details.
         </para>
       </listitem>
 
@@ -11833,7 +11833,7 @@
           high-speed (1 gigabit per second and higher),
           high-availability protocol used in building scalable
           multi-processor systems; it requires special hardware and
-          drivers. See <xref linkend="mysql-cluster-interconnects"/> for
+          drivers. See <xref linkend="mysql-cluster-interconnects"/>, for
           more about using SCI as a transport mechanism in MySQL
           Cluster.
         </para>
@@ -11886,7 +11886,7 @@
           remaining set to shut down. Arbitrator selection is controlled
           by the <literal>ArbitrationRank</literal> configuration
           parameter for MySQL Server and management server nodes. (See
-          <xref linkend="mysql-cluster-mgm-definition"/> for details.)
+          <xref linkend="mysql-cluster-mgm-definition"/>, for details.)
           It should also be noted that the role of arbitrator does not
           in and of itself impose any heavy demands upon the host so
           designated, and thus the arbitrator host does not need to be
@@ -11918,7 +11918,7 @@
         </para>
 
         <para>
-          See <xref linkend="mysql-cluster-limitations"/> for more
+          See <xref linkend="mysql-cluster-limitations"/>, for more
           information about these issues.
         </para>
       </listitem>
@@ -11998,7 +11998,7 @@
 
         <para>
           For more information, see
-          <xref linkend="mgm-client-commands"/> and
+          <xref linkend="mgm-client-commands"/>, and
           <xref linkend="multi-shutdown-restart"/>.
         </para>
       </listitem>
@@ -12146,7 +12146,7 @@
           Text files containing directives and information regarding the
           cluster, its hosts, and its nodes. These are read by the
           cluster's management nodes when the cluster is started. See
-          <xref linkend="mysql-cluster-config-file"/> for details.
+          <xref linkend="mysql-cluster-config-file"/>, for details.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/optimization.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -174,7 +174,7 @@
 
       <para>
         For more information about this, see
-        <xref linkend="constraints"/> and <xref linkend="insert"/> or
+        <xref linkend="constraints"/>, and <xref linkend="insert"/>, or
         <xref linkend="server-sql-mode"/>.
       </para>
 
@@ -1304,7 +1304,7 @@
             optimizer choose better indexes. For
             <literal>MyISAM</literal> tables, <command>myisamchk
             --analyze</command> does the same. See
-            <xref linkend="analyze-table"/> and
+            <xref linkend="analyze-table"/>, and
             <xref linkend="table-maintenance"/>.
           </para>
         </listitem>
@@ -1431,7 +1431,7 @@
                 use a <literal>range</literal> or
                 <literal>index_merge</literal> access method to retrieve
                 rows. The applicability criteria are as described in
-                <xref linkend="range-optimization"/> and
+                <xref linkend="range-optimization"/>, and
                 <xref linkend="index-merge-optimization"/>, with the
                 exception that all column values for the preceding table
                 are known and considered to be constants.
@@ -1521,7 +1521,7 @@
               <para>
                 These indicate how index scans are merged for the
                 <literal>index_merge</literal> join type. See
-                <xref linkend="index-merge-optimization"/> for more
+                <xref linkend="index-merge-optimization"/>, for more
                 information.
               </para>
             </listitem>
@@ -2065,7 +2065,7 @@
         tables should usually be done with indexes. You can use the
         <literal>EXPLAIN</literal> statement to determine which indexes
         are used for a <literal>SELECT</literal>. See
-        <xref linkend="mysql-indexes"/> and <xref linkend="explain"/>.
+        <xref linkend="mysql-indexes"/>, and <xref linkend="explain"/>.
       </para>
 
       <para>
@@ -2714,7 +2714,7 @@
             </para>
 
             <para>
-              See <xref linkend="range-access-single-part"/> for the
+              See <xref linkend="range-access-single-part"/>, for the
               definition of what is considered to be a constant.
             </para>
 
@@ -2841,7 +2841,7 @@
         </itemizedlist>
 
         <para>
-          <xref linkend="range-access-single-part"/> describes how
+          <xref linkend="range-access-single-part"/>, describes how
           optimizations are performed to combine or eliminate intervals
           for range conditions on single-part index. Analogous steps are
           performed for range conditions on multiple-part keys.
@@ -4737,7 +4737,7 @@
           clause, a loose index scan reads as many keys as the number of
           groups, which may be a much smaller number than that of all
           keys. If the <literal>WHERE</literal> clause contains range
-          predicates (see the discussion in <xref linkend="explain"/> of
+          predicates (see the discussion in <xref linkend="explain"/>, of
           the <literal>range</literal> join type), a loose index scan
           looks up the first key of each group that satisfies the range
           conditions, and again reads the least possible number of keys.
@@ -5689,8 +5689,8 @@
           <para>
             Stored procedures or UDFs (user-defined functions) may be a
             good way to gain performance for some tasks. See
-            <xref linkend="stored-procedures"/> and
-            <xref linkend="adding-functions"/> for more information
+            <xref linkend="stored-procedures"/>, and
+            <xref linkend="adding-functions"/>, for more information
             about these.
           </para>
         </listitem>
@@ -6458,7 +6458,7 @@
             If you encounter speed problems with table locks in MySQL,
             you may be able to improve performance by converting some of
             your tables to <literal>InnoDB</literal> or
-            <literal>BDB</literal> tables. See <xref linkend="innodb"/>
+            <literal>BDB</literal> tables. See <xref linkend="innodb"/>,
             and <xref linkend="bdb-storage-engine"/>.
           </para>
         </listitem>
@@ -6828,7 +6828,7 @@
         <literal>CHAR</literal>, <literal>VARCHAR</literal>, and
         <literal>TEXT</literal> columns. Indexing always takes place
         over the entire column and partial (prefix) indexing is not
-        supported. See <xref linkend="fulltext-search"/> for details.
+        supported. See <xref linkend="fulltext-search"/>, for details.
       </para>
 
       <para>
@@ -7569,7 +7569,7 @@
           <literal>keycache1.key_buffer_size</literal>,
           <literal>keycache1</literal> is the cache variable name and
           <literal>key_buffer_size</literal> is the cache component. See
-          <xref linkend="structured-system-variables"/> for a
+          <xref linkend="structured-system-variables"/>, for a
           description of the syntax used for referring to structured key
           cache system variables.
         </para>
@@ -8407,7 +8407,7 @@
         If the value is very large, even when you have not issued many
         <literal>FLUSH TABLES</literal> statements, you should increase
         the table cache size. See
-        <xref linkend="server-system-variables"/> and
+        <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 
@@ -8871,7 +8871,7 @@
 
       <para>
         You can find a full description for all system and status
-        variables in <xref linkend="server-system-variables"/> and
+        variables in <xref linkend="server-system-variables"/>, and
         <xref linkend="server-status-variables"/>.
       </para>
 

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/partitioning.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -158,7 +158,7 @@
       notion of a tablespace, and the MySQL Server, even prior to the
       introduction of partitioning, could be configured to employ
       different physical directories for storing different databases
-      (see <xref linkend="symbolic-links"/> for an explanation of how
+      (see <xref linkend="symbolic-links"/>, for an explanation of how
       this is done).
     </para>
 
@@ -303,7 +303,7 @@
       <literal>MAX_ROWS</literal> and <literal>MIN_ROWS</literal> can be
       used to determine the maximum and minimum numbers of rows,
       respectively, that can be stored in each partition. See
-      <xref linkend="partitioning-management"/> for more information on
+      <xref linkend="partitioning-management"/>, for more information on
       these options. <emphasis role="bold">Note</emphasis>: This
       particular feature is currently nonfunctional due to Bug #13250;
       we should have this fixed by the time the first 5.1 binaries are
@@ -622,7 +622,7 @@
         increased to 25, 30, or more &mdash; you can use an
         <literal>ALTER TABLE</literal> statement to add new partitions
         for stores 21-25, 26-30, and so on (see
-        <xref linkend="partitioning-management"/> for details of how to
+        <xref linkend="partitioning-management"/>, for details of how to
         do this).
       </para>
 
@@ -725,8 +725,8 @@
             you can simply use <literal>ALTER TABLE employees DROP
             PARTITION p0;</literal> to delete all rows relating to
             employees who stopped working for the firm prior to 1991.
-            (See <xref linkend="alter-table"/> and
-            <xref linkend="partitioning-management"/> for more
+            (See <xref linkend="alter-table"/>, and
+            <xref linkend="partitioning-management"/>, for more
             information.) For a table with a great many rows, this can
             be much more efficient than running a
             <literal>DELETE</literal> query such as <literal>DELETE FROM
@@ -1160,7 +1160,7 @@
         hashing</firstterm> which employs a more complex algorithm for
         determining the placement of new rows inserted into the
         partitioned table. See
-        <xref linkend="partitioning-linear-hash"/> for a description of
+        <xref linkend="partitioning-linear-hash"/>, for a description of
         this algorithm.
       </para>
 
@@ -1408,7 +1408,7 @@
         <literal>KEY</literal> partitioning as it does on
         <literal>HASH</literal> partitioning, with the partition number
         being derived using a powers-of-two algorithm rather than modulo
-        arithmetic. See <xref linkend="partitioning-linear-hash"/> for a
+        arithmetic. See <xref linkend="partitioning-linear-hash"/>, for a
         description of this algorithm and its implications.
       </para>
 
@@ -1748,7 +1748,7 @@
             default location no longer provides sufficient space, the
             corresponding rows can be moved using an <literal>ALTER
             TABLE ... REORGANIZE PARTITION</literal> statement. See
-            <xref linkend="partitioning-management"/> for an explanation
+            <xref linkend="partitioning-management"/>, for an explanation
             of how this can be done.
           </para>
         </listitem>
@@ -1991,7 +1991,7 @@
       partitioned tables. It is possible to add, drop, redefine, merge,
       or split existing partitions. All of these actions can be carried
       out using the partitioning extensions to the <literal>ALTER
-      TABLE</literal> command (see <xref linkend="alter-table"/> for
+      TABLE</literal> command (see <xref linkend="alter-table"/>, for
       syntax definitions). There are also ways to obtain information
       about partitioned tables and partitions. We discuss these topics
       in the sections that follow.
@@ -2018,7 +2018,7 @@
 
       <listitem>
         <para>
-          See <xref linkend="partitioning-info"/> for a discussion of
+          See <xref linkend="partitioning-info"/>, for a discussion of
           mechanisms provided in MySQL &current-series; for obtaining
           information about partitioned tables and partitions.
         </para>
@@ -2203,7 +2203,7 @@
         If you intend to change the partitioning of a table
         <emphasis>without</emphasis> losing data, use <literal>ALTER
         TABLE ... REORGANIZE PARTITION</literal> instead. See below or
-        in <xref linkend="alter-table"/> for information about
+        in <xref linkend="alter-table"/>, for information about
         <literal>REORGANIZE PARTITION</literal>.
       </para>
 
@@ -2283,7 +2283,7 @@
         use of the table afterwards: You can no longer insert into the
         table any rows having any of the values that were included in
         the value list defining the deleted partition. (See
-        <xref linkend="partitioning-list"/> for an example.)
+        <xref linkend="partitioning-list"/>, for an example.)
       </para>
 
       <para>
@@ -2565,7 +2565,7 @@
             you could not reuse the names of existing partitions in the
             <literal>INTO</literal> clause, even when those partitions
             were being dropped or redefined. See 
-            <xref linkend="news-5-1-4"/> for more information.
+            <xref linkend="news-5-1-4"/>, for more information.
           </para>
         </listitem>
 
@@ -2991,7 +2991,7 @@
         tables, and its output is the same as that for non-partitioned
         tables, except that the <literal>Engine</literal> column always
         contains the value <literal>'PARTITION'</literal>. (See
-        <xref linkend="show-table-status"/> for more information about
+        <xref linkend="show-table-status"/>, for more information about
         this command.) To obtain status information for individual
         partitions, we plan to implement a <literal>SHOW PARTITION
         STATUS</literal> command (see below).

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/problems.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -3628,7 +3628,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="working-with-null"/> for additional
+        See <xref linkend="working-with-null"/>, for additional
         information and examples.
       </para>
 
@@ -3803,7 +3803,7 @@
 </programlisting>
 
       <para>
-        See <xref linkend="show-table-status"/> and
+        See <xref linkend="show-table-status"/>, and
         <xref linkend="show-create-table"/>.
       </para>
 
@@ -3834,7 +3834,7 @@
       </para>
 
       <para>
-        See <xref linkend="show-engines"/> and
+        See <xref linkend="show-engines"/>, and
         <xref linkend="show-variables"/>.
       </para>
 
@@ -4527,7 +4527,7 @@
         <listitem>
           <para>
             There are known issues in using temporary tables with
-            replication. See <xref linkend="replication-features"/> for 
+            replication. See <xref linkend="replication-features"/>, for 
             more information.
           </para>
         </listitem>
@@ -4569,7 +4569,7 @@
     <para>
       For information about platform-specific issues, see the
       installation and porting instructions in
-      <xref linkend="operating-system-specific-notes"/> and
+      <xref linkend="operating-system-specific-notes"/>, and
       <xref linkend="porting"/>.
     </para>
 

Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/replication.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -852,7 +852,7 @@
         <filename>relay-log.info</filename> by default. They contain
         information like that shown in the output of the <literal>SHOW
         SLAVE STATUS</literal> statement (see
-        <xref linkend="replication-slave-sql"/> for a description of
+        <xref linkend="replication-slave-sql"/>, for a description of
         this statement). As disk files, they survive a slave server's
         shutdown. The next time the slave starts up, it reads these
         files to determine how far it has proceeded in reading binary
@@ -1037,7 +1037,7 @@
     <para>
       If you want to administer a MySQL replication setup, we suggest
       that you read this entire chapter through and try all statements
-      mentioned in <xref linkend="replication-master-sql"/> and
+      mentioned in <xref linkend="replication-master-sql"/>, and
       <xref linkend="replication-slave-sql"/>. You should also
       familiarize yourself with replication startup options described in
       <xref linkend="replication-options"/>.
@@ -1509,7 +1509,7 @@
       <emphasis role="bold">Note</emphasis>: The content of
       <filename>master.info</filename> overrides some of the options
       specified on the command line or in <filename>my.cnf</filename>.
-      See <xref linkend="replication-options"/> for more details.
+      See <xref linkend="replication-options"/>, for more details.
     </para>
 
     <para>
@@ -1995,7 +1995,7 @@
           startup, it notifies the slaves that the table needs to be
           emptied by writing a <literal>DELETE FROM</literal> statement
           for that table to the binary log. See
-          <xref linkend="memory-storage-engine"/> for more information.
+          <xref linkend="memory-storage-engine"/>, for more information.
         </para>
       </listitem>
 
@@ -4438,7 +4438,7 @@
           it is a bug or you have encountered one of the known
           replication limitations described in
           <xref linkend="replication-features"/>. If it is a bug, see
-          <xref linkend="replication-bugs"/> for instructions on how to
+          <xref linkend="replication-bugs"/>, for instructions on how to
           report it.
         </para>
       </listitem>

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/sql-syntax.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -807,7 +807,7 @@
             for <literal>ALTER TABLE ADD PARTITION</literal> supports
             the same options as the clause of the same name does for the
             <literal>CREATE TABLE</literal> statement clause of the same
-            name. (See <xref linkend="create-table"/> for the syntax and
+            name. (See <xref linkend="create-table"/>, for the syntax and
             description.) For example, suppose you have the partitioned
             table created as shown here:
           </para>
@@ -1419,7 +1419,7 @@
         plugin with the index if full-text indexing and searching
         operations need special handling. This clause is legal only for
         <literal>FULLTEXT</literal> indexes. See
-        <xref linkend="plugin-api"/> for details on creating plugins.
+        <xref linkend="plugin-api"/>, for details on creating plugins.
       </para>
 
       <para>
@@ -2198,13 +2198,13 @@
             <literal>VARCHAR</literal>, and <literal>TEXT</literal>
             columns. Indexing always happens over the entire column;
             partial indexing is not supported and any prefix length is
-            ignored if specified. See <xref linkend="fulltext-search"/>
+            ignored if specified. See <xref linkend="fulltext-search"/>,
             for details of operation. A <literal>WITH PARSER</literal>
             clause can be specified to associate a parser plugin with
             the index if full-text indexing and searching operations
             need special handling. This clause is legal only for
             <literal>FULLTEXT</literal> indexes. See
-            <xref linkend="plugin-api"/> for details on creating
+            <xref linkend="plugin-api"/>, for details on creating
             plugins.
           </para>
         </listitem>
@@ -2725,7 +2725,7 @@
             <option>--skip-symbolic-links</option> option. Your
             operating system must also have a working, thread-safe
             <literal>realpath()</literal> call. See
-            <xref linkend="symbolic-links-to-tables"/> for more complete
+            <xref linkend="symbolic-links-to-tables"/>, for more complete
             information.
           </para>
         </listitem>
@@ -3964,7 +3964,7 @@
         <command>myisamchk</command> utility to reorganize tables.
         <literal>OPTIMIZE TABLE</literal> is easier, but
         <command>myisamchk</command> is faster. See
-        <xref linkend="optimize-table"/> and
+        <xref linkend="optimize-table"/>, and
         <xref linkend="optimization"/>.
       </para>
 
@@ -4803,7 +4803,7 @@
         behave identically. The behavior of <literal>INSERT</literal>
         statements with respect to <literal>AUTO_INCREMENT</literal>
         columns is discussed further in
-        <xref linkend="information-functions"/> and
+        <xref linkend="information-functions"/>, and
         <xref linkend="mysql-insert-id"/>.
       </para>
 
@@ -6630,7 +6630,7 @@
       <para>
         <literal>SELECT</literal> is used to retrieve rows selected from
         one or more tables, and can include <literal>UNION</literal>
-        statements and subqueries. See <xref linkend="union"/> and
+        statements and subqueries. See <xref linkend="union"/>, and
         <xref linkend="subqueries"/>.
       </para>
 
@@ -6838,7 +6838,7 @@
             or
             <replaceable>db_name</replaceable>.<replaceable>tbl_name</replaceable>
             prefix for a column reference unless the reference would be
-            ambiguous. See <xref linkend="legal-names"/> for examples of
+            ambiguous. See <xref linkend="legal-names"/>, for examples of
             ambiguity that require the more explicit column reference
             forms.
           </para>
@@ -12879,8 +12879,8 @@
               columns are set to their implicit default values if strict
               SQL mode is not enabled. In strict mode, the statement is
               rejected if any of the omitted columns have no default
-              value. <xref linkend="server-sql-mode"/> discusses strict
-              mode. <xref linkend="create-table"/> discusses implicit
+              value. <xref linkend="server-sql-mode"/>, discusses strict
+              mode. <xref linkend="create-table"/>, discusses implicit
               default values.
             </para>
 
@@ -13033,7 +13033,7 @@
           to a MySQL 4.1 or later server using a pre-4.1 client program,
           do not use the preceding <literal>SET PASSWORD</literal> or
           <literal>UPDATE</literal> statement without reading
-          <xref linkend="password-hashing"/> first. The password format
+          <xref linkend="password-hashing"/>, first. The password format
           changed in MySQL 4.1, and under certain circumstances it is
           possible that if you change your password, you might not be
           able to connect to the server afterward.
@@ -17143,7 +17143,7 @@
           these variables using command-line options when
           <command>mysqld</command> starts or at runtime with the
           <literal>SET</literal> statement. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="set-option"/>.
         </para>
 
@@ -17779,7 +17779,7 @@
         </para>
 
         <para>
-          See also <xref linkend="reset"/> for information about how the
+          See also <xref linkend="reset"/>, for information about how the
           <literal>RESET</literal> statement is used with replication.
         </para>
 
@@ -18135,7 +18135,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing master replication
-        servers. <xref linkend="replication-slave-sql"/> discusses
+        servers. <xref linkend="replication-slave-sql"/>, discusses
         statements for managing slave servers.
       </para>
 
@@ -18396,7 +18396,7 @@
         <para>
           Lists the binary log files on the server. This statement is
           used as part of the procedure described in
-          <xref linkend="purge-master-logs"/> for determining which logs
+          <xref linkend="purge-master-logs"/>, for determining which logs
           can be purged.
         </para>
 
@@ -18524,7 +18524,7 @@
       <para>
         Replication can be controlled through the SQL interface. This
         section discusses statements for managing slave replication
-        servers. <xref linkend="replication-master-sql"/> discusses
+        servers. <xref linkend="replication-master-sql"/>, discusses
         statements for managing master servers.
       </para>
 
@@ -18943,7 +18943,7 @@
           This is actually a function, not a statement. It is used to
           ensure that the slave has read and executed events up to a
           given position in the master's binary log. See
-          <xref linkend="miscellaneous-functions"/> for a full
+          <xref linkend="miscellaneous-functions"/>, for a full
           description.
         </para>
 

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/storage-engines.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -307,7 +307,7 @@
 </programlisting>
 
   <para>
-    See <xref linkend="create-table"/> and
+    See <xref linkend="create-table"/>, and
     <xref linkend="alter-table"/>.
   </para>
 
@@ -1454,7 +1454,7 @@
           corruption is a result of the server dying. Otherwise,
           corruption may have occurred during normal operation. This is
           a bug. You should try to create a reproducible test case that
-          demonstrates the problem. See <xref linkend="crashing"/> and
+          demonstrates the problem. See <xref linkend="crashing"/>, and
           <xref linkend="reproduceable-test-case"/>.
         </para>
 
@@ -1576,7 +1576,7 @@
             <para>
               In general, it is a bad idea to share a data directory
               among multiple servers. See
-              <xref linkend="multiple-servers"/> for additional
+              <xref linkend="multiple-servers"/>, for additional
               discussion.
             </para>
           </listitem>
@@ -1924,7 +1924,7 @@
           used up does the storage engine need to read the next key
           block. This makes <literal>MERGE</literal> keys much slower on
           <literal>eq_ref</literal> searches, but not much slower on
-          <literal>ref</literal> searches. See <xref linkend="explain"/>
+          <literal>ref</literal> searches. See <xref linkend="explain"/>,
           for more information about <literal>eq_ref</literal> and
           <literal>ref</literal>.
         </para>
@@ -2315,7 +2315,7 @@
           statements such as <literal>INSERT INTO ... SELECT</literal>
           or <literal>LOAD DATA INFILE</literal> into this file in order
           to load the table from a persistent data source. See
-          <xref linkend="server-options"/> and
+          <xref linkend="server-options"/>, and
           <xref linkend="load-data"/>.
         </para>
       </listitem>
@@ -3002,7 +3002,7 @@
             unexpectedly. It should not be fatal even if this number is
             not 100% correct. You can update the row count by using
             <literal>ANALYZE TABLE</literal> or <literal>OPTIMIZE
-            TABLE</literal>. See <xref linkend="analyze-table"/> and
+            TABLE</literal>. See <xref linkend="analyze-table"/>, and
             <xref linkend="optimize-table"/>.
           </para>
         </listitem>

Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/stored-procedures.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -341,8 +341,8 @@
         Compound statements can contain declarations, loops, and other
         control structure statements. The syntax for these statements is
         described later in this chapter. See, for example,
-        <xref linkend="declare"/> and
-        <xref linkend="flow-control-constructs"/>
+        <xref linkend="declare"/>, and
+        <xref linkend="flow-control-constructs"/>.
       </para>
 
       <remark role="help-description-end"/>

Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/triggers.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -479,7 +479,7 @@
       MySQL &current-series; releases &mdash; you must drop all triggers
       <emphasis>before upgrading</emphasis> and re-create them
       afterwards, or else <literal>DROP TRIGGER</literal> does not work
-      after the upgrade. See <xref linkend="upgrading-from-5-0"/> for a
+      after the upgrade. See <xref linkend="upgrading-from-5-0"/>, for a
       suggested upgrade procedure.
     </para>
 
@@ -516,7 +516,7 @@
       To create a trigger or drop a trigger, use the <literal>CREATE
       TRIGGER</literal> or <literal>DROP TRIGGER</literal> statement.
       The syntax for these statements is described in
-      <xref linkend="create-trigger"/> and
+      <xref linkend="create-trigger"/>, and
       <xref linkend="drop-trigger"/>.
     </para>
 

Modified: trunk/refman-5.1/tutorial.xml
===================================================================
--- trunk/refman-5.1/tutorial.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-5.1/tutorial.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1144,7 +1144,7 @@
       <para>
         If the statement fails, it is likely that your MySQL
         installation does not have local file capability enabled by
-        default. See <xref linkend="load-data-local"/> for information
+        default. See <xref linkend="load-data-local"/>, for information
         on how to change this.
       </para>
 
@@ -2296,7 +2296,7 @@
 </programlisting>
 
         <para>
-          <xref linkend="regexp"/> provides more information about the
+          <xref linkend="regexp"/>, provides more information about the
           syntax for regular expressions.
         </para>
 
@@ -3736,7 +3736,7 @@
           <listitem>
             <para>
               How to assign the <literal>AUTO_INCREMENT</literal>
-              attribute to a column: <xref linkend="create-table"/> and
+              attribute to a column: <xref linkend="create-table"/>, and
               <xref linkend="alter-table"/>.
             </para>
           </listitem>

Modified: trunk/refman-common/news-4.0.xml
===================================================================
--- trunk/refman-common/news-4.0.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/news-4.0.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -408,7 +408,7 @@
           <command>configure</command>. (Previously it was necessary to
           pass <option>-DBIG_TABLES</option> to the compiler manually in
           order to enable large table support.)
-          <xref linkend="configure-options"/> for details.
+          See <xref linkend="configure-options"/>, for details.
         </para>
       </listitem>
 
@@ -7103,8 +7103,7 @@
           <literal>InnoDB</literal> now supports also isolation levels
           <literal>READ UNCOMMITTED</literal> and <literal>READ
           COMMITTED</literal>. For a detailed <literal>InnoDB</literal>
-          changelog, see <xref linkend="innodb-change-history"/> in this
-          manual.
+          changelog, see <xref linkend="innodb-change-history"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/news-4.1.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -3897,7 +3897,7 @@
           <command>configure</command>. (Previously it was necessary to
           pass <option>-DBIG_TABLES</option> to the compiler manually in
           order to enable large table support.) See
-          <xref linkend="configure-options"/> for details.
+          <xref linkend="configure-options"/>, for details.
         </para>
       </listitem>
 
@@ -3906,7 +3906,7 @@
           Added configuration directives <literal>!include</literal> and
           <literal>!includedir</literal> for including option files and
           searching directories for option files. See
-          <xref linkend="option-files"/> for usage.
+          <xref linkend="option-files"/>, for usage.
         </para>
       </listitem>
 
@@ -4954,7 +4954,7 @@
           encounters older tables that contain character columns that
           might be interpreted by newer servers to have a different
           column length. (Bug #6913) See
-          <xref linkend="upgrading-from-4-0"/> for a discussion of this
+          <xref linkend="upgrading-from-4-0"/>, for a discussion of this
           problem and what to do about it.
         </para>
       </listitem>

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/news-5.0.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -469,7 +469,7 @@
           The syntax for <literal>CREATE TRIGGER</literal> now includes
           a <literal>DEFINER</literal> clause for specifying which
           access privileges to check at trigger invocation time. See
-          <xref linkend="create-trigger"/> for more information.
+          <xref linkend="create-trigger"/>, for more information.
         </para>
       </listitem>
 
@@ -1214,7 +1214,7 @@
           <option>--log-bin-trust-function-creators</option>. For
           backward compatibility, the old names are recognized but
           result in a warning.
-          <xref linkend="stored-procedure-logging"/>
+          See <xref linkend="stored-procedure-logging"/>.
         </para>
       </listitem>
 
@@ -1234,7 +1234,7 @@
           VIEW</literal> statements, but the clauses had no effect. They
           now are enabled. They specify the security context to be used
           when checking access privileges at view invocation time. See
-          <xref linkend="create-view"/> for more information.
+          <xref linkend="create-view"/>, for more information.
         </para>
       </listitem>
 
@@ -2814,7 +2814,7 @@
           clauses for specifying the security context to be used when
           checking access privileges at view invocation time. (The
           syntax is present in 5.0.13, but these clauses have no effect
-          until 5.0.16.) See <xref linkend="create-view"/> for more
+          until 5.0.16.) See <xref linkend="create-view"/>, for more
           information.
         </para>
       </listitem>
@@ -3782,7 +3782,7 @@
         <para>
           It is no longer possible to issue <literal>FLUSH</literal>
           commands from within stored functions or triggers. See
-          <xref linkend="routine-restrictions"/> for details. (Bug
+          <xref linkend="routine-restrictions"/>, for details. (Bug
           #12280, Bug #12307)
         </para>
       </listitem>
@@ -4898,7 +4898,7 @@
               An extension to the <literal>SHOW</literal> command has
               been added: <literal>SHOW TRIGGERS</literal> can be used
               to view a listing of triggers. See
-              <xref linkend="show-triggers"/> for details.
+              <xref linkend="show-triggers"/>, for details.
             </para>
           </listitem>
 
@@ -4906,7 +4906,7 @@
             <para>
               The <literal>INFORMATION_SCHEMA</literal> database now
               includes a <literal>TRIGGERS</literal> table. See
-              <xref linkend="triggers-table"/> for details. (Bug #9586)
+              <xref linkend="triggers-table"/>, for details. (Bug #9586)
             </para>
           </listitem>
 
@@ -4916,7 +4916,7 @@
       <listitem>
         <para>
           Triggers can now reference tables by name. See
-          <xref linkend="create-trigger"/> for more information.
+          <xref linkend="create-trigger"/>, for more information.
         </para>
       </listitem>
 
@@ -6593,7 +6593,7 @@
           The behavior of the <literal>Last_query_cost</literal> system
           variable has been changed. The default value is now 0 (rather
           than -1) and it now has session-level scope (rather than being
-          global). See <xref linkend="server-status-variables"/> for
+          global). See <xref linkend="server-status-variables"/>, for
           additional information.
         </para>
       </listitem>
@@ -7366,7 +7366,7 @@
           recovery options. (Bug #2610) Stored routine-related
           statements now are logged, subject to the issues and
           limitations discussed in
-          <xref linkend="stored-procedure-logging"/>
+          <xref linkend="stored-procedure-logging"/>.
         </para>
       </listitem>
 
@@ -7388,7 +7388,7 @@
           written to the binary log, which affects replication and data
           recovery options. (Bug #10417) Trigger-related statements now
           are logged, subject to the issues and limitations discussed in
-          <xref linkend="stored-procedure-logging"/>
+          <xref linkend="stored-procedure-logging"/>.
         </para>
       </listitem>
 
@@ -8249,7 +8249,7 @@
           <command>configure</command>. (Previously it was necessary to
           pass <option>-DBIG_TABLES</option> to the compiler manually in
           order to enable large table support.) See
-          <xref linkend="configure-options"/> for details.
+          <xref linkend="configure-options"/>, for details.
         </para>
       </listitem>
 
@@ -8258,7 +8258,7 @@
           New configuration directives <literal>!include</literal> and
           <literal>!includedir</literal> implemented for including
           option files and searching directories for option files. See
-          <xref linkend="option-files"/> for usage.
+          <xref linkend="option-files"/>, for usage.
         </para>
       </listitem>
 
@@ -11567,7 +11567,7 @@
         <para>
           Easier replication upgrade (5.0.0 masters can read older
           binary logs and 5.0.0 slaves can read older relay logs). See
-          <xref linkend="replication-compatibility"/> for more details).
+          <xref linkend="replication-compatibility"/>, for more details).
           The format of the binary log and relay log is changed compared
           to that of MySQL 4.1 and older.
         </para>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/news-5.1.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -398,7 +398,7 @@
           is created. In effect, different portions of a table are
           stored as separate tables in different locations, but from the
           user point of view, the partitioned table is still a single
-          table. See <xref linkend="partitioning"/> for further
+          table. See <xref linkend="partitioning"/>, for further
           information on this functionality. (Author: Mikael Ronström)
         </para>
       </listitem>
@@ -469,7 +469,7 @@
                 <literal>SET <replaceable>instance_name</replaceable>.
                 <replaceable>option_name</replaceable>=<replaceable>option_value</replaceable></literal>
                 sets an option to the specified value and writes it to
-                the config file See <xref linkend="instance-manager"/>
+                the config file See <xref linkend="instance-manager"/>,
                 for more details on these new commands. (Author: Petr
                 Chardin)
               </para>
@@ -483,7 +483,7 @@
         <para>
           The performance of boolean full-text searches (using the
           <quote>+</quote> Operator) has been improved. See
-          <xref linkend="fulltext-search"/> for more details about
+          <xref linkend="fulltext-search"/>, for more details about
           full-text searching. (Author: Sergey Vojtovich)
         </para>
       </listitem>

Modified: trunk/refman-common/news-cluster.xml
===================================================================
--- trunk/refman-common/news-cluster.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/news-cluster.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -1025,7 +1025,7 @@
         <para>
           The ndb executables have been changed to make use of the
           regular MySQL command line option parsing features. See
-          <xref linkend="mysql-cluster-command-options"/> for notes on
+          <xref linkend="mysql-cluster-command-options"/>, for notes on
           changes.
         </para>
       </listitem>

Modified: trunk/refman-common/what-is.en.xml
===================================================================
--- trunk/refman-common/what-is.en.xml	2006-01-03 04:44:16 UTC (rev 645)
+++ trunk/refman-common/what-is.en.xml	2006-01-03 05:33:23 UTC (rev 646)
@@ -274,7 +274,7 @@
 
     <para>
       The following list describes some of the important characteristics
-      of the MySQL Database Software. See also <xref linkend="roadmap"/>
+      of the MySQL Database Software. See also <xref linkend="roadmap"/>,
       for more information about current and upcoming features.
     </para>
 
@@ -1147,7 +1147,7 @@
     <para>
       Thus, even though MySQL Server has no Y2K problems, <emphasis>it
       is the application's responsibility to provide unambiguous
-      input</emphasis>. See <xref linkend="y2k-issues"/> for MySQL
+      input</emphasis>. See <xref linkend="y2k-issues"/>, for MySQL
       Server's rules for dealing with ambiguous date input data that
       contains two-digit year values.
     </para>

Thread
svn commit - mysqldoc@docsrva: r646 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-commonpaul3 Jan