diff --git a/inxi.changelog b/inxi.changelog
index 5e3725c..0bbbf42 100644
--- a/inxi.changelog
+++ b/inxi.changelog
@@ -20,19 +20,19 @@ when Ansible or MOTD started inxi. This is because they are not tty so trip the
 non tty flag, which assumes it's in IRC in that case. The fix was to add a 
 whitelist of known clients based on the parent name inxi discovers while running 
 inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file 
-issue reports then not follow them? Who knows.
+issue reports then not follow up on them? Who knows.
 Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi 
 which disables the tty test as well. To handle that scenario, that is, when inxi is 
 not first in the pipe, I added many known terminal client names to the whitelists.
-This works in my tests, though the possible terminals, or programs with embedded
-terminals, is quite large, but inxi handles most of them automatically. When it 
-doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
+This works in my tests, though the set of possible terminals, or programs with 
+embedded terminals, is quite large, but inxi handles most of them automatically. When
+it doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
 in the meantime.
 2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
 in some character sets, like greek or russian utf8. The fix was more of a work-around
 than a true fix, but inxi now simply checks the weather local time output for wide 
 characters, and if detected, switches the local date/time format to iso standard, 
-which is does not contain non ascii characters as far as I can tell. This seemed to
+which does not contain non ascii characters as far as I can tell. This seemed to
 fix the issue.
 3. Added iso9660 from excluded file systems for partitions, not sure how inxi 
 missed that one for so long.