List:Commits« Previous MessageNext Message »
From:paul.dubois Date:March 29 2011 3:49pm
Subject:svn commit - mysqldoc@oter02: r25600 - in trunk: . dynamic-docs/changelog dynamic-docs/glossary innodb-1.1 innodb-plugin-1.0 mysql-monitor-2.0 mysql-m...
View as plain text  
Author: pd221994
Date: 2011-03-29 17:49:23 +0200 (Tue, 29 Mar 2011)
New Revision: 25600

Log:
 r46442@dhcp-adc-twvpn-1-vpnpool-10-154-5-83:  paul | 2011-03-29 10:44:46 -0500
 a SQL -> an SQL


Modified:
   svk:merge
   trunk/dynamic-docs/changelog/connector-net.xml
   trunk/dynamic-docs/changelog/workbench.xml
   trunk/dynamic-docs/glossary/innodb.xml
   trunk/innodb-1.1/innodb-performance.xml
   trunk/innodb-1.1/plugin.ent
   trunk/innodb-plugin-1.0/innodb-performance.xml
   trunk/mysql-monitor-2.0/mem-reference-advgraph-core.xml
   trunk/mysql-monitor-2.1/mem-reference-advgraph-core.xml
   trunk/mysql-monitor-2.2/mem-reference-advgraph-core.xml
   trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml
   trunk/mysqldoc-guide/special-markup.xml
   trunk/mysqltest-1.0/writing-tests.xml
   trunk/mysqltest-2.0/writing-tests.xml
   trunk/refman-5.5/optimization.xml
   trunk/refman-5.6/optimization.xml
   trunk/refman-common/connector-cpp-core.xml
   trunk/refman-common/connector-net-tutorials-intro.xml
   trunk/workbench/data-modeling.xml
   trunk/workbench/forward-engineering.xml
   trunk/workbench/sql-development.xml

Property changes on: trunk
___________________________________________________________________

Modified: svk:merge
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes


Modified: trunk/dynamic-docs/changelog/connector-net.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-net.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/dynamic-docs/changelog/connector-net.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1010 bytes

@@ -422,7 +422,7 @@
     <message>
 
       <para>
-        When the tracing driver was used and a SQL statement was longer
+        When the tracing driver was used and an SQL statement was longer
         than 300 characters, an ArgumentOutOfRangeExcpetion occurred if
         the statement also contained a quoted character, and the 300th
         character was in the middle of a quoted token.

@@ -3454,7 +3454,7 @@
     <message>
 
       <para>
-        When trying to create stored procedures from a SQL script, a
+        When trying to create stored procedures from an SQL script, a
         <literal>MySqlException</literal> was thrown when attempting to
         redefine the <literal>DELIMITER</literal>:
       </para>


Modified: trunk/dynamic-docs/changelog/workbench.xml
===================================================================
--- trunk/dynamic-docs/changelog/workbench.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/dynamic-docs/changelog/workbench.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 11, Lines Added: 19, Lines Deleted: 19; 4821 bytes

@@ -345,7 +345,7 @@
       <para>
         Generated scripts did not manage connection variables cleanly.
         For example, the state of AUTOCOMMIT was not preserved by the
-        script produced by forward engineering a SQL CREATE script. The
+        script produced by forward engineering an SQL CREATE script. The
         script switched off AUTOCOMMIT, but did not then restore it
         correctly to its previous state.
       </para>

@@ -2563,7 +2563,7 @@
 
       <para>
         &workbench; has been changed so that the Query Editor in the SQL
-        editor includes a SQL formatter. Code can be highlighted and
+        editor includes an SQL formatter. Code can be highlighted and
         formatted using the menu item <guimenu>Edit</guimenu>,
         <guimenu>Format</guimenu>.
       </para>

@@ -3395,10 +3395,10 @@
     <message>
 
       <para>
-        When importing a SQL script using the <guilabel>Reverse Engineer
-        SQL Script</guilabel> wizard, copying a path from the clipboard
-        to the <guilabel>Select SQL script</guilabel> file input box,
-        resulted in an <quote>invalid path</quote> error.
+        When importing an SQL script using the <guilabel>Reverse
+        Engineer SQL Script</guilabel> wizard, copying a path from the
+        clipboard to the <guilabel>Select SQL script</guilabel> file
+        input box, resulted in an <quote>invalid path</quote> error.
       </para>
 
     </message>

