Index: doc/src/sgml/ref/create_trigger.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v
retrieving revision 1.13
diff -c -r1.13 create_trigger.sgml
*** doc/src/sgml/ref/create_trigger.sgml	2001/05/27 09:59:28	1.13
--- doc/src/sgml/ref/create_trigger.sgml	2001/06/10 03:44:14
***************
*** 150,156 ****
      Only the relation owner may create a trigger on this relation.
     </para>
     <para>
!     As of the current release (v7.0), STATEMENT triggers are not implemented.
     </para>
     <para>
      Refer to <command>DROP TRIGGER</command> for information on how to 
--- 150,156 ----
      Only the relation owner may create a trigger on this relation.
     </para>
     <para>
!     As of the current release, STATEMENT triggers are not implemented.
     </para>
     <para>
      Refer to <command>DROP TRIGGER</command> for information on how to 
Index: doc/src/sgml/ref/psql-ref.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v
retrieving revision 1.55
diff -c -r1.55 psql-ref.sgml
*** doc/src/sgml/ref/psql-ref.sgml	2001/05/28 04:27:17	1.55
--- doc/src/sgml/ref/psql-ref.sgml	2001/06/10 03:44:16
***************
*** 1051,1057 ****
  
  	<note>
  	<para>
! 	As of <application>psql</application> version 7.0 it is no longer
  	necessary to save the command history, since that will be done
  	automatically on program termination. The history is
  	also loaded automatically every time <application>psql</application>
--- 1051,1057 ----
  
  	<note>
  	<para>
! 	In the current version, it is no longer
  	necessary to save the command history, since that will be done
  	automatically on program termination. The history is
  	also loaded automatically every time <application>psql</application>
***************
*** 1579,1585 ****
        </para>
  
        <para>
!       As of version 7.0, <application>psql</application> automatically issues a
        password prompt whenever the backend requests password authentication.
        Because this is currently based on a hack, the automatic
        recognition might mysteriously fail, hence this option to force a prompt.
--- 1579,1585 ----
        </para>
  
        <para>
!       In the current version, <application>psql</application> automatically issues a
        password prompt whenever the backend requests password authentication.
        Because this is currently based on a hack, the automatic
        recognition might mysteriously fail, hence this option to force a prompt.
Index: doc/src/sgml/ref/select.sgml
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v
retrieving revision 1.42
diff -c -r1.42 select.sgml
*** doc/src/sgml/ref/select.sgml	2001/05/30 04:32:30	1.42
--- doc/src/sgml/ref/select.sgml	2001/06/10 03:44:17
***************
*** 122,129 ****
  	table is scanned.  If ONLY is not specified, the table and all its
  	descendant tables (if any) are scanned.  * can be appended to the
  	table name to indicate that descendant tables are to be scanned,
! 	but as of <Productname>Postgres</Productname> 7.1 this is the default
! 	behavior.  (In releases before 7.1, ONLY was the default behavior.)
         </para>
        </listitem>
       </varlistentry>
--- 122,129 ----
  	table is scanned.  If ONLY is not specified, the table and all its
  	descendant tables (if any) are scanned.  * can be appended to the
  	table name to indicate that descendant tables are to be scanned,
! 	but in the current version, this is the default behavior.
! 	(In releases before 7.1, ONLY was the default behavior.)
         </para>
        </listitem>
       </varlistentry>