List:Commits« Previous MessageNext Message »
From:paul Date:January 9 2006 2:57am
Subject:svn commit - mysqldoc@docsrva: r731 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-09 03:57:50 +0100 (Mon, 09 Jan 2006)
New Revision: 731

Log:
 r5978@frost:  paul | 2006-01-08 20:57:32 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/apis.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/innodb.xml
   trunk/refman-4.1/installing.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-4.1/optimization.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-4.1/storage-engines.xml
   trunk/refman-5.0/apis.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/innodb.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.0/storage-engines.xml
   trunk/refman-5.1/apis.xml
   trunk/refman-5.1/connector-odbc.xml
   trunk/refman-5.1/custom-engine.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/innodb.xml
   trunk/refman-5.1/installing.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/sql-syntax.xml
   trunk/refman-5.1/storage-engines.xml
   trunk/refman-common/news-4.0.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-innodb.xml


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

Modified: trunk/refman-4.1/apis.xml
===================================================================
--- trunk/refman-4.1/apis.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/apis.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1991,8 +1991,8 @@
         <para>
           Note that when you use a <literal>REPLACE</literal> command,
           <literal>mysql_affected_rows()</literal> returns 2 if the new
-          row replaced an old row. This is because in this case one row
-          was inserted after the duplicate was deleted.
+          row replaced an old row, because in this case one row was
+          inserted after the duplicate was deleted.
         </para>
 
         <para>

Modified: trunk/refman-4.1/connector-odbc.xml
===================================================================
--- trunk/refman-4.1/connector-odbc.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/connector-odbc.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -5368,7 +5368,7 @@
       <title>&title-nocursor;</title>
 
       <para>
-        This is because the application is using old MyODBC 2.50
+        This occurs because the application is using old MyODBC 2.50
         version, and it did not set the cursor name explicitly through
         SQLSetCursorName. The fix is to upgrade to MyODBC 3.51 version.
       </para>

Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/data-types.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2586,7 +2586,7 @@
         use strings that have fewer than 6 characters. For example, if
         you specify <literal>'9903'</literal>, thinking that represents
         March, 1999, MySQL inserts a <quote>zero</quote> date into your
-        table. This is because the year and month values are
+        table. This occurs because the year and month values are
         <literal>99</literal> and <literal>03</literal>, but the day
         part is completely missing, so the value is not a legal date.
         However, as of MySQL 3.23, you can explicitly specify a value of

Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/database-administration.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -11108,12 +11108,12 @@
       <para>
         Administrative privileges (such as <literal>RELOAD</literal> or
         <literal>SHUTDOWN</literal>) are specified only in the
-        <literal>user</literal> table. This is because administrative
-        operations are operations on the server itself and are not
-        database-specific, so there is no reason to list these
-        privileges in the other grant tables. In fact, to determine
-        whether you can perform an administrative operation, the server
-        need consult only the <literal>user</literal> table.
+        <literal>user</literal> table. The reason for this is that
+        administrative operations are operations on the server itself
+        and are not database-specific, so there is no reason to list
+        these privileges in the other grant tables. In fact, to
+        determine whether you can perform an administrative operation,
+        the server need consult only the <literal>user</literal> table.
       </para>
 
       <para>

Modified: trunk/refman-4.1/extending-mysql.xml
===================================================================
--- trunk/refman-4.1/extending-mysql.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/extending-mysql.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -715,7 +715,7 @@
       <para>
         To create a function, you must have the
         <literal>INSERT</literal> and privilege for the
-        <literal>mysql</literal> database. This is because
+        <literal>mysql</literal> database. This is necessary because
         <literal>CREATE FUNCTION</literal> adds a row to the
         <literal>mysql.func</literal> system table that records the
         function's name, type, and shared library name. If you do not

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/innodb.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1025,8 +1025,8 @@
         <literal>newraw</literal> immediately after the data file size
         in <literal>innodb_data_file_path</literal>. The partition must
         be at least as large as the size that you specify. Note that 1MB
-        in <literal>InnoDB</literal> is 1024 * 1024 bytes, whereas 1MB
-        usually means 1,000,000 bytes in disk specifications.
+        in <literal>InnoDB</literal> is 1024 &times; 1024 bytes, whereas
+        1MB usually means 1,000,000 bytes in disk specifications.
       </para>
 
 <programlisting>
@@ -4442,7 +4442,7 @@
       </para>
 
       <para>
-        If an SQL statement returns an error, the commit/rollback
+        If an SQL statement returns an error, the commit or rollback
         behavior depends on the error. See
         <xref linkend="innodb-error-handling"/>.
       </para>
@@ -4550,7 +4550,7 @@
         transaction, all the locks of the transaction are released.
         However, if just a single SQL statement is rolled back as a
         result of an error, some of the locks set by the SQL statement
-        may be preserved. This is because <literal>InnoDB</literal>
+        may be preserved. This happens because <literal>InnoDB</literal>
         stores row locks in a format such it cannot know afterward which
         lock was set by which SQL statement.
       </para>
@@ -5511,7 +5511,7 @@
         If index records are inserted in a sequential order (ascending
         or descending), the resulting index pages are about 15/16 full.
         If records are inserted in a random order, the pages are from