@@ -4667,8 +4667,8 @@
     <message>
 
       <para>
-        If a SQL script containing international characters was saved in
-        the SQL Editor, and then restored, the last character in the
+        If an SQL script containing international characters was saved
+        in the SQL Editor, and then restored, the last character in the
         restored file was missing.
       </para>
 

@@ -6382,7 +6382,7 @@
     <message>
 
       <para>
-        When forward engineering a SQL ALTER script, the generated code
+        When forward engineering an SQL ALTER script, the generated code
         attempted to recreate all foreign keys.
       </para>
 

@@ -6626,8 +6626,8 @@
     <message>
 
       <para>
-        When a SQL Editor connection for a remote server was opened, the
-        following error was generated:
+        When an SQL Editor connection for a remote server was opened,
+        the following error was generated:
       </para>
 
 <programlisting>

@@ -6775,7 +6775,7 @@
         A model was created with &workbench; 5.1.18 and data inserted
         using the <guilabel>Insert</guilabel> tab. If the model was then
         saved and loaded into &workbench; 5.2.22, and the model forward
-        engineered to a SQL script, the generated script contained
+        engineered to an SQL script, the generated script contained
         <literal>INSERT</literal> statements that inserted
         <literal>NULL</literal> instead of the data originally typed in.
       </para>

@@ -9522,7 +9522,7 @@
     <message>
 
       <para>
-        If a SQL file, using Windows file format, was loaded into the
+        If an SQL file, using Windows file format, was loaded into the
         SQL Editor, it was displayed with additional line breaks, and
         the SQL code was not interpreted correctly. Further, if code
         written in the SQL editor was saved to a file and then opened in

@@ -11140,7 +11140,7 @@
     <message>
 
       <para>
-        If a SQL statement was selected in the SQL Statements area of
+        If an SQL statement was selected in the SQL Statements area of
         the SQL Editor, and copied to the snippets list using the
         <guibutton>Save SQL to Snippets List</guibutton> toolbar button,
         then the statement was only partially saved, the beginning of

@@ -13233,10 +13233,10 @@
     <message>
 
       <para>
-        In the SQL Editor, when a SQL query was entered that contained a
-        large number of characters, it appeared full width in the action
-        column of the Ouput tab, causing the Response column to be
-        unacceptably narrow.
+        In the SQL Editor, when an SQL query was entered that contained
+        a large number of characters, it appeared full width in the
+        action column of the Ouput tab, causing the Response column to
+        be unacceptably narrow.
       </para>
 
     </message>

@@ -22836,7 +22836,7 @@
     <message>
 
       <para>
-        When a SQL Script was added and then its name changed, the name
+        When an SQL Script was added and then its name changed, the name
         would erroneously revert back to <quote>Script</quote>.
       </para>
 


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 719 bytes

@@ -1400,7 +1400,7 @@
       <para>
         An internal data structure that is used to represent the result
         set of a <emphasis role="bold">query</emphasis>, or other
-        operation that performs a search using a SQL
+        operation that performs a search using an SQL
         <literal>WHERE</literal> clause. It works like an iterator in
         other high-level languages, producing each value from the result
         set as requested.


Modified: trunk/innodb-1.1/innodb-performance.xml
===================================================================
--- trunk/innodb-1.1/innodb-performance.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/innodb-1.1/innodb-performance.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 2, Lines Added: 17, Lines Deleted: 21; 2877 bytes

@@ -670,7 +670,7 @@
       without observing the limit set by
       <literal
       role="sysvar">innodb_thread_concurrency</literal>.
-      Since a SQL statement (such as a join) may comprise multiple row
+      Since an SQL statement (such as a join) may comprise multiple row
       operations within InnoDB, InnoDB assigns <quote>tickets</quote>
       that allow a thread to be scheduled repeatedly with minimal
       overhead.

@@ -1796,26 +1796,22 @@
     </indexterm>
 
     <para>
