Improve language.

diff --git a/blog/data/2016-12-23-isenkram.txt b/blog/data/2016-12-23-isenkram.txt
index 86cafd2c2c8b9863b11ddbfb13d85a0a608d90be..1a16c1c6c50bf7bcd4b3727a3ca3868383501bb0 100644 (file)
--- a/blog/data/2016-12-23-isenkram.txt
+++ b/blog/data/2016-12-23-isenkram.txt
@@ -2,14 +2,15 @@ Title: Appstream just learned how to map hardware to packages too!
 Tags: english, debian, isenkram
 Date: 2016-12-23 10:30
 
 Tags: english, debian, isenkram
 Date: 2016-12-23 10:30
 

-<p>I received a very nice christmas present today.  As my regular
+<p>I received a very nice Christmas present today.  As my regular

 readers probably know, I have been working on the
 <a href="http://packages.qa.debian.org/isenkram">the Isenkram
 readers probably know, I have been working on the
 <a href="http://packages.qa.debian.org/isenkram">the Isenkram

-system</a> for many years.  It make it easier for users to figure out
-what to install to get a given piece of hardware to work in Debian,
-and a key part of this system is a way to map hardware to packages.
-Isenkram have its own mapping database, and also uses data provided by
-each package using the AppStream metadata format.  And today,
+system</a> for many years.  The goal of the Isenkram system is to make
+it easier for users to figure out what to install to get a given piece
+of hardware to work in Debian, and a key part of this system is a way
+to map hardware to packages.  Isenkram have its own mapping database,
+and also uses data provided by each package using the AppStream
+metadata format.  And today,

 <a href="https://tracker.debian.org/pkg/appstream">AppStream</a> in
 Debian learned to look up hardware the same way Isenkram is doing it,
 ie using fnmatch():</p>
 <a href="https://tracker.debian.org/pkg/appstream">AppStream</a> in
 Debian learned to look up hardware the same way Isenkram is doing it,
 ie using fnmatch():</p>