From: Daniel Gruno
Date: Thu, 26 Jul 2012 09:53:38 +0000 (+0000)
Subject: xforms
X-Git-Tag: 2.2.23~91
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=48677129abf6c2db9dd011d7d994fd2d960a13ff;p=thirdparty%2Fapache%2Fhttpd.git
xforms
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1365927 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en
index 7b75147a0ce..40313e292df 100644
--- a/docs/manual/mod/mod_ssl.html.en
+++ b/docs/manual/mod/mod_ssl.html.en
@@ -443,7 +443,7 @@ consisting of OpenSSL cipher specifications to configure the Cipher Suite the
client is permitted to negotiate in the SSL handshake phase. Notice that this
directive can be used both in per-server and per-directory context. In
per-server context it applies to the standard SSL handshake when a connection
-is established. In per-directory context it forces a SSL renegotation with the
+is established. In per-directory context it forces a SSL renegotiation with the
reconfigured Cipher Suite after the HTTP request was read but before the HTTP
response is sent.
@@ -1409,7 +1409,7 @@ The following source variants are available:
the first argument). Use this especially at startup time, for instance
with an available /dev/random
and/or
/dev/urandom
devices (which usually exist on modern Unix
- derivates like FreeBSD and Linux).
+ derivatives like FreeBSD and Linux).
But be careful: Usually /dev/random
provides only as
much entropy data as it actually has, i.e. when you request 512 bytes of
@@ -1681,7 +1681,7 @@ OpenSSL already caches the SSL session information locally. But because modern
clients request inlined images and other data via parallel requests (usually
up to four parallel requests are common) those requests are served by
different pre-forked server processes. Here an inter-process cache
-helps to avoid unneccessary session handshakes.
+helps to avoid unnecessary session handshakes.
The following four storage types are currently supported:
@@ -1825,7 +1825,7 @@ This directive sets the Certificate verification level for the Client
Authentication. Notice that this directive can be used both in per-server and
per-directory context. In per-server context it applies to the client
authentication process used in the standard SSL handshake when a connection is
-established. In per-directory context it forces a SSL renegotation with the
+established. In per-directory context it forces a SSL renegotiation with the
reconfigured client verification level after the HTTP request was read but
before the HTTP response is sent.