added doc fixes provided by Michael Biebl - thanks

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/history.html b/doc/history.html
index 48a64892..cd432293 100644
--- a/doc/history.html
+++ b/doc/history.html
@@ -11,11 +11,11 @@ MySQL databases and fully configurable output formats (including great timestamp
 Rsyslog was initiated by <a href="http://www.gerhards.net/rainer">Rainer Gerhards</a>. 
 If you are interested to learn why&nbsp; Rainer initiated&nbsp; the project, you 
 may want to read his blog posting on &quot;<a href="http://rgerhards.blogspot.com/2007/08/why-does-world-need-another-syslogd.html">why 
-the world neeeds another syslogd</a>&quot;.<p>Rsyslog has
+the world needs another syslogd</a>&quot;.<p>Rsyslog has
 been forked in <b>2004</b> from the <a href="http://www.infodrom.org/projects/sysklogd/">sysklogd standard package</a>.
 The goal of the
 rsyslog project is to provide a feature-richer and reliable
-syslog deamon while retaining drop-in replacement capabilities to stock syslogd. By "reliable", we mean support for reliable transmission
+syslog daemon while retaining drop-in replacement capabilities to stock syslogd. By "reliable", we mean support for reliable transmission
 modes like TCP or <a href="http://www.monitorware.com/Common/en/glossary/rfc3195.php">RFC 3195</a> 
 (syslog-reliable). We do NOT imply that the sysklogd package is unreliable.</p>
 <p>The name "rsyslog" stems back to the
@@ -26,7 +26,7 @@ Instead, it contained enhanced configurability and other enhancements
 changes. Also, questions asked on the loganalysis list and at other
 places indicated that RFC3195 is NOT a prime priority for users, but
 rather better control over the output format. So there we were, with
-a rsyslod that covers a lot of enhancements, but not a single one
+a rsyslogd that covers a lot of enhancements, but not a single one
 of these that made its name ;) Since version 0.9.2, receiving syslog messages 
 via plain tcp is finally supported, a bit later sending via TCP, too. Starting 
 with 1.11.0, RFC 3195 is finally support at the receiving side (a.k.a. &quot;listener&quot;). 
@@ -72,14 +72,14 @@ very busy time with many great additions.<p>In <b>July 2007</b>, Andrew
 Pantyukhin added BSD ports files for rsyslog and liblogging. We were strongly 
 encouraged by this too. It looks like rsyslog is getting more and more momentum. 
 Let's see what comes next...<p>Also in <b>July 2007</b> (and beginning of 
-August), Rainer remodled the output part of rsyslog. It got a clean object model 
+August), Rainer remodeled the output part of rsyslog. It got a clean object model 
 and is now prepared for a plug-in architecture. During that time, some base 
 ideas for the overall new object model appeared.<p>In <b>August 2007</b> 
-community involvment grew more and more. Also, more packages appeared. We were 
-quite happy about that. To facilitate user contributíons, we set up a
+community involvement grew more and more. Also, more packages appeared. We were 
+quite happy about that. To facilitate user contributions, we set up a
 <a href="http://wiki.rsyslog.com/">wiki</a> on August 10th, 2007. Also in August 
 2007, rsyslog 1.18.2 appeared, which is deemed to be quite close to the final 
-2.0.0 release. With its appearance, the pace of changes was deliberatly reduced, 
+2.0.0 release. With its appearance, the pace of changes was deliberately reduced, 
 in order to allow it to mature (see Rainers's
 <a href="http://rgerhards.blogspot.com/2007/07/pace-of-changes-in-rsyslog.html">
 blog post</a> on this topic, written a bit early, but covering the essence).<p>Be sure to visit Rainer's <a href="http://rgerhards.blogspot.com/">syslog block</a>
@@ -91,4 +91,4 @@ Don't be shy to post to either the blog or the
 	<li><a href="http://www.rsyslog.com/Topic4.phtml">the rsyslog change log</a></li>
 </ul>
 </body>
-</html>
\ No newline at end of file
+</html>