You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by yo...@apache.org on 2004/08/06 08:59:51 UTC
cvs commit: httpd-2.0/docs/manual/ssl ssl_howto.html.en ssl_howto.xml
yoshiki 2004/08/05 23:59:51
Modified: docs/manual/ssl ssl_howto.html.en ssl_howto.xml
Log:
Fix typo. is->it
Revision Changes Path
1.12 +1 -1 httpd-2.0/docs/manual/ssl/ssl_howto.html.en
Index: ssl_howto.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_howto.html.en,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- ssl_howto.html.en 21 Feb 2004 00:31:45 -0000 1.11
+++ ssl_howto.html.en 6 Aug 2004 06:59:50 -0000 1.12
@@ -31,7 +31,7 @@
<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>
1.10 +2 -2 httpd-2.0/docs/manual/ssl/ssl_howto.xml
Index: ssl_howto.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_howto.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- ssl_howto.xml 17 Apr 2004 11:18:05 -0000 1.9
+++ ssl_howto.xml 6 Aug 2004 06:59:50 -0000 1.10
@@ -35,7 +35,7 @@
<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>