Author: mcbrown
Date: 2007-10-28 12:06:03 +0100 (Sun, 28 Oct 2007)
New Revision: 8376
Log:
Some typo fixes (Thanks PeterL!)
Modified:
trunk/refman-common/mysql-proxy.xml
Modified: trunk/refman-common/mysql-proxy.xml
===================================================================
--- trunk/refman-common/mysql-proxy.xml 2007-10-28 01:56:15 UTC (rev 8375)
+++ trunk/refman-common/mysql-proxy.xml 2007-10-28 11:06:03 UTC (rev 8376)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 6; 1668 bytes
@@ -30,8 +30,8 @@
In addition to the basic pass-through configuration, the MySQL Proxy
is also capable of monitoring and altering the communication between
the client and the server. This interception of the queries enables
- you to add profiling The interception of the exchanges is scriptable
- using the Lua scripting language.
+ you to add profiling, and the interception of the exchanges is
+ scriptable using the Lua scripting language.
</para>
<para>
@@ -756,9 +756,9 @@
when injecting queries into the query queue. Because the proxy
sits between the client and MySQL server, what the proxy sends
to the server, and the information that the proxy ultimately
- returns to the client do not have to match correlate. Once the
- client has connected to the proxy, the following sequence occurs
- for each individual query sent by the client.
+ returns to the client do not have to match or correlate. Once
+ the client has connected to the proxy, the following sequence
+ occurs for each individual query sent by the client.
</para>
<mediaobject>
@@ -968,7 +968,7 @@
<para>
The attributes for each entry within the
- <literal>proxy.servers</literal> table is shown in this table.
+ <literal>proxy.servers</literal> table are shown in this table.
</para>
<informaltable>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8376 - trunk/refman-common | mcbrown | 28 Oct |
