Many simple typos.

	RedHat's -> Red Hat's, underlaying -> underlying
	the Netherlands, the United Kingdom, the United States

	Additionally, ssl_howto.xml uses 'coherences' unclearly -- should this be 'interactions?.

	ssl_compat.xml uses 'compactified', which isn't a real word, but I'm not sure what it's intended to mean.


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

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/manual/ssl/ssl_faq.xml b/docs/manual/ssl/ssl_faq.xml
index 27fe959afa..8f9889ced1 100644
--- a/docs/manual/ssl/ssl_faq.xml
+++ b/docs/manual/ssl/ssl_faq.xml
@@ -16,7 +16,7 @@ he poses the right questions.</p>
 </blockquote>
 <p>This chapter is a collection of frequently asked questions (FAQ) and
 corresponding answers following the popular USENET tradition. Most of these
-questions occured on the Newsgroup <code><a href="news:comp.infosystems.www.servers.unix"
+questions occurred on the Newsgroup <code><a href="news:comp.infosystems.www.servers.unix"
 >comp.infosystems.www.servers.unix</a></code> or the mod_ssl Support
 Mailing List <code><a href="mailto:modssl-users@modssl.org"
 >modssl-users@modssl.org</a></code>. They are collected at this place
@@ -43,7 +43,7 @@ author.</p>
     Laurie's development cycle it then was re-assembled from scratch for
     Apache 1.3.0 by merging the old mod_ssl 1.x with the newer Apache-SSL
     1.18. From this point on mod_ssl lived its own life as mod_ssl v2. The
-    first publically released version was mod_ssl 2.0.0 from August 10th,
+    first publicly released version was mod_ssl 2.0.0 from August 10th,
     1998. As of this writing (August 1999) the current mod_ssl version 
     is 2.4.0.</p>
 
@@ -76,7 +76,7 @@ author.</p>
     <p>Additionally according to a <a
     href="http://www.apache.org/docs/misc/FAQ.html#year2000">Year 2000
     statement</a> from the Apache Group, the Apache webserver is Year 2000
-    compliant, too. But whether OpenSSL or the underlaying Operating System
+    compliant, too. But whether OpenSSL or the underlying Operating System
     (either a Unix or Win32 platform) is Year 2000 compliant is a different
     question which cannot be answered here.</p>
 </section>
@@ -89,9 +89,9 @@ author.</p>
     replaced the previous <dfn>CoCom</dfn> regime. 33 countries are signatories:
     Argentina, Australia, Austria, Belgium, Bulgaria, Canada, Czech Republic,
     Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Japan,
-    Luxembourg, Netherlands, New Zealand, Norway, Poland, Portugal, Republic
+    Luxembourg, the Netherlands, New Zealand, Norway, Poland, Portugal, Republic
     of Korea, Romania, Russian Federation, Slovak Republic, Spain, Sweden,
-    Switzerland, Turkey, Ukraine, United Kingdom and United States. For more
+    Switzerland, Turkey, Ukraine, the United Kingdom and the United States. For more
     details look at <a
     href="http://www.wassenaar.org/">http://www.wassenaar.org/</a>.</p>
 
@@ -678,7 +678,7 @@ Hosting to identify different SSL virtual hosts?</a></li>
 <section id="load"><title>Why has my webserver a higher load now that I run SSL there?</title>
 <p>Because SSL uses strong cryptographic encryption and this needs a lot of
     number crunching. And because when you request a webpage via HTTPS even
-    the images are transfered encrypted. So, when you have a lot of HTTPS
+    the images are transferred encrypted. So, when you have a lot of HTTPS
     traffic the load increases.</p>
 </section>
 
@@ -686,7 +686,7 @@ Hosting to identify different SSL virtual hosts?</a></li>
 the connection, although sometimes it works faster?</title>
 <p>Usually this is caused by using a <code>/dev/random</code> device for
     <code>SSLRandomSeed</code> which is blocking in read(2) calls if not
-    enough entropy is available. Read more about this problem in the refernce
+    enough entropy is available. Read more about this problem in the reference
     chapter under <code>SSLRandomSeed</code>.</p>
 </section>
 
@@ -726,9 +726,9 @@ shared cipher'' errors?</title>
 I try to connect to my freshly installed server?</title>
 <p>Either you have messed up your <code>SSLCipherSuite</code>
     directive (compare it with the pre-configured example in
-    <code>httpd.conf-dist</code>) or you have choosen the DSA/DH
+    <code>httpd.conf-dist</code>) or you have chosen the DSA/DH
     algorithms instead of RSA when you generated your private key
-    and ignored or overlooked the warnings.  If you have choosen
+    and ignored or overlooked the warnings.  If you have chosen
     DSA/DH, then your server no longer speaks RSA-based SSL ciphers
     (at least not until you also configure an additional RSA-based
     certificate/key pair). But current browsers like NS or IE only speak