From ebac30ed117e6b375bd6387ab3e39bba652f2ca6 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 11 Apr 2009 02:08:34 +0000
Subject: [PATCH] Wording improvement.
---
doc/src/sgml/client-auth.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 81620eaa5a7..6ebe46190d1 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.120 2009/04/11 02:07:25 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.121 2009/04/11 02:08:34 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 compared with the login username, and if they match the
+ will be compared to the login username, and if they match the
login will be allowed. Username mapping can be used if the usernames
don't match.
</para>
--
GitLab