M contents/articles/convergence.md → contents/articles/convergence.md

@@ -9,7 +9,7 @@ Over the past few months I have been thinking about changing a few things related to this web site and my [projects](/projects). With the rise of AI slop and overwhelming bloat throughout the Internet, I have been longing for more simplicity and lightness in my digital life.
 
 ### Eee...
 
-So, for my last birthday, I bought myself a nice, fully functional, EeePC!  It's an 1001PXD model from 2011c with a nice 233GB SATA hard drive, an Atom processor (32bit) and (wow!) 2GB of RAM. That was for 40€ mind, including shipping. Not bad at all.
+So, for my last birthday, I bought myself a nice, fully functional, EeePC!  It's an 1001PXD model from 2011 with a nice 233GB SATA hard drive, a (32bit) Atom processor and (wow!) 2GB of RAM. That was for 40€ mind, including shipping. Not bad at all.
 
 > %float-right%
 > ![My EeePC](/days/2026-05-02.jpeg)
@@ -26,19 +26,19 @@ ### Moving away from GitHub
 
 This has been bothering me for a while, actually. GitHub, once the stronghold of open source software and the only place you'd ever need to be as a developer, is now, well, [bad](https://sfconservancy.org/GiveUpGitHub/).
 
-The solution? Easy: [Sourcehut](https://sr.ht). I had been using it as a mirror for most of my projects for quite some time, but I was not ready to switch, mainly the possibility to create GitHub actions to cross-compile my programs so that I could distribute the binaries when I released a new version. 
+The solution? Easy: [Sourcehut](https://sr.ht). I had been using it as a mirror for most of my projects for quite some time, but I was not ready to switch, mainly because of the possibility to create GitHub actions to cross-compile my programs so that I could distribute the binaries when I released a new version. 
 
-Actually, Sourcehut has an awesome [build](https://builds.sr.ht)service for *nix systems, but it doesn't offer a way to build for macOS and Windows. And for sure I always wanted to ship the binaries for my software for those platforms as well, right? Well, meh...
+Actually, Sourcehut has an awesome [build](https://builds.sr.ht) service targeting *nix systems, but it doesn't offer a way to build for macOS or Windows. And for sure I always wanted to ship the binaries for my software for those platforms as well, right? Well, meh...
 
 Truth is, I now have two kids and a full time job, I am the main user of my ecosystem of highly-opinionated tools and keeping all those actions running smoothly had become a second (or third) job. So I was like, you know what? No more binaries distributed for any release of my software! Ah, that felt really good, and gave me the final push to make the move official. 
 
-And it turns out, releases are overhyped. I was recently discussing with [Devine](https://wiki.xxiivv.com/site/devine_lu_linvega.html) about [Kelvin Versionjng](https://wiki.xxiivv.com/site/kelvin_versioning.html), and while I like the idea of software aiming at becoming more stable, I just didn't like the whole decreasing temperature thing, and the way dependencies are managed.
+And it turns out, releases are overhyped. I was recently discussing with [Devine](https://wiki.xxiivv.com/site/devine_lu_linvega.html) about [Kelvin Versioning](https://wiki.xxiivv.com/site/kelvin_versioning.html), and while I like the idea of software aiming at becoming more stable, I just didn't like the whole decreasing temperature thing, and the way dependencies are managed.
 
 But I like the concept of software _converging_ to ultimate stability, maturity, and dependability. Oh yes I did...
 
 ### Convergent Versioning
 
-What if I stopped stressing about releasing a version 1.0 of a particular piece of software, and just worried about the level of _completeness_ of that piece of software instead? That is the core philosophy behind [Convergent Versioning](/conver), my own alternative to Semantic Versioning and Kelvin Versioning. After years trying to be a good citizen and trying to follow semantic versioning for all my projects, I realized that it would be much simpler and useful to think about my projects in terms of _how complete they are_ rather than _whether they break compatibility or not_. 
+What if I stopped stressing about preparing for a version 1.0 of a particular piece of software, and just focused on the level of _completeness_ of that piece of software instead? That is the core philosophy behind [Convergent Versioning](/conver), my own alternative to Semantic Versioning and Kelvin Versioning. After years trying to be a good citizen and trying to follow semantic versioning for all my projects, I realized that it would be much simpler and useful to think about my projects in terms of _how complete they are_ rather than _whether they break compatibility or not_. 
 
 I am not expecting tons of people to embrace Convergent Versioning, but even if I will be the only user of this new alternative versioning system, at least it will make sense _for me_. 
 
@@ -65,7 +65,7 @@ - No JavaScript.
 - No objects or external content, for the matter. No video, no audio, obviously no WASM.
 - Images are allowed (JPG, PNG, and GIF), but only if served from the same origin as the web site. 
 
-Too strict? Perhaps. But now H3RALD.com is nearly SubWeb compliant (I still have to fix some external images), and I still don't think I gave up that much! The branding and styling is still recognizable, but it is much more lightweight and considerably simpler. And of course, it renders in Dillo just fine!
+Too strict? Perhaps. But now H3RALD.com is nearly SubWeb-compliant (I still have to fix some external images), and I still don't think I gave up that much! The branding and styling is still recognizable, but it is much more lightweight and considerably simpler. And of course, it renders in Dillo perfectly.
 
 ### Where to go from here