Author: jstephens
Date: 2006-03-29 04:29:39 +0200 (Wed, 29 Mar 2006)
New Revision: 1695
Log:
Fixed a couple of minor spelling/wording errors.
Modified:
trunk/refman-5.1/partitioning.xml
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-03-29 02:06:38 UTC (rev 1694)
+++ trunk/refman-5.1/partitioning.xml 2006-03-29 02:29:39 UTC (rev 1695)
@@ -363,7 +363,7 @@
queries that may not have been so when the partitioning scheme
was first set up. This capability, sometimes referred to as
<firstterm>partition pruning</firstterm>, was implemented in
- MySQL 5.1.6. For additional informaiton, see
+ MySQL 5.1.6. For additional information, see
<xref linkend="partitioning-pruning"/>.
</para>
</listitem>
@@ -3553,10 +3553,10 @@
</para>
<para>
- The core concept behind partitioning is relatively simple, and can
- be described as <quote>Do not scan partitions where there can be
- no matching values</quote>. For example, suppose you have a
- partitioned table <literal>t1</literal> defined by this statement:
+ The core concept behind partition pruning is relatively simple,
+ and can be described as <quote>Do not scan partitions where there
+ can be no matching values</quote>. For example, suppose you have
+ a partitioned table <literal>t1</literal> defined by this statement:
</para>
<programlisting>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1695 - trunk/refman-5.1 | jon | 29 Mar |
