diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 34322aeba783b87c787b2aead108054e5bd95e65..f1a4881749041364338961268e07f3faa31a2ff0 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.62 2003/12/13 23:59:06 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.63 2004/01/26 05:35:15 momjian Exp $
 -->
 
 <chapter id="client-authentication">
@@ -535,8 +535,9 @@ local   db1,db2,@demodbs  all                                       md5
    <para>
     When <literal>trust</> authentication is specified,
     <productname>PostgreSQL</productname> assumes that anyone who can
-    connect to the server is authorized to access the database as
-    whatever database user he specifies (including the database superuser).
+    connect to the server is authorized to access the database with
+    whatever database user they specify (including the database superuser).
+    Of course, restrictions placed in the <literal>user</> column still apply.
     This method should only be used when there is adequate operating system-level
     protection on connections to the server.
    </para>