-      Starting in InnoDB 1.1 with MySQL 5.5, the limit on
-      concurrent <link linkend="glos_transaction">transactions</link> is greatly expanded,
-      removing a bottleneck with the InnoDB <link linkend="glos_rollback_segment">rollback
-      segment</link> that affected high-capacity systems,
-      because
-      The limit applies to concurrent transactions
-      that change any data.
-      (Read-only transactions do not count against
-      that maximum.)
-      The single rollback
-      segment is now divided into 128 segments, each of which can support up
-      to 1023 transactions that perform writes, for a total of
-      approximately 128K concurrent transactions.
-      The original transaction limit was 1023.
-      Each transaction is
-      assigned to one of the rollback segments, and remains tied to that
-      rollback segment for the duration. This enhancement improves both
-      scalability (higher number of concurrent transactions) and
-      performance (less contention when different transactions access
-      the rollback segments).
+      Starting in InnoDB 1.1 with MySQL 5.5, the limit on concurrent
+      <link linkend="glos_transaction">transactions</link> is greatly
+      expanded, removing a bottleneck with the InnoDB
+      <link linkend="glos_rollback_segment">rollback segment</link> that
+      affected high-capacity systems, because The limit applies to
+      concurrent transactions that change any data. (Read-only
+      transactions do not count against that maximum.) The single
+      rollback segment is now divided into 128 segments, each of which
+      can support up to 1023 transactions that perform writes, for a
+      total of approximately 128K concurrent transactions. The original
+      transaction limit was 1023. Each transaction is assigned to one of
+      the rollback segments, and remains tied to that rollback segment
+      for the duration. This enhancement improves both scalability
+      (higher number of concurrent transactions) and performance (less
+      contention when different transactions access the rollback
+      segments).
     </para>
 
     <para>


Modified: trunk/innodb-1.1/plugin.ent
===================================================================
--- trunk/innodb-1.1/plugin.ent	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/innodb-1.1/plugin.ent	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 3040 bytes

@@ -80,7 +80,7 @@
 
 <!ENTITY glos_cluster_index_access_flag "<glossentry id='glos_cluster_index_access_flag'><glossterm>cluster index access flag</glossterm>&#10;<indexterm significance='preferred'><primary>cluster index access flag</primary></indexterm>&#10;<glossdef>&#10;<para>&#10;A setting associated with a cursor within Embedded InnoDB.&#10;Turning this setting on allows a cursor to search&#10;using a secondary index, and transparently retrieve the full contents&#10;of the corresponding row, rather than just the column values&#10;from the secondary index.&#10;</para>&#10;<glossseealso otherterm='glos_clustered_index' />&#10;<glossseealso otherterm='glos_cursor' />&#10;</glossdef>&#10;</glossentry>&#10;">
 
-<!ENTITY glos_cursor "<glossentry id='glos_cursor'><glossterm>cursor</glossterm>&#10;<indexterm significance='preferred'><primary>cursor</primary></indexterm>&#10;<glossdef>&#10;<para>&#10;An internal data structure that is used to represent the&#10;result set of a query, or other operation that performs&#10;a search using a SQL <literal>WHERE</literal> clause.&#10;It works like an iterator in other high-level languages,&#10;producing each value from the result set as requested.&#10;</para>&#10;<para>&#10;Although usually SQL handles the processing of cursors for you,&#10;you might delve into the inner workings when dealing with&#10;performance-critical code.&#10;Embedded InnoDB requires you to be familiar with cursors&#10;and to manipulate them using C API calls.&#10;</para>&#10;&#10;&#10;</glossdef>&#10;</glossentry>&#10;">
+<!ENTITY glos_cursor "<glossentry id='glos_cursor'><glossterm>cursor</glossterm>&#10;<indexterm significance='preferred'><primary>cursor</primary></indexterm>&#10;<glossdef>&#10;<para>&#10;An internal data structure that is used to represent the&#10;result set of a query, or other operation that performs&#10;a search using an SQL <literal>WHERE</literal> clause.&#10;It works like an iterator in other high-level languages,&#10;producing each value from the result set as requested.&#10;</para>&#10;<para>&#10;Although usually SQL handles the processing of cursors for you,&#10;you might delve into the inner workings when dealing with&#10;performance-critical code.&#10;Embedded InnoDB requires you to be familiar with cursors&#10;and to manipulate them using C API calls.&#10;</para>&#10;&#10;&#10;</glossdef>&#10;</glossentry>&#10;">
 
 <!ENTITY glos_cursor_match_mode "<glossentry id='glos_cursor_match_mode'><glossterm>cursor match mode</glossterm>&#10;<indexterm significance='preferred'><primary>cursor match mode</primary></indexterm>&#10;<glossdef>&#10;<para>&#10;In Embedded InnoDB, a setting that controls prefetching and locking&#10;when retrieving records through a cursor.&#10;</para>&#10;&#10;</glossdef>&#10;</glossentry>&#10;">
 