-        1/2 to 15/16 full. If the fillfactor of an index page drops
+        1/2 to 15/16 full. If the fill factor of an index page drops
         below 1/2, <literal>InnoDB</literal> tries to contract the index
         tree to free the page.
       </para>
@@ -5815,7 +5815,7 @@
         issuing a <literal>SHOW TABLE STATUS</literal>,
         <literal>InnoDB</literal> reports the extents that are
         definitely free in the tablespace. <literal>InnoDB</literal>
-        always reserves some extents for clean-up and other internal
+        always reserves some extents for cleanup and other internal
         purposes; these reserved extents are not included in the free
         space.
       </para>

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/installing.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -15850,9 +15850,9 @@
         <para>
           Some customers have had problems on BSDI 4.0.1 that the
           <command>mysqld</command> binary after a while cannot open
-          tables. This is because some library/system-related bug causes
-          <command>mysqld</command> to change current directory without
-          having asked for that to happen.
+          tables. This occurs because some library/system-related bug
+          causes <command>mysqld</command> to change current directory
+          without having asked for that to happen.
         </para>
 
         <para>

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1710,8 +1710,8 @@
 
       <para>
         For subsequent <command>ndbd</command> starts, you will
-        generally <emphasis role="bold">not</emphasis> want to use this
-        option:
+        generally <emphasis role="bold">not</emphasis> want to use the
+        <option>--initial</option> option:
       </para>
 
 <programlisting>
@@ -1719,11 +1719,11 @@
 </programlisting>
 
       <para>
-        This is because the <option>--initial</option> option will
-        delete all existing data and log files (as well as all table
-        metadata) for this data node and create new ones. One exception
-        to this rule is when restarting the cluster and restoring from
-        backup after adding new data nodes.
+        The reason for this is that the <option>--initial</option>
+        option will delete all existing data and log files (as well as
+        all table metadata) for this data node and create new ones. One
+        exception to this rule is when restarting the cluster and
+        restoring from backup after adding new data nodes.
       </para>
 
       <remark role="todo">
@@ -2595,8 +2595,9 @@
         <para>
           For each parameter it is possible to use <literal>k</literal>,
           <literal>M</literal>, or <literal>G</literal> as a suffix to
-          indicate units of 1024, 1024*1024, or 1024*1024*1024. (For
-          example, <literal>100k</literal> means 100 * 1024 = 102400.)
+          indicate units of 1024, 1024&times;1024, or
+          1024&times;1024&times;1024. (For example,
+          <literal>100k</literal> means 100 &times; 1024 = 102400.)
           Parameters and values are currently case-sensitive.
         </para>
 
@@ -3281,9 +3282,9 @@
               <filename>ndb/src/kernel/blocks/Dbtc/Dbtc.hpp</filename>)
               set to 4000*128 bytes (500KB). A similar buffer for key
               info, <literal>ZDATABUF_FILESIZE</literal> (also in
-              <filename>Dbtc.hpp</filename>) contains 4000 * 16 = 62.5KB
-              of buffer space. <literal>Dbtc</literal> is the module
-              which handles transaction coordination.
+              <filename>Dbtc.hpp</filename>) contains 4000 &times; 16 =
+              62.5KB of buffer space. <literal>Dbtc</literal> is the
+              module which handles transaction coordination.
             </para>
           </listitem>
 
@@ -10200,9 +10201,10 @@
           Yes, it is possible to use DNS and DHCP for cluster hosts.
           However, if your application requires <quote>five
           nines</quote> availability, we recommend using fixed IP
-          addresses. This is because making communication between
-          Cluster hosts dependent on such services introduces additional
-          points of failure, and the fewer of these, the better.
+          addresses. Making communication between Cluster hosts
+          dependent on services such as DNS and DHCP introduces
+          additional points of failure, and the fewer of these, the
+          better.
         </para>
       </listitem>
 

Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/optimization.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1681,9 +1681,9 @@
         Cartesian product of all the tables; that is, every combination
         of rows. This takes quite a long time, because the product of
         the number of rows in each table must be examined. For the case
-        at hand, this product is <literal>74 * 2135 * 74 * 3872 =
-        45,268,558,720</literal> rows. If the tables were bigger, you
-        can only imagine how long it would take.
+        at hand, this product is <literal>74 &times; 2135 &times; 74
+        &times; 3872 = 45,268,558,720</literal> rows. If the tables were
+        bigger, you can only imagine how long it would take.
       </para>
 
       <para>
@@ -1838,8 +1838,8 @@
         you can estimate that, using B-tree indexes, you need this many
         seeks to find a row:
         <literal>log(<replaceable>row_count</replaceable>) /
