List:Commits« Previous MessageNext Message »
From:john.russell Date:June 4 2011 4:33pm
Subject:svn commit - mysqldoc@oter02: r26425 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars dynamic-docs/glossary mysql-monitor-common mysqlt...
View as plain text  
Author: jdrussel
Date: 2011-06-04 18:33:30 +0200 (Sat, 04 Jun 2011)
New Revision: 26425

Log:
Rainy Saturday morning, tennis match postponed, let's fix a few more typos.
These are all finger slips from adding one extra letter.
This category gives a high proportion of false matches
in the spellcheck script, due to variable names with
arbitrary letters tacked on, and combinations like 'retraining / retaining'.
'Performance enchancements' is sort of poetic though.


Modified:
   trunk/dynamic-docs/changelog/connector-j.xml
   trunk/dynamic-docs/changelog/connector-odbc.xml
   trunk/dynamic-docs/changelog/mysql-proxy.xml
   trunk/dynamic-docs/command-optvars/mysqlslap.xml
   trunk/dynamic-docs/glossary/innodb.xml
   trunk/mysql-monitor-common/mem-reference-core.xml
   trunk/mysqltest-2.0/programs.xml
   trunk/refman-5.0/apis-c.xml
   trunk/refman-5.0/globalization.xml
   trunk/refman-5.0/sql-syntax-data-definition.xml
   trunk/refman-5.0/sql-syntax-server-administration.xml
   trunk/refman-5.1/apis-c.xml
   trunk/refman-5.1/dba-mysqld-server-core.xml
   trunk/refman-5.1/sql-syntax-data-definition.xml
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-5.5/apis-c.xml
   trunk/refman-5.5/dba-log-files.xml
   trunk/refman-5.5/dba-mysqld-server-core.xml
   trunk/refman-5.5/sql-syntax-data-definition.xml
   trunk/refman-5.5/sql-syntax-server-administration.xml
   trunk/refman-5.6/apis-c.xml
   trunk/refman-5.6/dba-log-files.xml
   trunk/refman-5.6/dba-mysqld-server-core.xml
   trunk/refman-5.6/sql-syntax-data-definition.xml
   trunk/refman-5.6/sql-syntax-server-administration.xml
   trunk/refman-common/connector-j-connprops.xml
   trunk/refman-common/connector-net-tutorials-intro.xml
   trunk/refman-common/ha-memcached-core.xml


Modified: trunk/dynamic-docs/changelog/connector-j.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-j.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/dynamic-docs/changelog/connector-j.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1328 bytes

@@ -79,7 +79,7 @@
       <para>
         5.1.15 will ship with an SLF4J logger (which can then be plugged
         into Log4J). Unfortunately, it is not possible to ship a direct
-        Log4J integration because the GPL is not compatibile with
+        Log4J integration because the GPL is not compatible with
         Log4J's license.
       </para>
 

@@ -5472,7 +5472,7 @@
     <message>
 
       <para>
-        Performance enchancements: Driver is now 50&ndash;100% faster in
+        Performance enhancements: Driver is now 50&ndash;100% faster in
         most situations, and creates fewer temporary objects.
       </para>
 

@@ -11423,7 +11423,7 @@
         authentication, and when reading error messages. We now use
         Cp1252 for all strings sent to the server during the handshake
         phase, and a hard-coded mapping of the
-        <literal role="sysvar">language</literal> systtem variable to
+        <literal role="sysvar">language</literal> system variable to
         the character set that is used for error messages.
       </para>
 


Modified: trunk/dynamic-docs/changelog/connector-odbc.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/dynamic-docs/changelog/connector-odbc.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 506 bytes

@@ -5889,7 +5889,7 @@
     <message>
 
       <para>
-        Added support for column binding as SQL_NUMBERIC_STRUCT.
+        Added support for column binding as SQL_NUMERIC_STRUCT.
       </para>
 
     </message>


Modified: trunk/dynamic-docs/changelog/mysql-proxy.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysql-proxy.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/dynamic-docs/changelog/mysql-proxy.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 609 bytes

@@ -440,7 +440,7 @@
             information for both ends of connections.
           </para>
           <para>
-            Some familiar strucgtures have been updated to acommodate
+            Some familiar structures have been updated to acommodate
             this information:
           </para>
           <itemizedlist>


Modified: trunk/dynamic-docs/command-optvars/mysqlslap.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqlslap.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/dynamic-docs/command-optvars/mysqlslap.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 550 bytes

@@ -1400,7 +1400,7 @@
     <name>query</name>
 
     <shortdescription>