Modified: trunk/innodb-plugin-1.0/innodb-performance.xml
===================================================================
--- trunk/innodb-plugin-1.0/innodb-performance.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/innodb-plugin-1.0/innodb-performance.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 824 bytes

@@ -591,7 +591,7 @@
       context switching overhead by permitting multiple requests made
       during the execution of a single SQL statement to enter &innodb;
       without observing the limit set by &innodb_thread_concurrency;.
-      Since a SQL statement (such as a join) may comprise multiple row
+      Since an SQL statement (such as a join) may comprise multiple row
       operations within &innodb;, &innodb; assigns
       <quote>tickets</quote> that allow a thread to be scheduled
       repeatedly with minimal overhead.


Modified: trunk/mysql-monitor-2.0/mem-reference-advgraph-core.xml
===================================================================
--- trunk/mysql-monitor-2.0/mem-reference-advgraph-core.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysql-monitor-2.0/mem-reference-advgraph-core.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 778 bytes

@@ -3652,7 +3652,7 @@
             <listitem>
               <para>
                 To ensure that only the necessary columns are returned
-                from a SQL statement, the actual column names should be
+                from an SQL statement, the actual column names should be
                 specifically entered. This cuts down on unwanted network
                 traffic as only columns necessary for query satisfaction
                 are present.


Modified: trunk/mysql-monitor-2.1/mem-reference-advgraph-core.xml
===================================================================
--- trunk/mysql-monitor-2.1/mem-reference-advgraph-core.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysql-monitor-2.1/mem-reference-advgraph-core.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 778 bytes

@@ -4071,7 +4071,7 @@
             <listitem>
               <para>
                 To ensure that only the necessary columns are returned
-                from a SQL statement, the actual column names should be
+                from an SQL statement, the actual column names should be
                 specifically entered. This cuts down on unwanted network
                 traffic as only columns necessary for query satisfaction
                 are present.


Modified: trunk/mysql-monitor-2.2/mem-reference-advgraph-core.xml
===================================================================
--- trunk/mysql-monitor-2.2/mem-reference-advgraph-core.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysql-monitor-2.2/mem-reference-advgraph-core.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 778 bytes

@@ -4892,7 +4892,7 @@
             <listitem>
               <para>
                 To ensure that only the necessary columns are returned
-                from a SQL statement, the actual column names should be
+                from an SQL statement, the actual column names should be
                 specifically entered. This cuts down on unwanted network
                 traffic as only columns necessary for query satisfaction
                 are present.


Modified: trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml
===================================================================
--- trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysql-monitor-2.3/mem-reference-advgraph-core.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 778 bytes

@@ -5430,7 +5430,7 @@
             <listitem>
               <para>
                 To ensure that only the necessary columns are returned
-                from a SQL statement, the actual column names should be
+                from an SQL statement, the actual column names should be
                 specifically entered. This cuts down on unwanted network
                 traffic as only columns necessary for query satisfaction
                 are present.


Modified: trunk/mysqldoc-guide/special-markup.xml
===================================================================
--- trunk/mysqldoc-guide/special-markup.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysqldoc-guide/special-markup.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 772 bytes

@@ -876,7 +876,7 @@
           <literal>se</literal> for a storage engine,
           <literal>sysvar</literal> for a system variable,
           <literal>statvar</literal> for a status variable,