-        log(<replaceable>index_block_length</replaceable> / 3 * 2 /
-        (<replaceable>index_length</replaceable> +
+        log(<replaceable>index_block_length</replaceable> / 3 &times; 2
+        / (<replaceable>index_length</replaceable> +
         <replaceable>data_pointer_length</replaceable>)) + 1</literal>.
       </para>
 
@@ -1852,10 +1852,10 @@
       </para>
 
       <para>
-        This index would require storage of about 500,000 * 7 * 3/2 =
-        5.2MB (assuming a typical index buffer fill ratio of 2/3), so
-        you probably have much of the index in memory and so need only
-        one or two calls to read data to find the row.
+        This index would require storage of about 500,000 &times; 7
+        &times; 3/2 = 5.2MB (assuming a typical index buffer fill ratio
+        of 2/3), so you probably have much of the index in memory and so
+        need only one or two calls to read data to find the row.
       </para>
 
       <para>
@@ -4635,7 +4635,7 @@
       <para>
         <literal>InnoDB</literal> uses row locks and
         <literal>BDB</literal> uses page locks. For these two storage
-        engines, deadlocks are possible. This is because
+        engines, deadlocks are possible. This occurs because
         <literal>InnoDB</literal> automatically acquires row locks and
         <literal>BDB</literal> acquires page locks during the processing
         of SQL statements, not at the start of the transaction.

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/problems.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -3745,10 +3745,10 @@
 
       <para>
         Standard SQL doesn't allow you to refer to a column alias in a
-        <literal>WHERE</literal> clause. This is because when the
-        <literal>WHERE</literal> code is executed, the column value may
-        not yet be determined. For example, the following query is
-        illegal:
+        <literal>WHERE</literal> clause. This restriction is imposed
+        because when the <literal>WHERE</literal> code is executed, the
+        column value may not yet be determined. For example, the
+        following query is illegal:
       </para>
 
 <programlisting>
@@ -4418,7 +4418,7 @@
         If you use <literal>ALTER TABLE</literal> on a transactional
         table or if you are using Windows or OS/2, <literal>ALTER
         TABLE</literal> unlocks the table if you had done a
-        <literal>LOCK TABLE</literal> on it. This is because
+        <literal>LOCK TABLE</literal> on it. This is done because
         <literal>InnoDB</literal> and these operating systems cannot
         drop a table that is in use.
       </para>

Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/sql-syntax.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1152,9 +1152,9 @@
         index type. However, <literal>USING</literal> is the preferred
         form. In addition, the index name that precedes the index type
         in the index specification syntax is not optional with
-        <literal>TYPE</literal>. This is because, unlike
-        <literal>USING</literal>, <literal>TYPE</literal> is not a
-        reserved word and thus is interpreted as an index name.
+        <literal>TYPE</literal>: Unlike <literal>USING</literal>,
+        <literal>TYPE</literal> is not a reserved word and thus is
+        interpreted as an index name.
       </para>
 
       <para>
@@ -17092,9 +17092,9 @@
           <option>--replicate-*-do-*</option> and
           <option>--replicate-*-ignore-*</option> options are honored.
           <option>--replicate-rewrite-db</option> is
-          <emphasis>not</emphasis> taken into account. This is because a
-          user could, with this option, set up a non-unique mapping such
-          as <option>--replicate-rewrite-db=db1-&gt;db3</option> and
+          <emphasis>not</emphasis> taken into account because a user
+          could use this option to set up a non-unique mapping such as
+          <option>--replicate-rewrite-db=db1-&gt;db3</option> and
           <option>--replicate-rewrite-db=db2-&gt;db3</option>, which
           would confuse the slave when loading tables from the master.
         </para>

Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-4.1/storage-engines.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2028,7 +2028,7 @@
             TABLE</literal> to add a non-unique index on the
             <literal>MERGE</literal> table, the index ordering is
             different for the tables if there was already a non-unique
-            index in the underlying table. (This is because
+            index in the underlying table. (This happens because
             <literal>ALTER TABLE</literal> puts
             <literal>UNIQUE</literal> indexes before non-unique indexes
             to facilitate rapid detection of duplicate keys.)

Modified: trunk/refman-5.0/apis.xml
===================================================================
--- trunk/refman-5.0/apis.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/apis.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2039,8 +2039,8 @@
         <para>
           Note that when you use a <literal>REPLACE</literal> command,
           <literal>mysql_affected_rows()</literal> returns 2 if the new
-          row replaced an old row. This is because in this case one row
-          was inserted after the duplicate was deleted.
+          row replaced an old row, because in this case one row was
+          inserted after the duplicate was deleted.
         </para>
 
         <para>

Modified: trunk/refman-5.0/connector-odbc.xml
===================================================================
--- trunk/refman-5.0/connector-odbc.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/connector-odbc.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -5368,7 +5368,7 @@
       <title>&title-nocursor;</title>
 
       <para>
-        This is because the application is using old MyODBC 2.50
+        This occurs because the application is using old MyODBC 2.50
         version, and it did not set the cursor name explicitly through
         SQLSetCursorName. The fix is to upgrade to MyODBC 3.51 version.
       </para>

Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/data-types.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2653,7 +2653,7 @@
         use strings that have fewer than 6 characters. For example, if
         you specify <literal>'9903'</literal>, thinking that represents
         March, 1999, MySQL inserts a <quote>zero</quote> date value into
-        your table. This is because the year and month values are
+        your table. This occurs because the year and month values are
         <literal>99</literal> and <literal>03</literal>, but the day
         part is completely missing, so the value is not a legal date.
         However, you can explicitly specify a value of zero to represent

Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/database-administration.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -13175,12 +13175,12 @@
       <para>
         Administrative privileges (such as <literal>RELOAD</literal> or
         <literal>SHUTDOWN</literal>) are specified only in the
-        <literal>user</literal> table. This is because administrative
-        operations are operations on the server itself and are not
-        database-specific, so there is no reason to list these
-        privileges in the other grant tables. In fact, to determine
-        whether you can perform an administrative operation, the server
-        need consult only the <literal>user</literal> table.
+        <literal>user</literal> table. The reason for this is that
+        administrative operations are operations on the server itself
+        and are not database-specific, so there is no reason to list
+        these privileges in the other grant tables. In fact, to
+        determine whether you can perform an administrative operation,
+        the server need consult only the <literal>user</literal> table.
       </para>
 
       <para>

Modified: trunk/refman-5.0/extending-mysql.xml
===================================================================
--- trunk/refman-5.0/extending-mysql.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/extending-mysql.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -718,7 +718,7 @@
       <para>
         To create a function, you must have the
         <literal>INSERT</literal> and privilege for the
-        <literal>mysql</literal> database. This is because
+        <literal>mysql</literal> database. This is necessary because
         <literal>CREATE FUNCTION</literal> adds a row to the
         <literal>mysql.func</literal> system table that records the
         function's name, type, and shared library name. If you do not

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/innodb.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -913,8 +913,8 @@
         <literal>newraw</literal> immediately after the data file size
         in <literal>innodb_data_file_path</literal>. The partition must
         be at least as large as the size that you specify. Note that 1MB
-        in <literal>InnoDB</literal> is 1024 * 1024 bytes, whereas 1MB
-        usually means 1,000,000 bytes in disk specifications.
+        in <literal>InnoDB</literal> is 1024 &times; 1024 bytes, whereas
+        1MB usually means 1,000,000 bytes in disk specifications.
       </para>
 
 <programlisting>
@@ -4402,7 +4402,7 @@
       </para>
 
       <para>
-        If an SQL statement returns an error, the commit/rollback
+        If an SQL statement returns an error, the commit or rollback
         behavior depends on the error. See
         <xref linkend="innodb-error-handling"/>.
       </para>
@@ -4512,7 +4512,7 @@
         transaction, all the locks of the transaction are released.
         However, if just a single SQL statement is rolled back as a
         result of an error, some of the locks set by the SQL statement
-        may be preserved. This is because <literal>InnoDB</literal>
+        may be preserved. This happens because <literal>InnoDB</literal>
         stores row locks in a format such it cannot know afterward which
         lock was set by which SQL statement.
       </para>
@@ -5457,7 +5457,7 @@
         If index records are inserted in a sequential order (ascending
         or descending), the resulting index pages are about 15/16 full.
         If records are inserted in a random order, the pages are from
-        1/2 to 15/16 full. If the fillfactor of an index page drops
+        1/2 to 15/16 full. If the fill factor of an index page drops
         below 1/2, <literal>InnoDB</literal> tries to contract the index
         tree to free the page.
       </para>
@@ -5761,7 +5761,7 @@
         issuing a <literal>SHOW TABLE STATUS</literal>,
         <literal>InnoDB</literal> reports the extents that are
         definitely free in the tablespace. <literal>InnoDB</literal>
-        always reserves some extents for clean-up and other internal
+        always reserves some extents for cleanup and other internal
         purposes; these reserved extents are not included in the free
         space.
       </para>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/installing.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -15029,9 +15029,9 @@
         <para>
           Some customers have had problems on BSDI 4.0.1 that the
           <command>mysqld</command> binary after a while can't open
-          tables. This is because some library/system-related bug causes
-          <command>mysqld</command> to change current directory without
-          having asked for that to happen.
+          tables. This occurs because some library/system-related bug
+          causes <command>mysqld</command> to change current directory
+          without having asked for that to happen.
         </para>
 
         <para>

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1719,8 +1719,8 @@
 
       <para>
         For subsequent <command>ndbd</command> starts, you will
-        generally <emphasis role="bold">not</emphasis> want to use this
-        option:
+        generally <emphasis role="bold">not</emphasis> want to use the
+        <option>--initial</option> option:
       </para>
 
 <programlisting>
@@ -1728,11 +1728,11 @@
 </programlisting>
 
       <para>
-        This is because the <option>--initial</option> option will
-        delete all existing data and log files (as well as all table
-        metadata) for this data node and create new ones. One exception
-        to this rule is when restarting the cluster and restoring from
-        backup after adding new data nodes.
+        The reason for this is that the <option>--initial</option>
+        option will delete all existing data and log files (as well as
+        all table metadata) for this data node and create new ones. One
+        exception to this rule is when restarting the cluster and
+        restoring from backup after adding new data nodes.
       </para>
 
       <remark role="todo">
@@ -2593,8 +2593,9 @@
         <para>
           For each parameter it is possible to use <literal>k</literal>,
           <literal>M</literal>, or <literal>G</literal> as a suffix to
-          indicate units of 1024, 1024*1024, or 1024*1024*1024. (For
-          example, <literal>100k</literal> means 100 * 1024 = 102400.)
+          indicate units of 1024, 1024&times;1024, or
+          1024&times;1024&times;1024. (For example,
+          <literal>100k</literal> means 100 &times; 1024 = 102400.)
           Parameters and values are currently case-sensitive.
         </para>
 
@@ -3291,9 +3292,9 @@
               <filename>ndb/src/kernel/blocks/Dbtc/Dbtc.hpp</filename>)
               set to 4000*128 bytes (500KB). A similar buffer for key
               info, <literal>ZDATABUF_FILESIZE</literal> (also in
-              <filename>Dbtc.hpp</filename>) contains 4000 * 16 = 62.5KB
-              of buffer space. <literal>Dbtc</literal> is the module
-              which handles transaction coordination.
+              <filename>Dbtc.hpp</filename>) contains 4000 &times; 16 =
+              62.5KB of buffer space. <literal>Dbtc</literal> is the
+              module which handles transaction coordination.
             </para>
           </listitem>
 
@@ -10484,9 +10485,10 @@
           Yes, it is possible to use DNS and DHCP for cluster hosts.
           However, if your application requires <quote>five
           nines</quote> availability, we recommend using fixed IP
-          addresses. This is because making communication between
-          Cluster hosts dependent on such services introduces additional
-          points of failure, and the fewer of these, the better.
+          addresses. Making communication between Cluster hosts
+          dependent on services such as DNS and DHCP introduces
+          additional points of failure, and the fewer of these, the
+          better.
         </para>
       </listitem>
 

Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/optimization.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1853,9 +1853,9 @@
         Cartesian product of all the tables; that is, every combination
         of rows. This takes quite a long time, because the product of
         the number of rows in each table must be examined. For the case
-        at hand, this product is <literal>74 * 2135 * 74 * 3872 =
-        45,268,558,720</literal> rows. If the tables were bigger, you
-        can only imagine how long it would take.
+        at hand, this product is <literal>74 &times; 2135 &times; 74
+        &times; 3872 = 45,268,558,720</literal> rows. If the tables were
+        bigger, you can only imagine how long it would take.
       </para>
 
       <para>
@@ -2009,8 +2009,8 @@
         you can estimate that, using B-tree indexes, you need this many
         seeks to find a row:
         <literal>log(<replaceable>row_count</replaceable>) /
-        log(<replaceable>index_block_length</replaceable> / 3 * 2 /
-        (<replaceable>index_length</replaceable> +
+        log(<replaceable>index_block_length</replaceable> / 3 &times; 2
+        / (<replaceable>index_length</replaceable> +
         <replaceable>data_pointer_length</replaceable>)) + 1</literal>.
       </para>
 
@@ -2023,10 +2023,10 @@
       </para>
 
       <para>
-        This index would require storage of about 500,000 * 7 * 3/2 =
-        5.2MB (assuming a typical index buffer fill ratio of 2/3), so
-        you probably have much of the index in memory and so need only
-        one or two calls to read data to find the row.
+        This index would require storage of about 500,000 &times; 7
+        &times; 3/2 = 5.2MB (assuming a typical index buffer fill ratio
+        of 2/3), so you probably have much of the index in memory and so
+        need only one or two calls to read data to find the row.
       </para>
 
       <para>
@@ -6101,7 +6101,7 @@
       <para>
         <literal>InnoDB</literal> uses row locks and
         <literal>BDB</literal> uses page locks. For these two storage
-        engines, deadlocks are possible. This is because
+        engines, deadlocks are possible. This occurs because
         <literal>InnoDB</literal> automatically acquires row locks and
         <literal>BDB</literal> acquires page locks during the processing
         of SQL statements, not at the start of the transaction.

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/problems.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -3740,10 +3740,10 @@
 
       <para>
         Standard SQL doesn't allow you to refer to a column alias in a
-        <literal>WHERE</literal> clause. This is because when the
-        <literal>WHERE</literal> code is executed, the column value may
-        not yet be determined. For example, the following query is
-        illegal:
+        <literal>WHERE</literal> clause. This restriction is imposed
+        because when the <literal>WHERE</literal> code is executed, the
+        column value may not yet be determined. For example, the
+        following query is illegal:
       </para>
 
 <programlisting>
@@ -4378,7 +4378,7 @@
         If you use <literal>ALTER TABLE</literal> on a transactional
         table or if you are using Windows or OS/2, <literal>ALTER
         TABLE</literal> unlocks the table if you had done a
-        <literal>LOCK TABLE</literal> on it. This is because
+        <literal>LOCK TABLE</literal> on it. This is done because
         <literal>InnoDB</literal> and these operating systems cannot
         drop a table that is in use.
       </para>

Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/sql-syntax.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1171,9 +1171,9 @@
         index type. However, <literal>USING</literal> is the preferred
         form. In addition, the index name that precedes the index type
         in the index specification syntax is not optional with
-        <literal>TYPE</literal>. This is because, unlike
-        <literal>USING</literal>, <literal>TYPE</literal> is not a
-        reserved word and thus is interpreted as an index name.
+        <literal>TYPE</literal>: Unlike <literal>USING</literal>,
+        <literal>TYPE</literal> is not a reserved word and thus is
+        interpreted as an index name.
       </para>
 
       <para>
@@ -18608,9 +18608,9 @@
           <option>--replicate-*-do-*</option> and
           <option>--replicate-*-ignore-*</option> options are honored.
           <option>--replicate-rewrite-db</option> is
-          <emphasis>not</emphasis> taken into account. This is because a
-          user could, with this option, set up a non-unique mapping such
-          as <option>--replicate-rewrite-db=db1-&gt;db3</option> and
+          <emphasis>not</emphasis> taken into account because a user
+          could use this option to set up a non-unique mapping such as
+          <option>--replicate-rewrite-db=db1-&gt;db3</option> and
           <option>--replicate-rewrite-db=db2-&gt;db3</option>, which
           would confuse the slave when loading tables from the master.
         </para>

Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.0/storage-engines.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2015,7 +2015,7 @@
             TABLE</literal> to add a non-unique index on the
             <literal>MERGE</literal> table, the index ordering is
             different for the tables if there was already a non-unique
-            index in the underlying table. (This is because
+            index in the underlying table. (This happens because
             <literal>ALTER TABLE</literal> puts
             <literal>UNIQUE</literal> indexes before non-unique indexes
             to facilitate rapid detection of duplicate keys.)

Modified: trunk/refman-5.1/apis.xml
===================================================================
--- trunk/refman-5.1/apis.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/apis.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2037,7 +2037,7 @@
         <para>
           Note that when you use a <literal>REPLACE</literal> command,
           <literal>mysql_affected_rows()</literal> returns 2 if the new
-          row replaced an old row. This is because in this case one row
+          row replaced an old row, because in this case one row
           was inserted after the duplicate was deleted.
         </para>
 

Modified: trunk/refman-5.1/connector-odbc.xml
===================================================================
--- trunk/refman-5.1/connector-odbc.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/connector-odbc.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -5368,7 +5368,7 @@
       <title>&title-nocursor;</title>
 
       <para>
-        This is because the application is using old MyODBC 2.50
+        This occurs because the application is using old MyODBC 2.50
         version, and it did not set the cursor name explicitly through
         SQLSetCursorName. The fix is to upgrade to MyODBC 3.51 version.
       </para>

Modified: trunk/refman-5.1/custom-engine.xml
===================================================================
--- trunk/refman-5.1/custom-engine.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/custom-engine.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2771,7 +2771,7 @@
       </para>
 
       <para>
-        When a COMMIT/ROLLBACK operation occurs (with <literal>bool
+        When a <literal>COMMIT</literal> or <literal>ROLLBACK</literal> operation occurs (with <literal>bool
         all</literal> set to <literal>true</literal>), all savepoints
         are assumed to be released. If the storage engine allocates
         resources for savepoints, it should free them.
@@ -5959,7 +5959,7 @@
       </para>
 
       <para>
-        Perform any needed clean-up; no outstanding updates are there at
+        Perform any needed cleanup; no outstanding updates are there at
         the moment.
       </para>
 

Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/data-types.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2560,7 +2560,7 @@
         use strings that have fewer than 6 characters. For example, if
         you specify <literal>'9903'</literal>, thinking that represents
         March, 1999, MySQL inserts a <quote>zero</quote> date value into
-        your table. This is because the year and month values are
+        your table. This occurs because the year and month values are
         <literal>99</literal> and <literal>03</literal>, but the day
         part is completely missing, so the value is not a legal date.
         However, you can explicitly specify a value of zero to represent

Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/database-administration.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -13131,7 +13131,7 @@
       <para>
         Administrative privileges (such as <literal>RELOAD</literal> or
         <literal>SHUTDOWN</literal>) are specified only in the
-        <literal>user</literal> table. This is because administrative
+        <literal>user</literal> table. The reason for this is that administrative
         operations are operations on the server itself and are not
         database-specific, so there is no reason to list these
         privileges in the other grant tables. In fact, to determine

Modified: trunk/refman-5.1/extending-mysql.xml
===================================================================
--- trunk/refman-5.1/extending-mysql.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/extending-mysql.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2516,7 +2516,7 @@
       <para>
         To create a function, you must have the
         <literal>INSERT</literal> and privilege for the
-        <literal>mysql</literal> database. This is because
+        <literal>mysql</literal> database. This is necessary because
         <literal>CREATE FUNCTION</literal> adds a row to the
         <literal>mysql.func</literal> system table that records the
         function's name, type, and shared library name. If you do not

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/innodb.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -913,7 +913,7 @@
         <literal>newraw</literal> immediately after the data file size
         in <literal>innodb_data_file_path</literal>. The partition must
         be at least as large as the size that you specify. Note that 1MB
-        in <literal>InnoDB</literal> is 1024 * 1024 bytes, whereas 1MB
+        in <literal>InnoDB</literal> is 1024 &times; 1024 bytes, whereas 1MB
         usually means 1,000,000 bytes in disk specifications.
       </para>
 
@@ -4378,7 +4378,7 @@
       </para>
 
       <para>
-        If an SQL statement returns an error, the commit/rollback
+        If an SQL statement returns an error, the commit or rollback
         behavior depends on the error. See
         <xref linkend="innodb-error-handling"/>.
       </para>
@@ -4473,7 +4473,7 @@
         transaction, all the locks of the transaction are released.
         However, if just a single SQL statement is rolled back as a
         result of an error, some of the locks set by the SQL statement
-        may be preserved. This is because <literal>InnoDB</literal>
+        may be preserved. This happens because <literal>InnoDB</literal>
         stores row locks in a format such it cannot know afterward which
         lock was set by which SQL statement.
       </para>
@@ -5418,7 +5418,7 @@
         If index records are inserted in a sequential order (ascending
         or descending), the resulting index pages are about 15/16 full.
         If records are inserted in a random order, the pages are from
-        1/2 to 15/16 full. If the fillfactor of an index page drops
+        1/2 to 15/16 full. If the fill factor of an index page drops
         below 1/2, <literal>InnoDB</literal> tries to contract the index
         tree to free the page.
       </para>
@@ -5718,7 +5718,7 @@
         issuing a <literal>SHOW TABLE STATUS</literal>,
         <literal>InnoDB</literal> reports the extents that are
         definitely free in the tablespace. <literal>InnoDB</literal>
-        always reserves some extents for clean-up and other internal
+        always reserves some extents for cleanup and other internal
         purposes; these reserved extents are not included in the free
         space.
       </para>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/installing.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -14341,7 +14341,7 @@
         <para>
           Some customers have had problems on BSDI 4.0.1 that the
           <command>mysqld</command> binary after a while can't open
-          tables. This is because some library/system-related bug causes
+          tables. This occurs because some library/system-related bug causes
           <command>mysqld</command> to change current directory without
           having asked for that to happen.
         </para>

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1719,7 +1719,7 @@
 
       <para>
         For subsequent <command>ndbd</command> starts, you will
-        generally <emphasis role="bold">not</emphasis> want to use this
+        generally <emphasis role="bold">not</emphasis> want to use the <option>--initial</option>
         option:
       </para>
 
@@ -1728,7 +1728,7 @@
 </programlisting>
 
       <para>
-        This is because the <option>--initial</option> option will
+        The reason for this is that the <option>--initial</option> option will
         delete all existing data and log files (as well as all table
         metadata) for this data node and create new ones. One exception
         to this rule is when restarting the cluster and restoring from
@@ -2593,8 +2593,8 @@
         <para>
           For each parameter it is possible to use <literal>k</literal>,
           <literal>M</literal>, or <literal>G</literal> as a suffix to
-          indicate units of 1024, 1024*1024, or 1024*1024*1024. (For
-          example, <literal>100k</literal> means 100 * 1024 = 102400.)
+          indicate units of 1024, 1024&times;1024, or 1024&times;1024&times;1024. (For
+          example, <literal>100k</literal> means 100 &times; 1024 = 102400.)
           Parameters and values are currently case-sensitive.
         </para>
 
@@ -3291,7 +3291,7 @@
               <filename>ndb/src/kernel/blocks/Dbtc/Dbtc.hpp</filename>)
               set to 4000*128 bytes (500KB). A similar buffer for key
               info, <literal>ZDATABUF_FILESIZE</literal> (also in
-              <filename>Dbtc.hpp</filename>) contains 4000 * 16 = 62.5KB
+              <filename>Dbtc.hpp</filename>) contains 4000 &times; 16 = 62.5KB
               of buffer space. <literal>Dbtc</literal> is the module
               which handles transaction coordination.
             </para>
@@ -12064,8 +12064,8 @@
           Yes, it is possible to use DNS and DHCP for cluster hosts.
           However, if your application requires <quote>five
           nines</quote> availability, we recommend using fixed IP
-          addresses. This is because making communication between
-          Cluster hosts dependent on such services introduces additional
+          addresses. Making communication between
+          Cluster hosts dependent on services such as DNS and DHCP introduces additional
           points of failure, and the fewer of these, the better.
         </para>
       </listitem>

Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/optimization.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1846,7 +1846,7 @@
         Cartesian product of all the tables; that is, every combination
         of rows. This takes quite a long time, because the product of
         the number of rows in each table must be examined. For the case
-        at hand, this product is <literal>74 * 2135 * 74 * 3872 =
+        at hand, this product is <literal>74 &times; 2135 &times; 74 &times; 3872 =
         45,268,558,720</literal> rows. If the tables were bigger, you
         can only imagine how long it would take.
       </para>
@@ -2002,7 +2002,7 @@
         you can estimate that, using B-tree indexes, you need this many
         seeks to find a row:
         <literal>log(<replaceable>row_count</replaceable>) /
-        log(<replaceable>index_block_length</replaceable> / 3 * 2 /
+        log(<replaceable>index_block_length</replaceable> / 3 &times; 2 /
         (<replaceable>index_length</replaceable> +
         <replaceable>data_pointer_length</replaceable>)) + 1</literal>.
       </para>
@@ -2016,7 +2016,7 @@
       </para>
 
       <para>
-        This index would require storage of about 500,000 * 7 * 3/2 =
+        This index would require storage of about 500,000 &times; 7 &times; 3/2 =
         5.2MB (assuming a typical index buffer fill ratio of 2/3), so
         you probably have much of the index in memory and so need only
         one or two calls to read data to find the row.
@@ -6071,7 +6071,7 @@
       <para>
         <literal>InnoDB</literal> uses row locks and
         <literal>BDB</literal> uses page locks. For these two storage
-        engines, deadlocks are possible. This is because
+        engines, deadlocks are possible. This occurs because
         <literal>InnoDB</literal> automatically acquires row locks and
         <literal>BDB</literal> acquires page locks during the processing
         of SQL statements, not at the start of the transaction.

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/partitioning.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -496,7 +496,7 @@
 </programlisting>
 
     <para>
-      This is because MySQL sees no difference between the partition
+      Failure occurs because MySQL sees no difference between the partition
       names <literal>mypart</literal> and <literal>MyPart</literal>.
     </para>
 
@@ -919,7 +919,7 @@
 </programlisting>
 
       <para>
-        This is because the <literal>store_id</literal> column value
+        Failure occurs because the <literal>store_id</literal> column value
         <literal>21</literal> is not found in any of the value lists
         used to define partitions <literal>pNorth</literal>,
         <literal>pEast</literal>, <literal>pWest</literal>, or

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/problems.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -3734,7 +3734,7 @@
 
       <para>
         Standard SQL doesn't allow you to refer to a column alias in a
-        <literal>WHERE</literal> clause. This is because when the
+        <literal>WHERE</literal> clause. This restriction is imposed because when the
         <literal>WHERE</literal> code is executed, the column value may
         not yet be determined. For example, the following query is
         illegal:
@@ -4358,7 +4358,7 @@
         If you use <literal>ALTER TABLE</literal> on a transactional
         table or if you are using Windows or OS/2, <literal>ALTER
         TABLE</literal> unlocks the table if you had done a
-        <literal>LOCK TABLE</literal> on it. This is because
+        <literal>LOCK TABLE</literal> on it. This is done because
         <literal>InnoDB</literal> and these operating systems cannot
         drop a table that is in use.
       </para>

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/sql-syntax.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -1392,7 +1392,7 @@
         index type. However, <literal>USING</literal> is the preferred
         form. In addition, the index name that precedes the index type
         in the index specification syntax is not optional with
-        <literal>TYPE</literal>. This is because, unlike
+        <literal>TYPE</literal>: Unlike
         <literal>USING</literal>, <literal>TYPE</literal> is not a
         reserved word and thus is interpreted as an index name.
       </para>
@@ -19070,8 +19070,8 @@
           <option>--replicate-*-do-*</option> and
           <option>--replicate-*-ignore-*</option> options are honored.
           <option>--replicate-rewrite-db</option> is
-          <emphasis>not</emphasis> taken into account. This is because a
-          user could, with this option, set up a non-unique mapping such
+          <emphasis>not</emphasis> taken into account because a
+          user could use this option to set up a non-unique mapping such
           as <option>--replicate-rewrite-db=db1-&gt;db3</option> and
           <option>--replicate-rewrite-db=db2-&gt;db3</option>, which
           would confuse the slave when loading tables from the master.

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-5.1/storage-engines.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -2015,7 +2015,7 @@
             TABLE</literal> to add a non-unique index on the
             <literal>MERGE</literal> table, the index ordering is
             different for the tables if there was already a non-unique
-            index in the underlying table. (This is because
+            index in the underlying table. (This happens because
             <literal>ALTER TABLE</literal> puts
             <literal>UNIQUE</literal> indexes before non-unique indexes
             to facilitate rapid detection of duplicate keys.)

Modified: trunk/refman-common/news-4.0.xml
===================================================================
--- trunk/refman-common/news-4.0.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-common/news-4.0.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -4602,8 +4602,8 @@
         <para>
           <command>mysqld</command> now only adds an interrupt handler
           for the <literal>SIGINT</literal> signal if you start it with
-          the new <option>--gdb</option> option. This is because some
-          MySQL users encountered strange problems when they
+          the new <option>--gdb</option> option. This is done because
+          some MySQL users encountered strange problems when they
           accidentally sent <literal>SIGINT</literal> to
           <command>mysqld</command> threads.
         </para>

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-common/news-5.0.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -5978,9 +5978,9 @@
         <para>
           Where a <literal>GROUP BY</literal> query uses a grouping
           column from the query's <literal>SELECT</literal> clause,
-          MySQL now issues a warning. This is because the SQL standard
-          states that any grouping column must unambiguously reference a
-          column of the table resulting from the query's
+          MySQL now issues a warning. This is done because the SQL
+          standard states that any grouping column must unambiguously
+          reference a column of the table resulting from the query's
           <literal>FROM</literal> clause, and allowing columns from the
           <literal>SELECT</literal> clause to be used as grouping
           columns is a MySQL extension to the standard.

Modified: trunk/refman-common/news-innodb.xml
===================================================================
--- trunk/refman-common/news-innodb.xml	2006-01-09 02:09:54 UTC (rev 730)
+++ trunk/refman-common/news-innodb.xml	2006-01-09 02:57:50 UTC (rev 731)
@@ -282,7 +282,7 @@
 
       <listitem>
         <para>
-          'Gap' type row locks without the
+          <quote>Gap</quote> type row locks without the
           <literal>LOCK_INSERT_INTENTION</literal> flag do not need to
           wait for anything. This is because different users can have
           conflicting lock types on gaps. This change reduces

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