changelog cleanups

inxi.changelog

@@ -74,31 +74,31 @@ etc for zfs.
 ENHANCEMENTS:
 
 1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo 
-types. Not sure how that one was missed, but there it is. This should tighten
+types. Not sure how that one was missed, but there it is. This should tighten 
 repo reports for dnf/yum/zypp types.
 
 2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for: 
 penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2. 
 
-3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
+3. Added xfwm as a compositor type, that had been left out, somewhat on purpose, 
-since xfwm can run in compositing or non compositing mode. But should show 
+since xfwm can run in compositing or non compositing mode. But should show since 
-since many users use compositing mode now.
+many users use compositing mode now.
 
 4. Added OpenMediaVault distro ID and systembase handlers.
 
 5. Going along with zfs bug fix 3, using zfs list data for free, size, 
-allocated. Trying to understand how zfs developers actually thought about this
+allocated. Trying to understand how zfs developers actually thought about this 
-is nearly impossible so just used what seems to correspond to reality most.
+is nearly impossible so just used what seems to correspond to reality most. Also 
-Also shows raw values for zfs data in RAID along with regular ones to make 
+shows raw values for zfs data in RAID along with regular ones to make clear 
-clear which is which value.
+which is which value.
 
-6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
+6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel. 
-Both vendors finally released some new CPUs and the data became available, 
+Both vendors finally released some new CPUs and the data became available, which 
-which doesn't always happen quickly.
+doesn't always happen quickly.
 
-7. A bunch of new disk vendors and vendor IDs added. Never stops, like the 
+7. A bunch of new disk vendors and vendor IDs added. Never stops, like the sands 
-sands of time, like the ocean waves, like the scuttling crabs scrounding around
+of time, like the ocean waves, like the scuttling crabs scrounging around in the 
-in the seaweed in the foam where the outgoing wave left its mark...
+seaweed in the foam where the outgoing wave left its mark...
 
 --------------------------------------------------------------------------------
 DOCUMENTATION:
@@ -115,17 +115,17 @@ clear.
 --------------------------------------------------------------------------------
 CODE CHANGES:
 
-1. Refactored uptime parser logic, the code and regex was just getting too 
+1. Refactored uptime parser logic, the code and regex was just getting too messy 
-messy and difficult to work with and debug, now it works similar to how the 
+and difficult to work with and debug, now it works similar to how the revised 
-revised BSD parsers run, the regex are pulled apart and made more granular so
+BSD parsers run, the regex are pulled apart and made more granular so a small 
-a small syntax change ideally won't break the detections as easily.
+syntax change ideally won't break the detections as easily.
 
-2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
+2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over 
 time I notice that almost invariably stuff done to save lines of code makes  
 code harder to read as the feature expands, so it's generally worth just 
-unravelling it so it all stacks and is easy to scan/read. Also removed extra
+unravelling it so it all stacks and is easy to scan/read. Also removed extra 
-white space in parens, which is something I'm leaning more towards but it's
+white space in parens, which is something I'm leaning more towards but it's not 
-not worth fixing all at once so it's just done where it's noticed.
+worth fixing all at once so it's just done where it's noticed.
 
 That's using: 
 if ( /test/ ){