svn commit - mysqldoc@docsrva: r7171 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2

[paul]

Author: paul
Date: 2007-07-22 00:41:16 +0200 (Sun, 22 Jul 2007)
New Revision: 7171

Log:
 r22889@frost:  paul | 2007-07-21 17:39:58 -0500
 Fix typos.  (Shane)


Modified:
   trunk/refman-4.1/se-innodb.xml
   trunk/refman-5.0/se-innodb.xml
   trunk/refman-5.1/se-innodb.xml
   trunk/refman-5.2/se-innodb.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27800
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22856
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27800
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22889
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941


Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml	2007-07-20 19:43:27 UTC (rev 7170)
+++ trunk/refman-4.1/se-innodb.xml	2007-07-21 22:41:16 UTC (rev 7171)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1607 bytes

@@ -1027,7 +1027,7 @@
     </indexterm>
 
     <para>
-      <emphasis role="bold">Note</emphasis>: If is not a good idea to
+      <emphasis role="bold">Note</emphasis>: It is not a good idea to
       configure <literal>InnoDB</literal> to use datafiles or logfiles
       on NFS volumes. Otherwise, the files might be locked by other
       processes and become unavailable for use by MySQL.

@@ -7058,7 +7058,7 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Warning</emphasis>: If is not a good
+          <emphasis role="bold">Warning</emphasis>: It is not a good
           idea to configure <literal>InnoDB</literal> to use datafiles
           or logfiles on NFS volumes. Otherwise, the files might be
           locked by other processes and become unavailable for use by

@@ -7379,7 +7379,7 @@
           The <literal>LOAD TABLE FROM MASTER</literal> statement for
           setting up replication slave servers does not work for
           <literal>InnoDB</literal> tables. A workaround is to alter the
-          table to <literal>MyISAM</literal> on the master, do then the
+          table to <literal>MyISAM</literal> on the master, then do the
           load, and after that alter the master table back to
           <literal>InnoDB</literal>. Do not do this if the tables use
           <literal>InnoDB</literal>-specific features such as foreign


Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml	2007-07-20 19:43:27 UTC (rev 7170)
+++ trunk/refman-5.0/se-innodb.xml	2007-07-21 22:41:16 UTC (rev 7171)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1605 bytes

@@ -215,7 +215,7 @@
     </indexterm>
 
     <para>
-      <emphasis role="bold">Note</emphasis>: If is not a good idea to
+      <emphasis role="bold">Note</emphasis>: It is not a good idea to
       configure <literal>InnoDB</literal> to use datafiles or logfiles
       on NFS volumes. Otherwise, the files might be locked by other
       processes and become unavailable for use by MySQL.

@@ -7161,7 +7161,7 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Warning</emphasis>: If is not a good
+          <emphasis role="bold">Warning</emphasis>: It is not a good
           idea to configure <literal>InnoDB</literal> to use datafiles
           or logfiles on NFS volumes. Otherwise, the files might be
           locked by other processes and become unavailable for use by

@@ -7460,7 +7460,7 @@
           The <literal>LOAD TABLE FROM MASTER</literal> statement for
           setting up replication slave servers does not work for
           <literal>InnoDB</literal> tables. A workaround is to alter the
-          table to <literal>MyISAM</literal> on the master, do then the
+          table to <literal>MyISAM</literal> on the master, then do the
           load, and after that alter the master table back to
           <literal>InnoDB</literal>. Do not do this if the tables use
           <literal>InnoDB</literal>-specific features such as foreign


Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml	2007-07-20 19:43:27 UTC (rev 7170)
+++ trunk/refman-5.1/se-innodb.xml	2007-07-21 22:41:16 UTC (rev 7171)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1605 bytes

@@ -215,7 +215,7 @@
     </indexterm>
 
     <para>
-      <emphasis role="bold">Note</emphasis>: If is not a good idea to
+      <emphasis role="bold">Note</emphasis>: It is not a good idea to
       configure <literal>InnoDB</literal> to use datafiles or logfiles
       on NFS volumes. Otherwise, the files might be locked by other
       processes and become unavailable for use by MySQL.

@@ -7196,7 +7196,7 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Warning</emphasis>: If is not a good
+          <emphasis role="bold">Warning</emphasis>: It is not a good
           idea to configure <literal>InnoDB</literal> to use datafiles
           or logfiles on NFS volumes. Otherwise, the files might be
           locked by other processes and become unavailable for use by

@@ -7480,7 +7480,7 @@
           The <literal>LOAD TABLE FROM MASTER</literal> statement for
           setting up replication slave servers does not work for
           <literal>InnoDB</literal> tables. A workaround is to alter the
-          table to <literal>MyISAM</literal> on the master, do then the
+          table to <literal>MyISAM</literal> on the master, then do the
           load, and after that alter the master table back to
           <literal>InnoDB</literal>. Do not do this if the tables use
           <literal>InnoDB</literal>-specific features such as foreign


Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml	2007-07-20 19:43:27 UTC (rev 7170)
+++ trunk/refman-5.2/se-innodb.xml	2007-07-21 22:41:16 UTC (rev 7171)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1605 bytes

@@ -215,7 +215,7 @@
     </indexterm>
 
     <para>
-      <emphasis role="bold">Note</emphasis>: If is not a good idea to
+      <emphasis role="bold">Note</emphasis>: It is not a good idea to
       configure <literal>InnoDB</literal> to use datafiles or logfiles
       on NFS volumes. Otherwise, the files might be locked by other
       processes and become unavailable for use by MySQL.

@@ -7196,7 +7196,7 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Warning</emphasis>: If is not a good
+          <emphasis role="bold">Warning</emphasis>: It is not a good
           idea to configure <literal>InnoDB</literal> to use datafiles
           or logfiles on NFS volumes. Otherwise, the files might be
           locked by other processes and become unavailable for use by

@@ -7480,7 +7480,7 @@
           The <literal>LOAD TABLE FROM MASTER</literal> statement for
           setting up replication slave servers does not work for
           <literal>InnoDB</literal> tables. A workaround is to alter the
-          table to <literal>MyISAM</literal> on the master, do then the
+          table to <literal>MyISAM</literal> on the master, then do the
           load, and after that alter the master table back to
           <literal>InnoDB</literal>. Do not do this if the tables use
           <literal>InnoDB</literal>-specific features such as foreign