Index: doc/src/sgml/ref/clusterdb.sgml
===================================================================
RCS file: /home/neil/cvsup/cvs/pgsql-server/doc/src/sgml/ref/clusterdb.sgml,v
retrieving revision 1.10
diff -c -r1.10 clusterdb.sgml
*** doc/src/sgml/ref/clusterdb.sgml	18 Jun 2003 12:19:11 -0000	1.10
--- doc/src/sgml/ref/clusterdb.sgml	9 Aug 2003 08:39:56 -0000
***************
*** 129,138 ****
        <term><option>--host <replaceable class="parameter">host</replaceable></></term>
        <listitem>
         <para>
! 	Specifies the host name of the machine on which the 
! 	server
! 	is running.  If the value begins with a slash, it is used 
! 	as the directory for the Unix domain socket.
         </para>
        </listitem>
       </varlistentry>
--- 129,137 ----
        <term><option>--host <replaceable class="parameter">host</replaceable></></term>
        <listitem>
         <para>
! 	Specifies the host name of the machine on which the server is
! 	running.  If the value begins with a slash, it is used as the
! 	directory for the Unix domain socket.
         </para>
        </listitem>
       </varlistentry>
***************
*** 182,188 ****
        <term><computeroutput>CLUSTER</computeroutput></term>
        <listitem>
         <para>
!         Everything went well.
         </para>
        </listitem>
       </varlistentry>
--- 181,187 ----
        <term><computeroutput>CLUSTER</computeroutput></term>
        <listitem>
         <para>
!         The database was successfully clustered.
         </para>
        </listitem>
       </varlistentry>
Index: doc/src/sgml/ref/createuser.sgml
===================================================================
RCS file: /home/neil/cvsup/cvs/pgsql-server/doc/src/sgml/ref/createuser.sgml,v
retrieving revision 1.34
diff -c -r1.34 createuser.sgml
*** doc/src/sgml/ref/createuser.sgml	6 Jun 2003 15:31:46 -0000	1.34
--- doc/src/sgml/ref/createuser.sgml	9 Aug 2003 08:43:19 -0000
***************
*** 276,282 ****
        <term><computeroutput>CREATE USER</computeroutput></term>
        <listitem>
         <para>
!         All is well.
         </para>
        </listitem>
       </varlistentry>
--- 276,282 ----
        <term><computeroutput>CREATE USER</computeroutput></term>
        <listitem>
         <para>
!         The user was successfully created.
         </para>
        </listitem>
       </varlistentry>
Index: doc/src/sgml/ref/dropuser.sgml
===================================================================
RCS file: /home/neil/cvsup/cvs/pgsql-server/doc/src/sgml/ref/dropuser.sgml,v
retrieving revision 1.26
diff -c -r1.26 dropuser.sgml
*** doc/src/sgml/ref/dropuser.sgml	18 Jun 2003 12:19:11 -0000	1.26
--- doc/src/sgml/ref/dropuser.sgml	9 Aug 2003 08:45:29 -0000
***************
*** 180,186 ****
        <term><computeroutput>DROP USER</computeroutput></term>
        <listitem>
         <para>
!         All is well.
         </para>
        </listitem>
       </varlistentry>
--- 180,186 ----
        <term><computeroutput>DROP USER</computeroutput></term>
        <listitem>
         <para>
!         The user was successfully removed.
         </para>
        </listitem>
       </varlistentry>
Index: doc/src/sgml/ref/prepare.sgml
===================================================================
RCS file: /home/neil/cvsup/cvs/pgsql-server/doc/src/sgml/ref/prepare.sgml,v
retrieving revision 1.4
diff -c -r1.4 prepare.sgml
*** doc/src/sgml/ref/prepare.sgml	26 Apr 2003 23:56:51 -0000	1.4
--- doc/src/sgml/ref/prepare.sgml	9 Aug 2003 08:42:06 -0000
***************
*** 130,136 ****
     In some situations, the query plan produced by for a prepared
     statement may be inferior to the plan produced if the statement
     were submitted and executed normally. This is because when the
!    statement is planned and the planer attempts to determine the
     optimal query plan, the actual values of any parameters specified
     in the statement are
     unavailable. <productname>PostgreSQL</productname> collects
--- 130,136 ----
     In some situations, the query plan produced by for a prepared
     statement may be inferior to the plan produced if the statement
     were submitted and executed normally. This is because when the
!    statement is planned and the planner attempts to determine the
     optimal query plan, the actual values of any parameters specified
     in the statement are
     unavailable. <productname>PostgreSQL</productname> collects
Index: doc/src/sgml/ref/vacuumdb.sgml
===================================================================
RCS file: /home/neil/cvsup/cvs/pgsql-server/doc/src/sgml/ref/vacuumdb.sgml,v
retrieving revision 1.29
diff -c -r1.29 vacuumdb.sgml
*** doc/src/sgml/ref/vacuumdb.sgml	18 Jun 2003 12:19:11 -0000	1.29
--- doc/src/sgml/ref/vacuumdb.sgml	9 Aug 2003 08:48:51 -0000
***************
*** 59,68 ****
  
  
    <para>
!   <application>vacuumdb</application> might need to connect several
!   times to the <productname>PostgreSQL</productname> server, asking for
!   a password each time. It is convenient to have a
!   <filename>$HOME/.pgpass</> file in such cases.
    </para>
  
   </refsect1>
--- 59,69 ----
  
  
    <para>
!    <application>vacuumdb</application> might need to connect several
!    times to the <productname>PostgreSQL</productname> server, asking
!    for a password each time. It is convenient to have a
!    <filename>$HOME/.pgpass</> file in such cases. See <xref
!    linkend="libpq-pgpass"> for more information.
    </para>
  
   </refsect1>
***************
*** 234,240 ****
        <term><computeroutput>VACUUM</computeroutput></term>
        <listitem>
         <para>
!         Everything went well.
         </para>
        </listitem>
       </varlistentry>
--- 235,241 ----
        <term><computeroutput>VACUUM</computeroutput></term>
        <listitem>
         <para>
!         The database was successfully vacuumed.
         </para>
        </listitem>
       </varlistentry>