--- a/ChangeLog	Thu May 20 21:21:22 2010 +0200
+++ b/ChangeLog	Thu May 20 21:22:33 2010 +0200
@@ -1,4 +1,5 @@
-This file summarizes the (implementation) changes in a technical view.
+This ChangeLog file summarizes the (implementation) changes from the
+technical view.
 
 The code repository log file provides the changes in full detail.
 
@@ -6,7 +7,7 @@
 technical speach and with focus on compatibility.
 
 
-0.2.22	Thu, 13 May 2010 17:31:40 +0200
+0.2.22	Thu, 20 May 2010 21:19:56 +0200
 	* new maintainer: markus schnalke <meillo@marmaro.de>. See NEWS.
 	* fixed expanding of $prefix for template files. Thanks to Johann
 	  Felix Soden.

--- a/NEWS	Thu May 20 21:21:22 2010 +0200
+++ b/NEWS	Thu May 20 21:22:33 2010 +0200
@@ -1,4 +1,4 @@
-This files lists changes which may be important for you, especially
+This NEWS file lists changes which may be important for you, especially
 in regard to compatiblity in upgrades.
 
 See ChangeLog file for more details and technical changes that don't
@@ -10,13 +10,13 @@
 0.2.22
 
 - Hello, I'm meillo, the new maintainer and developer of masqmail. Oku
-handed masqmail over to me, as he wasn't active anymore.
+handed masqmail over to me, because he wasn't active anymore.
 
 - This release includes various fixes for problems in 0.2.21, mainly
 based on bugs from Debian.
 
 - Distribution specific data has been excluded from the distribution,
-but is separately available on the website.
+but is separately available on the project's website.
 
 - Man pages will not be generated from xml sources in future, but the
 nroff sources will be maintained directly.
@@ -25,6 +25,7 @@
 /var/run/masqmail/masqmail-route, as it already was in the Debian
 package.
 
+
 0.2.21
 
 - Retrospective: Probably, this version was not published in the usual
@@ -33,9 +34,10 @@
 log files as user `mail'. It also changes the location for pid files;
 they are stored in /var/run/masqmail/ now.
 
+
 0.2.18
 
-- delivery warnings and failures are now also implermented if the
+- delivery warnings and failures are now also implemented if the
 connection to a server fails. Because masqmail is designed for dialup
 networks, a connection failure will merely generate a warning by default.
 If you deliver in a local network and use the default local_net route,