diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 097c426fd6c595bfaea17a1dc17650f26e026e61..81620eaa5a751048cb69f19a3120282896310edd 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.119 2009/03/22 21:55:07 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.120 2009/04/11 02:07:25 momjian Exp $ -->
 
 <chapter id="client-authentication">
  <title>Client Authentication</title>
@@ -1245,7 +1245,7 @@ ldapserver=ldap.example.net prefix="cn=" suffix="dc=example, dc=net"
     When using this authentication method, the server will require that
     the client provide a certificate. No password prompt will be sent
     to the client. The <literal>cn</literal> attribute of the certificate
-    will be matched with the login username, and if they match the
+    will be compared with the login username, and if they match the
     login will be allowed. Username mapping can be used if the usernames
     don't match.
    </para>