hyphenate some compound modifiers

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@924915 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 36b1332446a9f76a3c75dca2502a4f0c55786869..80575723c397bcf0ee28a496128db3ec55fb3bd0 100644 (file)
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -3458,7 +3458,7 @@ port</description>
     the client if any are supplied (otherwise it will use the
     canonical name, as defined above). These values are the same
     that are used to implement <a
-    href="../vhosts/name-based.html">name based virtual hosts</a>,
+    href="../vhosts/name-based.html">name-based virtual hosts</a>,
     and are available with the same clients. The CGI variables
     <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
     constructed from the client supplied values as well.</p>

diff --git a/docs/manual/mod/mod_cache.xml b/docs/manual/mod/mod_cache.xml
index 26f65048f340a54ec5859f9b545f48edc701df18..ff30909a2e09b89f03066eb0bde5bd19cd3fedc6 100644 (file)
--- a/docs/manual/mod/mod_cache.xml
+++ b/docs/manual/mod/mod_cache.xml
@@ -179,7 +179,7 @@
 
   <p>To solve this problem the <directive module="mod_cache">CacheQuickHandler
   </directive> directive can be set to <strong>off</strong>, and the server will
-  process all phases normally handled by a non cached request, including the
+  process all phases normally handled by a non-cached request, including the
   <strong>authentication and authorisation</strong> phases.</p>
 
   <p>In addition, the administrator may optionally specify the <strong>precise point

diff --git a/docs/manual/mod/mod_session.xml b/docs/manual/mod/mod_session.xml
index e12f9292307327c74934e76921b5f93206a45d1c..c65870cc295b2cf6b4618d2109db3e693150ff11 100644 (file)
--- a/docs/manual/mod/mod_session.xml
+++ b/docs/manual/mod/mod_session.xml
@@ -203,7 +203,7 @@
       of the cookie.</p>
       
       <note type="warning"><title>Warning</title>
-      <p>Some of the HTTP cookie privacy features are either non standard, or
+      <p>Some of the HTTP cookie privacy features are either non-standard, or
       are not implemented consistently across browsers. The session modules
       allow you to set cookie parameters, but it makes no guarantee that privacy
       will be respected by the browser. If security is a concern, use the

diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index dfa3bb826e266990e00d93c2e4cd78e786ae64cb..7057e739b9652aa53ab31692599fbd066ce1bfdd 100644 (file)
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -1303,7 +1303,7 @@ SSLRenegBufferSize 262144
 
 <directivesynopsis>
 <name>SSLStrictSNIVHostCheck</name>
-<description>Whether to allow non SNI clients to access a name based virtual
+<description>Whether to allow non-SNI clients to access a name-based virtual
 host.
 </description>
 <syntax>SSLStrictSNIVHostCheck on|off</syntax>
@@ -1314,8 +1314,8 @@ host.
 
 <usage>
 <p>
-This directive sets whether a non SNI client is allowed to access a name based
-virtual host. If set to <code>on</code> in the default name based virtual
+This directive sets whether a non-SNI client is allowed to access a name-based
+virtual host. If set to <code>on</code> in the default name-based virtual
 host, clients that are SNI unaware will not be allowed to access <em>any</em>
 virtual host, belonging to this particular IP / port combination.
 If set to <code>on</code> in any other virtual host, SNI unaware clients

diff --git a/docs/manual/ssl/ssl_faq.xml b/docs/manual/ssl/ssl_faq.xml
index 732242029945b0e38dca7bad2e52d9c6f8cf1cf6..c82cf2ca5046781ecdc6526485491d945ee21b59 100644 (file)
--- a/docs/manual/ssl/ssl_faq.xml
+++ b/docs/manual/ssl/ssl_faq.xml
@@ -859,7 +859,7 @@ HTTPS to an Apache+mod_ssl server with Microsoft Internet Explorer (MSIE)?</titl
     MSIE 5.x has an error in the way it handles the SGC negotiation.</p>
     
     <p>And finally there are versions of MSIE which seem to require that
-    an SSL session can be reused (a totally non standard-conforming
+    an SSL session can be reused (a totally non-standard-conforming
     behaviour, of course). Connecting with those MSIE versions only work
     if a SSL session cache is used. So, as a work-around, make sure you
     are using a session cache (see the <directive module="mod_ssl"