From c38776af21f0c86cef6f8d01e1ce4d5e4f698113 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Date: Thu, 5 Mar 2009 10:37:25 +0100
Subject: doc typo fix
thanks to Trent W. Buck for alerting me.
---
doc/rsyslog_stunnel.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
(limited to 'doc/rsyslog_stunnel.html')
diff --git a/doc/rsyslog_stunnel.html b/doc/rsyslog_stunnel.html
index 104a672e..1d024934 100644
--- a/doc/rsyslog_stunnel.html
+++ b/doc/rsyslog_stunnel.html
@@ -22,7 +22,7 @@ a peek at your data. In some environments, this is no problem at all. In
others, it is a huge setback, probably even preventing deployment of syslog
solutions. Thankfully, there is an easy way to encrypt syslog communication. I
will describe one approach in this paper.
-The most straigthforward solution would be that the syslogd itself encrypts
+
The most straightforward solution would be that the syslogd itself encrypts
messages. Unfortuantely, encryption is only standardized in
RFC 3195. But there
is currently no syslogd that implements RFC 3195's encryption features,
@@ -237,4 +237,4 @@ comments or find bugs (I *do* bugs - no way... ;)), please
http://www.gnu.org/copyleft/fdl.html.
-