Fix typo. is->it

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

diff --git a/docs/manual/ssl/ssl_howto.html.en b/docs/manual/ssl/ssl_howto.html.en
index 8a2efe6419ba6cffed177fcddd12e2f35e87381f..86abf0938fa3381f0ed4d967ca5d3836007234fc 100644 (file)
--- a/docs/manual/ssl/ssl_howto.html.en
+++ b/docs/manual/ssl/ssl_howto.html.en
@@ -31,7 +31,7 @@ and is left as an exercise for the reader.</p>
 <p>How to solve particular security constraints for an SSL-aware
 webserver is not always obvious because of the coherences between SSL,
 HTTP and Apache's way of processing requests. This chapter gives
-instructions on how to solve such typical situations. Treat is as a first
+instructions on how to solve such typical situations. Treat it as a first
 step to find out the final solution, but always try to understand the 
 stuff before you use it. Nothing is worse than using a security solution
 without knowing its restrictions and coherences.</p>

diff --git a/docs/manual/ssl/ssl_howto.xml b/docs/manual/ssl/ssl_howto.xml
index b17a1f9676820bcfd4daef4adf45ec2b21efc379..138fe8e6970c5843a71306034334dbc5002e2d2d 100644 (file)
--- a/docs/manual/ssl/ssl_howto.xml
+++ b/docs/manual/ssl/ssl_howto.xml
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8' ?>
 <!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
-<!-- $Revision: 1.3.2.8 $ -->
+<!-- $Revision: 1.3.2.9 $ -->
 
 <!--
  Copyright 2002-2004 The Apache Software Foundation
@@ -35,7 +35,7 @@ and is left as an exercise for the reader.</p>
 <p>How to solve particular security constraints for an SSL-aware
 webserver is not always obvious because of the coherences between SSL,
 HTTP and Apache's way of processing requests. This chapter gives
-instructions on how to solve such typical situations. Treat is as a first
+instructions on how to solve such typical situations. Treat it as a first
 step to find out the final solution, but always try to understand the 
 stuff before you use it. Nothing is worse than using a security solution
 without knowing its restrictions and coherences.</p>