-          <literal>sqlmode</literal> for a SQL mode,
+          <literal>sqlmode</literal> for an SQL mode,
           <literal>isolevel</literal> for a transaction isolation level,
           <literal>cfunc</literal> for a C API function,
           <literal>jointype</literal> for an optimizer join type (as


Modified: trunk/mysqltest-1.0/writing-tests.xml
===================================================================
--- trunk/mysqltest-1.0/writing-tests.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysqltest-1.0/writing-tests.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 833 bytes

@@ -1454,8 +1454,8 @@
       <listitem>
         <para>
           Wait for a condition to become true. Set the
-          <literal>$wait_condition</literal> variable to a SQL statement
-          that selects a value and then include the
+          <literal>$wait_condition</literal> variable to an SQL
+          statement that selects a value and then include the
           <literal>wait_condition.inc</literal> file. The include file
           executes the statement in a loop with a 0.1 second sleep
           between executions until the select value is nonzero. For


Modified: trunk/mysqltest-2.0/writing-tests.xml
===================================================================
--- trunk/mysqltest-2.0/writing-tests.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/mysqltest-2.0/writing-tests.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 833 bytes

@@ -1509,8 +1509,8 @@
       <listitem>
         <para>
           Wait for a condition to become true. Set the
-          <literal>$wait_condition</literal> variable to a SQL statement
-          that selects a value and then include the
+          <literal>$wait_condition</literal> variable to an SQL
+          statement that selects a value and then include the
           <literal>wait_condition.inc</literal> file. The include file
           executes the statement in a loop with a 0.1 second sleep
           between executions until the select value is nonzero. For


Modified: trunk/refman-5.5/optimization.xml
===================================================================
--- trunk/refman-5.5/optimization.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/refman-5.5/optimization.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1312 bytes

@@ -5630,7 +5630,7 @@
       Depending on the details of your tables, columns, indexes, and the
       conditions in your <literal>WHERE</literal> clause, the MySQL
       optimizer considers many techniques to efficiently perform the
-      lookups involved in a SQL query. A query on a huge table can be
+      lookups involved in an SQL query. A query on a huge table can be
       performed without reading all the rows; a join involving several
       tables can be performed without comparing every combination of
       rows. The set of operations that the optimizer chooses to perform

@@ -7759,7 +7759,7 @@
             the buffer pool, it initially inserts it at the midpoint
             (the head of the old sublist). A block can be read in
             because it is required for a user-specified operation such
-            as a SQL query, or as part of a
+            as an SQL query, or as part of a
             <link linkend="glos_read_ahead">read-ahead</link> operation
             performed automatically by <literal>InnoDB</literal>.
           </para>


Modified: trunk/refman-5.6/optimization.xml
===================================================================
--- trunk/refman-5.6/optimization.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/refman-5.6/optimization.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1312 bytes

@@ -5780,7 +5780,7 @@
       Depending on the details of your tables, columns, indexes, and the
       conditions in your <literal>WHERE</literal> clause, the MySQL
       optimizer considers many techniques to efficiently perform the
-      lookups involved in a SQL query. A query on a huge table can be
+      lookups involved in an SQL query. A query on a huge table can be
       performed without reading all the rows; a join involving several
       tables can be performed without comparing every combination of
       rows. The set of operations that the optimizer chooses to perform

@@ -7912,7 +7912,7 @@
             the buffer pool, it initially inserts it at the midpoint
             (the head of the old sublist). A block can be read in
             because it is required for a user-specified operation such
-            as a SQL query, or as part of a
+            as an SQL query, or as part of a
             <link linkend="glos_read_ahead">read-ahead</link> operation
             performed automatically by <literal>InnoDB</literal>.
           </para>


Modified: trunk/refman-common/connector-cpp-core.xml
===================================================================
--- trunk/refman-common/connector-cpp-core.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/refman-common/connector-cpp-core.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 662 bytes

@@ -2342,7 +2342,7 @@
 
       <para>
         <classname>sql::PreparedStatement</classname> is created by
-        passing a SQL query to
+        passing an SQL query to
         <methodname>sql::Connection::prepareStatement()</methodname>. As
         <classname>sql::PreparedStatement</classname> is derived from
         <classname>sql::Statement</classname>, you will feel familiar


Modified: trunk/refman-common/connector-net-tutorials-intro.xml
===================================================================
--- trunk/refman-common/connector-net-tutorials-intro.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/refman-common/connector-net-tutorials-intro.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 880 bytes

@@ -767,7 +767,7 @@
       Calling a Stored Procedure from your Connector/NET application is
       similar to techniques you have seen earlier in this tutorial. A
       <literal>MySqlCommand</literal> object is created, but rather than
-      taking a SQL query as a parameter it takes the name of the Stored
+      taking an SQL query as a parameter it takes the name of the Stored
       Procedure to call. The <literal>MySqlCommand</literal> object also
       needs to be set to the type of Stored Procedure. This is
       illustrated by the following code snippet:


Modified: trunk/workbench/data-modeling.xml
===================================================================
--- trunk/workbench/data-modeling.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/workbench/data-modeling.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 709 bytes

@@ -164,7 +164,7 @@
 
     <para>
       The purpose of this action item is to enable you to create a model
-      from a SQL Create script. Such a script may have been created by
+      from an SQL Create script. Such a script may have been created by
       hand or may be as a result of reverse engineering an existing
       database to generate the script, which may then be modified
       according to requirements. Clicking this action item launches the


Modified: trunk/workbench/forward-engineering.xml
===================================================================
--- trunk/workbench/forward-engineering.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/workbench/forward-engineering.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 7; 1296 bytes

@@ -215,13 +215,13 @@
       </figure>
 
       <para>
-        This first screen enables you to select a SQL script and compare
-        it with the model currently in &workbench;. The difference
-        between the two models will be used to create an alter script
-        that can be used to modify the target schema so that it matches
-        the model held in &workbench;. You can also view the script
-        generated, rather than saving it to a file, by leaving the
-        <guilabel>Output File</guilabel> field empty.
+        This first screen enables you to select an SQL script and
+        compare it with the model currently in &workbench;. The
+        difference between the two models will be used to create an
+        alter script that can be used to modify the target schema so
+        that it matches the model held in &workbench;. You can also view
+        the script generated, rather than saving it to a file, by
+        leaving the <guilabel>Output File</guilabel> field empty.
       </para>
 
       <note>


Modified: trunk/workbench/sql-development.xml
===================================================================
--- trunk/workbench/sql-development.xml	2011-03-29 14:46:24 UTC (rev 25599)
+++ trunk/workbench/sql-development.xml	2011-03-29 15:49:23 UTC (rev 25600)
Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 3058 bytes

@@ -95,7 +95,7 @@
     <para>
       If you already have created a connection to a database it will
       appear in this panel as an icon. Double-clicking the icon will
-      directly launch a SQL Editor tab, and connect you to the database
+      directly launch an SQL Editor tab, and connect you to the database
       as defined by the connection.
     </para>
 

@@ -134,7 +134,7 @@
       Edit Table Data wizard is launched. This is a two stage wizard.
       The first stage enables you to select a Stored Connection. The
       second stage enables you to select the Schema and Table you want
-      to edit. After the wizard is completed, a SQL Editor tab is
+      to edit. After the wizard is completed, an SQL Editor tab is
       launched which displays a data grid that enables you to
       interactively edit table data as required.
     </para>

@@ -153,9 +153,9 @@
     <para>
       Clicking this action item launched the Edit SQL Script wizard.
       This is a two stage wizard. The first stage enables you to select
-      a Stored Connection. The second stage enables you to select a SQL
+      a Stored Connection. The second stage enables you to select an SQL
       Script file, and optionally have the script executed after it is
-      opened. After the wizard is completed, a SQL Editor tab will be
+      opened. After the wizard is completed, an SQL Editor tab will be
       launched, with the script displayed. If you optionally selected to
       run the script, the script will run and the results will be
       displayed.

@@ -261,7 +261,7 @@
       <title>Main Menu</title>
 
       <para>
-        When a SQL Editor tab is selected the most important items on
+        When an SQL Editor tab is selected the most important items on
         the main menu bar are the <guimenu>Query</guimenu> and <guimenu>
         Edit</guimenu> menu items. Each of these is discussed further in
         the following sections.

@@ -475,7 +475,7 @@
 
         <listitem>
           <para>
-            <emphasis role="bold">Open a SQL Script File</emphasis>:
+            <emphasis role="bold">Open an SQL Script File</emphasis>:
             Cicking this button enables any saved SQL script to be
             loaded ready for execution. The script will be displayed in
             the <guilabel>SQL Query</guilabel> area.

@@ -579,7 +579,7 @@
             <emphasis role="bold">Refresh state of database
             structures</emphasis>: Refreshes the view of Schemata,
             Tables, Views and Routines that appears in the Live Overview
-            Schema tabsheet. For example, if a SQL script creates a new
+            Schema tabsheet. For example, if an SQL script creates a new
             table, it will not appear in the Overview tab until the
             refresh toolbar button is pressed.
           </para>


Thread
svn commit - mysqldoc@oter02: r25600 - in trunk: . dynamic-docs/changelog dynamic-docs/glossary innodb-1.1 innodb-plugin-1.0 mysql-monitor-2.0 mysql-m...paul.dubois29 Mar