From: Yoshiki Hayashi <yoshiki@apache.org>
Date: Fri, 6 Aug 2004 06:59:50 +0000 (+0000)
Subject: Fix typo. is->it
X-Git-Tag: post_ajp_proxy~81
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6b45004e2467f89f731e500cedae0ee6d0ed92d3;p=apache

Fix typo. is->it


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

diff --git a/docs/manual/ssl/ssl_howto.html.en b/docs/manual/ssl/ssl_howto.html.en
index 621dcc0229..915393d502 100644
--- 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 1bb88aa13d..ff5c311d0f 100644
--- 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.9 $ -->
+<!-- $Revision: 1.10 $ -->
 
 <!--
  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>