List:Commits« Previous MessageNext Message »
From:paul Date:January 6 2006 6:49am
Subject:svn commit - mysqldoc@docsrva: r705 - in trunk: . refman refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-06 07:49:44 +0100 (Fri, 06 Jan 2006)
New Revision: 705

Log:
 r5912@frost:  paul | 2006-01-06 00:49:22 -0600
 Fix typos.


Modified:
   trunk/
   trunk/refman-4.1/introduction.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-4.1/optimization.xml
   trunk/refman-4.1/porting.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/renamed-nodes.txt
   trunk/refman-4.1/storage-engines.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.0/introduction.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.0/optimization.xml
   trunk/refman-5.0/porting.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/renamed-nodes.txt
   trunk/refman-5.0/replication.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.0/storage-engines.xml
   trunk/refman-5.1/installing.xml
   trunk/refman-5.1/ndbcluster.xml
   trunk/refman-5.1/optimization.xml
   trunk/refman-5.1/porting.xml
   trunk/refman-5.1/problems.xml
   trunk/refman-5.1/renamed-nodes.txt
   trunk/refman-5.1/replication.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-5.1/storage-engines.xml
   trunk/refman-common/bug-reports.xml
   trunk/refman-common/news-4.1.xml
   trunk/refman-common/news-5.0.xml
   trunk/refman-common/news-connector-j.xml
   trunk/refman-common/titles.en.ent
   trunk/refman/connector-j.xml
   trunk/refman/introduction.xml
   trunk/refman/mysql-optimization.xml
   trunk/refman/ndbcluster.xml
   trunk/refman/porting.xml
   trunk/refman/problems.xml
   trunk/refman/sql-syntax.xml
   trunk/refman/storage-engines.xml


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

Modified: trunk/refman/connector-j.xml
===================================================================
--- trunk/refman/connector-j.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/connector-j.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -6849,7 +6849,7 @@
      - Implemented getBigDecimal() without scale component
        for JDBC2.
 
-     - Fixed composite key problem with updateable result sets.
+     - Fixed composite key problem with updatable result sets.
 
      - Added detection of -/+INF for doubles.
 

Modified: trunk/refman/introduction.xml
===================================================================
--- trunk/refman/introduction.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/introduction.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1117,7 +1117,7 @@
         <listitem>
           <para>
             <emphasis role="bold">Views</emphasis>: MySQL 5.0 added
-            support for named, updateable views. See
+            support for named, updatable views. See
             <xref linkend="views"/> and
             <xref linkend="ansi-diff-views"/>.
           </para>

Modified: trunk/refman/mysql-optimization.xml
===================================================================
--- trunk/refman/mysql-optimization.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/mysql-optimization.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -9752,7 +9752,7 @@
             <para>
               Symlinking can be accomplished manually from the command
               line using <command>ln -s</command> if
-              <command>mysqld</command> is not running. Aternativly, you
+              <command>mysqld</command> is not running. Alternatively, you
               can instruct a running MySQL server to perform the
               symlinking by using the <literal>DATA DIRECTORY</literal>
               and <literal>INDEX DIRECTORY</literal> options to

Modified: trunk/refman/ndbcluster.xml
===================================================================
--- trunk/refman/ndbcluster.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/ndbcluster.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -571,7 +571,7 @@
             MySQL Cluster is to run your Cluster on a protected network.
             If you intend to use MySQL Cluster for Web applications, the
             cluster should definitely reside behind your firewall and
