From: Vincent Bray <noodl@apache.org>
Date: Wed, 20 Aug 2008 23:01:45 +0000 (+0000)
Subject: Merge r687494 from trunk (Minor grammar corrections for mod_ssl.xml)
X-Git-Tag: 2.2.10~65
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=df65f745e38978bdd224dc479595f3b8b6f407d8;p=thirdparty%2Fapache%2Fhttpd.git

Merge r687494 from trunk (Minor grammar corrections for mod_ssl.xml)

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@687498 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index 7985c66a181..c903c5f7694 100644
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -789,10 +789,10 @@ server certificate chain into <directive
 module="mod_ssl">SSLCACertificatePath</directive> has the same effect
 for the certificate chain construction, it has the side-effect that
 client certificates issued by this same CA certificate are also
-accepted on client authentication. That's usually not one expect.</p>
+accepted on client authentication.</p>
 <p>
 But be careful: Providing the certificate chain works only if you are using a
-<em>single</em> (either RSA <em>or</em> DSA) based server certificate. If you are
+<em>single</em> RSA <em>or</em> DSA based server certificate. If you are
 using a coupled RSA+DSA certificate pair, this will work only if actually both
 certificates use the <em>same</em> certificate chain. Else the browsers will be
 confused in this situation.</p>