diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml
index 32b9b9a2c1565bc65a787045bc7970e42f93df8e..f6c86b930d8982e29d2aba25aa2c2fddc8229da0 100644
--- a/doc/src/sgml/query.sgml
+++ b/doc/src/sgml/query.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.13 2000/09/29 20:21:34 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.14 2000/12/12 16:47:52 momjian Exp $
 -->
 
  <chapter id="query">
@@ -273,8 +273,8 @@ SELECT * INTO TABLE temp FROM weather;
     As an example, say we wish to find all the records that
     are in the  temperature  range  of  other  records.  In
     effect,  we  need  to  compare  the temp_lo and temp_hi
-    attributes of each EMP  instance  to  the  temp_lo  and
-    temp_hi  attributes of all other EMP instances.
+    attributes of each WEATHER  instance  to  the  temp_lo  and
+    temp_hi  attributes of all other WEATHER instances.
     <note>
      <para>
       This  is only a conceptual model.  The actual join may
diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml
index 2717037aa899f58dd0fd09bac5e41d03d94f7605..52b2e9117ace38a30ff56e763ae602f649c17041 100644
--- a/doc/src/sgml/ref/create_rule.sgml
+++ b/doc/src/sgml/ref/create_rule.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.19 2000/10/05 19:48:17 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.20 2000/12/12 16:47:52 momjian Exp $
 Postgres documentation
 -->
 
@@ -208,14 +208,14 @@ ON UPDATE TO emp-1.salary WHERE emp-2.name = "Joe"
 CREATE RULE bad_rule_combination_1 AS
     ON SELECT TO emp
     DO INSTEAD 
-	SELECT TO toyemp;
+	SELECT * FROM toyemp;
      </programlisting>
 
      <programlisting>
 CREATE RULE bad_rule_combination_2 AS
     ON SELECT TO toyemp
     DO INSTEAD 
-	SELECT TO emp;
+	SELECT * FROM emp;
      </programlisting>
      <para>
       This attempt to select from EMP will cause