-      The file or string containg the SELECT statement to use for
+      The file or string containing the SELECT statement to use for
       retrieving data
     </shortdescription>
 


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 706 bytes

@@ -5019,7 +5019,7 @@
         pessimistic <emphasis role="bold">locking</emphasis> strategy,
         to minimize the chance of
         <emphasis role="bold">deadlocks</emphasis>. At the application
-        level, you might avoid deadlocks by usiing a pessimistic
+        level, you might avoid deadlocks by using a pessimistic
         strategy of acquiring all locks needed by a transaction at the
         very beginning.
       </para>


Modified: trunk/mysql-monitor-common/mem-reference-core.xml
===================================================================
--- trunk/mysql-monitor-common/mem-reference-core.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/mysql-monitor-common/mem-reference-core.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 537 bytes

@@ -2055,7 +2055,7 @@
 
     <para>
       The above will create a file, <filename>data-1.3.sql</filename>
-      containg all of the &merlin; 1.3 information.
+      containing all of the &merlin; 1.3 information.
     </para>
 
     <para>


Modified: trunk/mysqltest-2.0/programs.xml
===================================================================
--- trunk/mysqltest-2.0/programs.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/mysqltest-2.0/programs.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 666 bytes

@@ -1844,7 +1844,7 @@
 
       <para>
         Other tests may refer to the last three variables listed in the
-        preceeding table, to locate files to read or write. For example,
+        preceding table, to locate files to read or write. For example,
         tests that need to create files will typically put them in
         <literal>$MYSQL_TMP_DIR/<replaceable>file_name</replaceable></literal>.
       </para>


Modified: trunk/refman-5.0/apis-c.xml
===================================================================
--- trunk/refman-5.0/apis-c.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.0/apis-c.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1098 bytes

@@ -9039,7 +9039,7 @@
               <listitem>
                 <para>
                   In all other cases, set the other members
-                  appriopriately and set <literal>is_null</literal> to
+                  appropriately and set <literal>is_null</literal> to
                   the address of a <literal>my_bool</literal> variable.
                   Set that variable's value to true or false
                   appropriately between executions to indicate whether

@@ -14400,7 +14400,7 @@
       was built using the same option. If the client application uses
       the dynamic C runtime (<literal>/MD</literal> option, or
       <literal>/MDd</literal> option in debug mode), it cannot link with
-      the static client library and must use the dynnamic library.
+      the static client library and must use the dynamic library.
     </para>
 
     <para>


Modified: trunk/refman-5.0/globalization.xml
===================================================================
--- trunk/refman-5.0/globalization.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.0/globalization.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 592 bytes

@@ -7033,7 +7033,7 @@
       </para>
 
       <para>
-        For implementation instructions, for a non-UCA colluation, see
+        For implementation instructions, for a non-UCA collation, see
         <xref linkend="adding-character-set"/>. For a UCA collation, see
         <xref linkend="adding-collation-unicode-uca"/>.
       </para>


Modified: trunk/refman-5.0/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-data-definition.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.0/sql-syntax-data-definition.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 709 bytes

@@ -2171,7 +2171,7 @@
 
     <para>
       Statements that return a result set can be used within a stored
-      procedcure but not within a stored function. This prohibition
+      procedure but not within a stored function. This prohibition
       includes <literal role="stmt">SELECT</literal> statements that do
       not have an <literal>INTO
       <replaceable>var_list</replaceable></literal> clause and other


Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 576 bytes

@@ -474,7 +474,7 @@
 
       <para>
         There are several aspects to the <literal>GRANT</literal>
-        statement, described under the folllowing topics in this
+        statement, described under the following topics in this
         section:
       </para>
 


Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.1/apis-c.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1098 bytes

@@ -9146,7 +9146,7 @@
               <listitem>
                 <para>
                   In all other cases, set the other members
-                  appriopriately and set <literal>is_null</literal> to
+                  appropriately and set <literal>is_null</literal> to
                   the address of a <literal>my_bool</literal> variable.
                   Set that variable's value to true or false
                   appropriately between executions to indicate whether

@@ -14492,7 +14492,7 @@
       was built using the same option. If the client application uses
       the dynamic C runtime (<literal>/MD</literal> option, or
       <literal>/MDd</literal> option in debug mode), it cannot link with
-      the static client library and must use the dynnamic library.
+      the static client library and must use the dynamic library.
     </para>
 
     <para>


Modified: trunk/refman-5.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.1/dba-mysqld-server-core.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.1/dba-mysqld-server-core.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 698 bytes