-            not in your network's De-Militarised Zone
+            not in your network's De-Militarized Zone
             (<ulink url="http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ</ulink>)
             or elsewhere.
           </para>
@@ -2754,7 +2754,7 @@
               This parameter defines the amount of space available to
               store database records. The entire amount will be
               allocated in memory, so it is extremely important that the
-              machine has sufficient physical memory to accomodate this
+              machine has sufficient physical memory to accommodate this
               value.
             </para>
 
@@ -3097,7 +3097,7 @@
             <para>
               Read queries which set locks also cause operation records
               to be created. Some extra space is allocated within
-              individual nodes to accomodate cases where the
+              individual nodes to accommodate cases where the
               distribution is not perfect over the nodes.
             </para>
 
@@ -3432,7 +3432,7 @@
             <para>
               If the checkpointing is slow and there are so many writes
               to the database that the log files are full and the log
-              tail cannot be cut without jeapo rdising recovery, then
+              tail cannot be cut without jeopardizing recovery, then
               all updating transactions will be aborted with internal
               error code 410, or <literal>Out of log file space
               temporarily</literal>. This condition will prevail until a
@@ -4134,7 +4134,7 @@
 
             <para>
               Controls the number of index memory pages that can be
-              written to disk during the loca checkpoint phase of a node
+              written to disk during the local checkpoint phase of a node
               restart.
             </para>
 
@@ -4652,9 +4652,9 @@
             </para>
 
             <para>
-              The spped at which queries are performed can vary by more
+              The speed at which queries are performed can vary by more
               than 40% depending upon how this parameter is set. In
-              future releases, the MySQL Server will make educated
+              future releases, MySQL Server will make educated
               guesses on how to set parameters relating to batch size,
               based on the query type.
             </para>

Modified: trunk/refman/porting.xml
===================================================================
--- trunk/refman/porting.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/porting.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -732,9 +732,9 @@
 
     </section>
 
-    <section id="reproduceable-test-case">
+    <section id="reproducible-test-case">
 
-      <title>&title-reproduceable-test-case;</title>
+      <title>&title-reproducible-test-case;</title>
 
       <para>
         If you get corrupted tables or if <command>mysqld</command>
@@ -824,7 +824,7 @@
           <para>
             If the tables are corrupted again or you can get
             <command>mysqld</command> to die with the above command, you
-            have found reproduceable bug that should be easy to fix! FTP
+            have found reproducible bug that should be easy to fix! FTP
             the tables and the binary log to
             <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/> and
             enter it into our bugs system at

Modified: trunk/refman/problems.xml
===================================================================
--- trunk/refman/problems.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/problems.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1147,7 +1147,7 @@
             tables involved were checked with <literal>CHECK
             TABLE</literal> before you ran the query, can you provide a
             reproducible test case? See
-            <xref linkend="reproduceable-test-case"/>.
+            <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 
@@ -2781,7 +2781,7 @@
         <listitem>
           <para>
             Try to make a test case that we can use to repeat the
-            problem. See <xref linkend="reproduceable-test-case"/>.
+            problem. See <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 

Modified: trunk/refman/sql-syntax.xml
===================================================================
--- trunk/refman/sql-syntax.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/sql-syntax.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -5743,7 +5743,7 @@
 
       <para>
         The <literal>SET</literal> clause can be used to supply values
-        not derived from the input file. THe following statement sets
+        not derived from the input file. The following statement sets
         <literal>column3</literal> to the current date and time:
       </para>
 

Modified: trunk/refman/storage-engines.xml
===================================================================
--- trunk/refman/storage-engines.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman/storage-engines.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1450,7 +1450,7 @@
           corruption may have occurred during normal operation, which is
           a bug. You should try to create a reproducible test case that
           demonstrates the problem. See <xref linkend="crashing"/> and
-          <xref linkend="reproduceable-test-case"/>.
+          <xref linkend="reproducible-test-case"/>.
         </para>
 
       </section>

Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/introduction.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1079,7 +1079,7 @@
         <listitem>
           <para>
             <emphasis role="bold">Views</emphasis>: MySQL 5.0 added
-            support for named, updateable views.
+            support for named, updatable views.
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -572,7 +572,7 @@
             MySQL Cluster is to run your Cluster on a protected network.
             If you intend to use MySQL Cluster for Web applications, the
             cluster should definitely reside behind your firewall and
-            not in your network's De-Militarised Zone
+            not in your network's De-Militarized Zone
             (<ulink url="http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ</ulink>)
             or elsewhere.
           </para>
@@ -2778,7 +2778,7 @@
               This parameter defines the amount of space available for
               storing database records. The entire amount is allocated
               in memory, so it is extremely important that the machine
-              has sufficient physical memory to accomodate this value.
+              has sufficient physical memory to accommodate this value.
             </para>
 
             <para>
@@ -3120,7 +3120,7 @@
             <para>
               Read queries which set locks also cause operation records
               to be created. Some extra space is allocated within
-              individual nodes to accomodate cases where the
+              individual nodes to accommodate cases where the
               distribution is not perfect over the nodes.
             </para>
 
@@ -3464,7 +3464,7 @@
             <para>
               If the checkpointing is slow and there are so many writes
               to the database that the log files are full and the log
-              tail cannot be cut without jeapo rdising recovery, then
+              tail cannot be cut without jeopardizing recovery, then
               all updating transactions will be aborted with internal
               error code 410, or <literal>Out of log file space
               temporarily</literal>. This condition will prevail until a
@@ -4197,7 +4197,7 @@
 
             <para>
               Controls the number of index memory pages that can be
-              written to disk during the loca checkpoint phase of a node
+              written to disk during the local checkpoint phase of a node
               restart.
             </para>
 
@@ -4726,9 +4726,9 @@
             </para>
 
             <para>
-              The spped at which queries are performed can vary by more
+              The speed at which queries are performed can vary by more
               than 40% depending upon how this parameter is set. In
-              future releases, the MySQL Server will make educated
+              future releases, MySQL Server will make educated
               guesses on how to set parameters relating to batch size,
               based on the query type.
             </para>

Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/optimization.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -8247,7 +8247,7 @@
             <para>
               Symlinking can be accomplished manually from the command
               line using <command>ln -s</command> if
-              <command>mysqld</command> is not running. Aternativly, you
+              <command>mysqld</command> is not running. Alternatively, you
               can instruct a running MySQL server to perform the
               symlinking by using the <literal>DATA DIRECTORY</literal>
               and <literal>INDEX DIRECTORY</literal> options to

Modified: trunk/refman-4.1/porting.xml
===================================================================
--- trunk/refman-4.1/porting.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/porting.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -735,9 +735,9 @@
 
     </section>
 
-    <section id="reproduceable-test-case">
+    <section id="reproducible-test-case">
 
-      <title>&title-reproduceable-test-case;</title>
+      <title>&title-reproducible-test-case;</title>
 
       <para>
         If you get corrupted tables or if <command>mysqld</command>
@@ -827,7 +827,7 @@
           <para>
             If the tables are corrupted again or you can get
             <command>mysqld</command> to die with the above command, you
-            have found reproduceable bug that should be easy to fix! FTP
+            have found reproducible bug that should be easy to fix! FTP
             the tables and the binary log to
             <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/> and
             enter it into our bugs system at

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/problems.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1159,7 +1159,7 @@
             tables involved were checked with <literal>CHECK
             TABLE</literal> before you ran the query, can you provide a
             reproducible test case? See
-            <xref linkend="reproduceable-test-case"/>.
+            <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 
@@ -2788,7 +2788,7 @@
         <listitem>
           <para>
             Try to make a test case that we can use to repeat the
-            problem. See <xref linkend="reproduceable-test-case"/>.
+            problem. See <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-4.1/renamed-nodes.txt
===================================================================
--- trunk/refman-4.1/renamed-nodes.txt	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/renamed-nodes.txt	2006-01-06 06:49:44 UTC (rev 705)
@@ -91,3 +91,4 @@
 asking-questions bug-reports
 mailing-list mailing-lists
 answering-questions mailing-list-use
+reproduceable-test-case reproducible-test-case

Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-4.1/storage-engines.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1432,7 +1432,7 @@
           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
-          <xref linkend="reproduceable-test-case"/>.
+          <xref linkend="reproducible-test-case"/>.
         </para>
 
       </section>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/installing.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -32,7 +32,7 @@
       <para>
         <emphasis role="bold">Determine whether your platform is
         supported.</emphasis> Please note that not all supported systems
-        are equally suitable for running MySQL. On some pltforms it is
+        are equally suitable for running MySQL. On some platforms it is
         much more robust and efficient than others. See
         <xref linkend="which-os"/>, for details.
       </para>

Modified: trunk/refman-5.0/introduction.xml
===================================================================
--- trunk/refman-5.0/introduction.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/introduction.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -481,7 +481,7 @@
         <listitem>
           <para>
             <emphasis role="bold">Views</emphasis>: MySQL 5.0 added
-            support for named, updateable views. See
+            support for named, updatable views. See
             <xref linkend="views"/>, and
             <xref linkend="ansi-diff-views"/>.
           </para>

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -578,7 +578,7 @@
             MySQL Cluster is to run your Cluster on a protected network.
             If you intend to use MySQL Cluster for Web applications, the
             cluster should definitely reside behind your firewall and
-            not in your network's De-Militarised Zone
+            not in your network's De-Militarized Zone
             (<ulink url="http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ</ulink>)
             or elsewhere.
           </para>
@@ -2776,7 +2776,7 @@
               This parameter defines the amount of space available for
               storing database records. The entire amount is allocated
               in memory, so it is extremely important that the machine
-              has sufficient physical memory to accomodate this value.
+              has sufficient physical memory to accommodate this value.
             </para>
 
             <remark role="todo">
@@ -3126,7 +3126,7 @@
             <para>
               Read queries which set locks also cause operation records
               to be created. Some extra space is allocated within
-              individual nodes to accomodate cases where the
+              individual nodes to accommodate cases where the
               distribution is not perfect over the nodes.
             </para>
 
@@ -3474,7 +3474,7 @@
             <para>
               If the checkpointing is slow and there are so many writes
               to the database that the log files are full and the log
-              tail cannot be cut without jeapo rdising recovery, then
+              tail cannot be cut without jeopardizing recovery, then
               all updating transactions will be aborted with internal
               error code 410, or <literal>Out of log file space
               temporarily</literal>. This condition will prevail until a
@@ -4211,7 +4211,7 @@
 
             <para>
               Controls the number of index memory pages that can be
-              written to disk during the loca checkpoint phase of a node
+              written to disk during the local checkpoint phase of a node
               restart.
             </para>
 
@@ -4739,9 +4739,9 @@
             </para>
 
             <para>
-              The spped at which queries are performed can vary by more
+              The speed at which queries are performed can vary by more
               than 40% depending upon how this parameter is set. In
-              future releases, the MySQL Server will make educated
+              future releases, MySQL Server will make educated
               guesses on how to set parameters relating to batch size,
               based on the query type.
             </para>

Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/optimization.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -9801,7 +9801,7 @@
             <para>
               Symlinking can be accomplished manually from the command
               line using <literal>ln -s</literal> if
-              <command>mysqld</command> is not running. Aternativly, you
+              <command>mysqld</command> is not running. Alternatively, you
               can instruct a running MySQL server to perform the
               symlinking by using the <literal>DATA DIRECTORY</literal>
               and <literal>INDEX DIRECTORY</literal> options to

Modified: trunk/refman-5.0/porting.xml
===================================================================
--- trunk/refman-5.0/porting.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/porting.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -735,9 +735,9 @@
 
     </section>
 
-    <section id="reproduceable-test-case">
+    <section id="reproducible-test-case">
 
-      <title>&title-reproduceable-test-case;</title>
+      <title>&title-reproducible-test-case;</title>
 
       <para>
         If you get corrupted tables or if <command>mysqld</command>
@@ -827,7 +827,7 @@
           <para>
             If the tables are corrupted again or you can get
             <command>mysqld</command> to die with the above command, you
-            have found reproduceable bug that should be easy to fix! FTP
+            have found reproducible bug that should be easy to fix! FTP
             the tables and the binary log to
             <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/> and
             enter it into our bugs system at

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/problems.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1159,7 +1159,7 @@
             tables involved were checked with <literal>CHECK
             TABLE</literal> before you ran the query, can you provide a
             reproducible test case? See
-            <xref linkend="reproduceable-test-case"/>.
+            <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 
@@ -2755,7 +2755,7 @@
         <listitem>
           <para>
             Try to make a test case that we can use to repeat the
-            problem. See <xref linkend="reproduceable-test-case"/>.
+            problem. See <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.0/renamed-nodes.txt
===================================================================
--- trunk/refman-5.0/renamed-nodes.txt	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/renamed-nodes.txt	2006-01-06 06:49:44 UTC (rev 705)
@@ -388,3 +388,4 @@
 asking-questions bug-reports
 mailing-list mailing-lists
 answering-questions mailing-list-use
+reproduceable-test-case reproducible-test-case

Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/replication.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -2049,7 +2049,7 @@
           However, when a second connection updates the
           non-transactional table before the first connection's
           transaction is complete, statements can be logged out of
-          orderr, because the second connection's update is written
+          order, because the second connection's update is written
           immediately after it is performed, regardless of the state of
           the transaction being performed by the first connection.
         </para>

Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/sql-syntax.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -5645,7 +5645,7 @@
 
       <para>
         The <literal>SET</literal> clause can be used to supply values
-        not derived from the input file. THe following statement sets
+        not derived from the input file. The following statement sets
         <literal>column3</literal> to the current date and time:
       </para>
 

Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.0/storage-engines.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1455,7 +1455,7 @@
           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
-          <xref linkend="reproduceable-test-case"/>.
+          <xref linkend="reproducible-test-case"/>.
         </para>
 
       </section>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/installing.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -32,7 +32,7 @@
       <para>
         <emphasis role="bold">Determine whether your platform is
         supported.</emphasis> Please note that not all supported systems
-        are equally suitable for running MySQL. On some pltforms it is
+        are equally suitable for running MySQL. On some platforms it is
         much more robust and efficient than others. See
         <xref linkend="which-os"/>, for details.
       </para>

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -578,7 +578,7 @@
             MySQL Cluster is to run your Cluster on a protected network.
             If you intend to use MySQL Cluster for Web applications, the
             cluster should definitely reside behind your firewall and
-            not in your network's De-Militarised Zone
+            not in your network's De-Militarized Zone
             (<ulink url="http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm">DMZ</ulink>)
             or elsewhere.
           </para>
@@ -2776,7 +2776,7 @@
               This parameter defines the amount of space available for
               storing database records. The entire amount is allocated
               in memory, so it is extremely important that the machine
-              has sufficient physical memory to accomodate this value.
+              has sufficient physical memory to accommodate this value.
             </para>
 
             <remark role="todo">
@@ -3126,7 +3126,7 @@
             <para>
               Read queries which set locks also cause operation records
               to be created. Some extra space is allocated within
-              individual nodes to accomodate cases where the
+              individual nodes to accommodate cases where the
               distribution is not perfect over the nodes.
             </para>
 
@@ -3474,7 +3474,7 @@
             <para>
               If the checkpointing is slow and there are so many writes
               to the database that the log files are full and the log
-              tail cannot be cut without jeapo rdising recovery, then
+              tail cannot be cut without jeopardizing recovery, then
               all updating transactions will be aborted with internal
               error code 410, or <literal>Out of log file space
               temporarily</literal>. This condition will prevail until a
@@ -4211,7 +4211,7 @@
 
             <para>
               Controls the number of index memory pages that can be
-              written to disk during the loca checkpoint phase of a node
+              written to disk during the local checkpoint phase of a node
               restart.
             </para>
 
@@ -4739,9 +4739,9 @@
             </para>
 
             <para>
-              The spped at which queries are performed can vary by more
+              The speed at which queries are performed can vary by more
               than 40% depending upon how this parameter is set. In
-              future releases, the MySQL Server will make educated
+              future releases, MySQL Server will make educated
               guesses on how to set parameters relating to batch size,
               based on the query type.
             </para>

Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/optimization.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -9904,7 +9904,7 @@
             <para>
               Symlinking can be accomplished manually from the command
               line using <literal>ln -s</literal> if
-              <command>mysqld</command> is not running. Aternativly, you
+              <command>mysqld</command> is not running. Alternatively, you
               can instruct a running MySQL server to perform the
               symlinking by using the <literal>DATA DIRECTORY</literal>
               and <literal>INDEX DIRECTORY</literal> options to

Modified: trunk/refman-5.1/porting.xml
===================================================================
--- trunk/refman-5.1/porting.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/porting.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -735,9 +735,9 @@
 
     </section>
 
-    <section id="reproduceable-test-case">
+    <section id="reproducible-test-case">
 
-      <title>&title-reproduceable-test-case;</title>
+      <title>&title-reproducible-test-case;</title>
 
       <para>
         If you get corrupted tables or if <command>mysqld</command>
@@ -827,7 +827,7 @@
           <para>
             If the tables are corrupted again or you can get
             <command>mysqld</command> to die with the above command, you
-            have found reproduceable bug that should be easy to fix! FTP
+            have found reproducible bug that should be easy to fix! FTP
             the tables and the binary log to
             <ulink url="ftp://ftp.mysql.com/pub/mysql/upload/"/> and
             enter it into our bugs system at

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/problems.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1159,7 +1159,7 @@
             tables involved were checked with <literal>CHECK
             TABLE</literal> before you ran the query, can you provide a
             reproducible test case? See
-            <xref linkend="reproduceable-test-case"/>.
+            <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 
@@ -2755,7 +2755,7 @@
         <listitem>
           <para>
             Try to make a test case that we can use to repeat the
-            problem. See <xref linkend="reproduceable-test-case"/>.
+            problem. See <xref linkend="reproducible-test-case"/>.
           </para>
         </listitem>
 

Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/renamed-nodes.txt	2006-01-06 06:49:44 UTC (rev 705)
@@ -91,3 +91,4 @@
 asking-questions bug-reports
 mailing-list mailing-lists
 answering-questions mailing-list-use
+reproduceable-test-case reproducible-test-case

Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/replication.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -2234,7 +2234,7 @@
           However, when a second connection updates the
           non-transactional table before the first connection's
           transaction is complete, statements can be logged out of
-          orderr, because the second connection's update is written
+          order, because the second connection's update is written
           immediately after it is performed, regardless of the state of
           the transaction being performed by the first connection.
         </para>

Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/sql-syntax.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -6226,7 +6226,7 @@
 
       <para>
         The <literal>SET</literal> clause can be used to supply values
-        not derived from the input file. THe following statement sets
+        not derived from the input file. The following statement sets
         <literal>column3</literal> to the current date and time:
       </para>
 

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-5.1/storage-engines.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -1455,7 +1455,7 @@
           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
-          <xref linkend="reproduceable-test-case"/>.
+          <xref linkend="reproducible-test-case"/>.
         </para>
 
       </section>

Modified: trunk/refman-common/bug-reports.xml
===================================================================
--- trunk/refman-common/bug-reports.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-common/bug-reports.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -199,7 +199,7 @@
     everything you did that led to the problem and describe, in exact
     detail, the problem itself. The best reports are those that include
     a full example showing how to reproduce the bug or problem. See
-    <xref linkend="reproduceable-test-case"/>.
+    <xref linkend="reproducible-test-case"/>.
   </para>
 
   <para>

Modified: trunk/refman-common/news-4.1.xml
===================================================================
--- trunk/refman-common/news-4.1.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-common/news-4.1.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -866,7 +866,7 @@
       <listitem>
         <para>
           <literal>PURGE MASTER LOGS</literal> statement that used
-          subselect for date crashed server. (Bug #10308)
+          subquery for date crashed server. (Bug #10308)
         </para>
       </listitem>
 
@@ -1799,7 +1799,7 @@
 
       <listitem>
         <para>
-          Mishanding of comparison for rows containg
+          Mishandling of comparison for rows containing
           <literal>NULL</literal> values against rows produced by an
           <literal>IN</literal> subquery could cause a server crash.
           (Bug #12392)
@@ -2400,7 +2400,7 @@
 
       <listitem>
         <para>
-          Prepared statement with subselects returned corrupt data. (Bug
+          Prepared statement with subqueries returned corrupt data. (Bug
           #11458)
         </para>
       </listitem>
@@ -2784,7 +2784,7 @@
 
       <listitem>
         <para>
-          An <literal>UPDATE</literal> query containing a subselect
+          An <literal>UPDATE</literal> query containing a subquery
           caused replication to fail. (Bug #9361)
         </para>
       </listitem>
@@ -6871,7 +6871,7 @@
       <listitem>
         <para>
           Fixed a bug that caused the server to crash on attempt to
-          execute a prepared statement with a subselect inside a boolean
+          execute a prepared statement with a subquery inside a boolean
           expression. (Bug #5987)
         </para>
       </listitem>

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-common/news-5.0.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -881,7 +881,7 @@
 
       <listitem>
         <para>
-          <literal>InnoDB</literal>: Activitity on an
+          <literal>InnoDB</literal>: Activity on an
           <literal>InnoDB</literal> table caused execution time for
           <literal>SHOW CREATE TABLE</literal> for the table to
           increase. (Bug #13762)
@@ -4444,7 +4444,7 @@
 
       <listitem>
         <para>
-          Mishanding of comparison for rows containg
+          Mishandling of comparison for rows containing
           <literal>NULL</literal> values against rows produced by an
           <literal>IN</literal> subquery could cause a server crash.
           (Bug #12392)
@@ -5902,7 +5902,7 @@
 
       <listitem>
         <para>
-          Combining cursors and subselects could cause server crash or
+          Combining cursors and subqueries could cause server crash or
           memory leaks. (Bug #10736)
         </para>
       </listitem>
@@ -9774,7 +9774,7 @@
       <listitem>
         <para>
           Selecting from an <literal>INFORMATION_SCHEMA</literal> table
-          combined with a subselect on an
+          combined with a subquery on an
           <literal>INFORMATION_SCHEMA</literal> table caused an error
           with the message <literal>Table
           <replaceable>tbl_name</replaceable> is corrupted</literal>.

Modified: trunk/refman-common/news-connector-j.xml
===================================================================
--- trunk/refman-common/news-connector-j.xml	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-common/news-connector-j.xml	2006-01-06 06:49:44 UTC (rev 705)
@@ -2331,7 +2331,7 @@
      - Implemented getBigDecimal() without scale component
        for JDBC2.
 
-     - Fixed composite key problem with updateable result sets.
+     - Fixed composite key problem with updatable result sets.
 
      - Added detection of -/+INF for doubles.
 

Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent	2006-01-06 05:50:20 UTC (rev 704)
+++ trunk/refman-common/titles.en.ent	2006-01-06 06:49:44 UTC (rev 705)
@@ -1439,7 +1439,7 @@
 <!ENTITY title-replication-upgrade-4-0 "Upgrading Replication to 4.0 or 4.1">
 <!ENTITY title-replication-upgrade-5-0 "Upgrading Replication to 5.0">
 <!ENTITY title-reporting-mysqltest-bugs "How to Report Bugs in the MySQL Test Suite">
-<!ENTITY title-reproduceable-test-case "Making a Test Case If You Experience Table Corruption">
+<!ENTITY title-reproducible-test-case "Making a Test Case If You Experience Table Corruption">
 <!ENTITY title-request-access "Access Control, Stage 2: Request Verification">
 <!ENTITY title-reserved-words "Treatment of Reserved Words in MySQL">
 <!ENTITY title-reset "<literal>RESET</literal> Syntax">

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