From b05204ac8a36ebe4f68823fdc47be2cde294621b Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 12 Jan 2003 18:42:59 +0000
Subject: [PATCH] Fix some minor grammatical errors.

---
 doc/src/sgml/perform.sgml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
index fb2dd96b03..4c150d5022 100644
--- a/doc/src/sgml/perform.sgml
+++ b/doc/src/sgml/perform.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.22 2002/11/11 20:14:03 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.23 2003/01/12 18:42:59 tgl Exp $
 -->
 
  <chapter id="performance-tips">
@@ -600,7 +600,7 @@ SELECT * FROM a, b, c WHERE a.id = b.id AND b.ref = c.id;
 SELECT * FROM a CROSS JOIN b CROSS JOIN c WHERE a.id = b.id AND b.ref = c.id;
 SELECT * FROM a JOIN (b JOIN c ON (b.ref = c.id)) ON (a.id = b.id);
 </programlisting>
-   but the second and third take less time to plan than the first.  This effect
+   the second and third take less time to plan than the first.  This effect
    is not worth worrying about for only three tables, but it can be a
    lifesaver with many tables.
   </para>
@@ -628,8 +628,8 @@ SELECT * FROM d LEFT JOIN
         (SELECT * FROM a, b, c WHERE ...) AS ss
         ON (...);
 </programlisting>
-   Here, joining D must be the last step in the query plan, but the
-   planner is free to consider various join orders for A, B, C.
+   Here, joining to D must be the last step in the query plan, but the
+   planner is free to consider various join orders for A, B, and C.
   </para>
 
   <para>