@@ -15237,7 +15237,7 @@
         <listitem>
           <para>
             The <literal>mysql.plugin</literal> table shows which
-            plugins have been registerted with
+            plugins have been registered with
             <literal role="stmt">INSTALL PLUGIN</literal>. The table
             contains only plugin names and library file names, so it
             does not provide as much information as the


Modified: trunk/refman-5.1/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-data-definition.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.1/sql-syntax-data-definition.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 709 bytes

@@ -4688,7 +4688,7 @@
 
     <para>
       Statements that return a result set can be used within a stored
-      procedcure but not within a stored function. This prohibition
+      procedure but not within a stored function. This prohibition
       includes <literal role="stmt">SELECT</literal> statements that do
       not have an <literal>INTO
       <replaceable>var_list</replaceable></literal> clause and other


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 576 bytes

@@ -409,7 +409,7 @@
 
       <para>
         There are several aspects to the <literal>GRANT</literal>
-        statement, described under the folllowing topics in this
+        statement, described under the following topics in this
         section:
       </para>
 


Modified: trunk/refman-5.5/apis-c.xml
===================================================================
--- trunk/refman-5.5/apis-c.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.5/apis-c.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1098 bytes

@@ -9179,7 +9179,7 @@
               <listitem>
                 <para>
                   In all other cases, set the other members
-                  appriopriately and set <literal>is_null</literal> to
+                  appropriately and set <literal>is_null</literal> to
                   the address of a <literal>my_bool</literal> variable.
                   Set that variable's value to true or false
                   appropriately between executions to indicate whether

@@ -15514,7 +15514,7 @@
       was built using the same option. If the client application uses
       the dynamic C runtime (<literal>/MD</literal> option, or
       <literal>/MDd</literal> option in debug mode), it cannot link with
-      the static client library and must use the dynnamic library.
+      the static client library and must use the dynamic library.
     </para>
 
     <para>


Modified: trunk/refman-5.5/dba-log-files.xml
===================================================================
--- trunk/refman-5.5/dba-log-files.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.5/dba-log-files.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 825 bytes

@@ -1832,7 +1832,7 @@
         type of statement (safe, unsafe, or binary injected), the binary
         logging format (<literal>STATEMENT</literal>,
         <literal>ROW</literal>, or <literal>MIXED</literal>), and the
