List:Commits« Previous MessageNext Message »
From:jon Date:July 8 2007 10:28pm
Subject:svn commit - mysqldoc@docsrva: r7045 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2
View as plain text  
Author: jstephens
Date: 2007-07-08 22:28:39 +0200 (Sun, 08 Jul 2007)
New Revision: 7045

Log:

Fixed grammar goof (Thanks, 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


Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml	2007-07-08 15:06:43 UTC (rev 7044)
+++ trunk/refman-4.1/se-innodb.xml	2007-07-08 20:28:39 UTC (rev 7045)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 765 bytes

@@ -4022,7 +4022,7 @@
       <para>
         A consistent read means that <literal>InnoDB</literal> uses
         multi-versioning to present to a query a snapshot of the
-        database at a point in time. The query see the changes made by
+        database at a point in time. The query sees the changes made by
         those transactions that committed before that point of time, and
         no changes made by later or uncommitted transactions. The
         exception to this rule is that the query sees the changes made


Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml	2007-07-08 15:06:43 UTC (rev 7044)
+++ trunk/refman-5.0/se-innodb.xml	2007-07-08 20:28:39 UTC (rev 7045)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 765 bytes

@@ -4017,7 +4017,7 @@
       <para>
         A consistent read means that <literal>InnoDB</literal> uses
         multi-versioning to present to a query a snapshot of the
-        database at a point in time. The query see the changes made by
+        database at a point in time. The query sees the changes made by
         those transactions that committed before that point of time, and
         no changes made by later or uncommitted transactions. The
         exception to this rule is that the query sees the changes made


Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml	2007-07-08 15:06:43 UTC (rev 7044)
+++ trunk/refman-5.1/se-innodb.xml	2007-07-08 20:28:39 UTC (rev 7045)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 765 bytes

@@ -4032,7 +4032,7 @@
       <para>
         A consistent read means that <literal>InnoDB</literal> uses
         multi-versioning to present to a query a snapshot of the
-        database at a point in time. The query see the changes made by
+        database at a point in time. The query sees the changes made by
         those transactions that committed before that point of time, and
         no changes made by later or uncommitted transactions. The
         exception to this rule is that the query sees the changes made


Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml	2007-07-08 15:06:43 UTC (rev 7044)
+++ trunk/refman-5.2/se-innodb.xml	2007-07-08 20:28:39 UTC (rev 7045)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 765 bytes

@@ -4032,7 +4032,7 @@
       <para>
         A consistent read means that <literal>InnoDB</literal> uses
         multi-versioning to present to a query a snapshot of the
-        database at a point in time. The query see the changes made by
+        database at a point in time. The query sees the changes made by
         those transactions that committed before that point of time, and
         no changes made by later or uncommitted transactions. The
         exception to this rule is that the query sees the changes made


Thread
svn commit - mysqldoc@docsrva: r7045 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.2jon8 Jul