-        logging capabailities of the storage engine (statement capable,
+        logging capabilities of the storage engine (statement capable,
         row capable, both, or neither). Statements may be logged with or
         without a warning; failed statements are not logged, but
         generate errors in the log. This is shown in the following


Modified: trunk/refman-5.5/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.5/dba-mysqld-server-core.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.5/dba-mysqld-server-core.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 698 bytes

@@ -15818,7 +15818,7 @@
         <listitem>
           <para>
             The <literal>mysql.plugin</literal> table shows which
-            plugins have been registerted with
+            plugins have been registered with
             <literal role="stmt">INSTALL PLUGIN</literal>. The table
             contains only plugin names and library file names, so it
             does not provide as much information as the


Modified: trunk/refman-5.5/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-data-definition.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.5/sql-syntax-data-definition.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 709 bytes

@@ -3645,7 +3645,7 @@
 
     <para>
       Statements that return a result set can be used within a stored
-      procedcure but not within a stored function. This prohibition
+      procedure but not within a stored function. This prohibition
       includes <literal role="stmt">SELECT</literal> statements that do
       not have an <literal>INTO
       <replaceable>var_list</replaceable></literal> clause and other


Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 576 bytes

@@ -469,7 +469,7 @@
 
       <para>
         There are several aspects to the <literal>GRANT</literal>
-        statement, described under the folllowing topics in this
+        statement, described under the following topics in this
         section:
       </para>
 


Modified: trunk/refman-5.6/apis-c.xml
===================================================================
--- trunk/refman-5.6/apis-c.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.6/apis-c.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1098 bytes

@@ -9192,7 +9192,7 @@
               <listitem>
                 <para>
                   In all other cases, set the other members
-                  appriopriately and set <literal>is_null</literal> to
+                  appropriately and set <literal>is_null</literal> to
                   the address of a <literal>my_bool</literal> variable.
                   Set that variable's value to true or false
                   appropriately between executions to indicate whether

@@ -15494,7 +15494,7 @@
       was built using the same option. If the client application uses
       the dynamic C runtime (<literal>/MD</literal> option, or
       <literal>/MDd</literal> option in debug mode), it cannot link with
-      the static client library and must use the dynnamic library.
+      the static client library and must use the dynamic library.
     </para>
 
     <para>


Modified: trunk/refman-5.6/dba-log-files.xml
===================================================================
--- trunk/refman-5.6/dba-log-files.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.6/dba-log-files.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 825 bytes

@@ -1833,7 +1833,7 @@
         type of statement (safe, unsafe, or binary injected), the binary
         logging format (<literal>STATEMENT</literal>,
         <literal>ROW</literal>, or <literal>MIXED</literal>), and the
-        logging capabailities of the storage engine (statement capable,
+        logging capabilities of the storage engine (statement capable,
         row capable, both, or neither). Statements may be logged with or
         without a warning; failed statements are not logged, but
         generate errors in the log. This is shown in the following


Modified: trunk/refman-5.6/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.6/dba-mysqld-server-core.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.6/dba-mysqld-server-core.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 698 bytes

@@ -15434,7 +15434,7 @@
         <listitem>
           <para>
             The <literal>mysql.plugin</literal> table shows which
-            plugins have been registerted with
+            plugins have been registered with
             <literal role="stmt">INSTALL PLUGIN</literal>. The table
             contains only plugin names and library file names, so it
             does not provide as much information as the


Modified: trunk/refman-5.6/sql-syntax-data-definition.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-data-definition.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.6/sql-syntax-data-definition.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 709 bytes

@@ -3707,7 +3707,7 @@
 
     <para>
       Statements that return a result set can be used within a stored
-      procedcure but not within a stored function. This prohibition
+      procedure but not within a stored function. This prohibition
       includes <literal role="stmt">SELECT</literal> statements that do
       not have an <literal>INTO
       <replaceable>var_list</replaceable></literal> clause and other


Modified: trunk/refman-5.6/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-server-administration.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-5.6/sql-syntax-server-administration.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 576 bytes

@@ -467,7 +467,7 @@
 
       <para>
         There are several aspects to the <literal>GRANT</literal>
-        statement, described under the folllowing topics in this
+        statement, described under the following topics in this
         section:
       </para>
 


Modified: trunk/refman-common/connector-j-connprops.xml
===================================================================
--- trunk/refman-common/connector-j-connprops.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-common/connector-j-connprops.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1311 bytes

@@ -298,7 +298,7 @@
               <entry>selfDestructOnPingMaxOperations</entry>
               <entry>=If set to a non-zero value, the driver will report close the connection
                 and report failure when Connection.ping() or
-                Connection.isValid(int) is called if the connnection's
+                Connection.isValid(int) is called if the connection's
                 count of commands sent to the server exceeds this value.</entry>
               <entry>0</entry>
               <entry>5.1.6</entry>

@@ -307,7 +307,7 @@
               <entry>selfDestructOnPingSecondsLifetime</entry>
               <entry>If set to a non-zero value, the driver will report close the connection
                 and report failure when Connection.ping() or
-                Connection.isValid(int) is called if the connnection's
+                Connection.isValid(int) is called if the connection's
                 lifetime exceeds this value.</entry>
               <entry>0</entry>
               <entry>5.1.6</entry>


Modified: trunk/refman-common/connector-net-tutorials-intro.xml
===================================================================
--- trunk/refman-common/connector-net-tutorials-intro.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-common/connector-net-tutorials-intro.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 767 bytes

@@ -220,7 +220,7 @@
       results have been obtained in a <literal>MySqlReader</literal>
       object, the results can be processed. In this case the information
       is simply printed out as part of a <literal>while</literal> loop.
-      Finally, the <literal>MySqlReader</literal> object is displosed of
+      Finally, the <literal>MySqlReader</literal> object is disposed of
       by running its <literal>Close</literal> method on it.
     </para>
 


Modified: trunk/refman-common/ha-memcached-core.xml
===================================================================
--- trunk/refman-common/ha-memcached-core.xml	2011-06-03 23:47:19 UTC (rev 26424)
+++ trunk/refman-common/ha-memcached-core.xml	2011-06-04 16:33:30 UTC (rev 26425)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 732 bytes

@@ -712,7 +712,7 @@
         <para>
           Specify the maximum size permitted for storing an object
           within the <command>memcached</command> instance. The size
-          supports a unit postix (<literal>k</literal> for kilobytes,
+          supports a unit postfix (<literal>k</literal> for kilobytes,
           <literal>m</literal> for megabytes). For example, to increase
           the maximum supported object size to 32MB:
         </para>


Thread
svn commit - mysqldoc@oter02: r26425 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars dynamic-docs/glossary mysql-monitor-common mysqlt...john.russell4 Jun