Terribly sorry @jgilje

_posts/2021-12-01-86box-v3-0.md

@@ -209,7 +209,7 @@ Due to the way the PCI bus works, PCI-based machines have a limited number of sl
 
 {% include imageheading.html url="/assets/images/v3.0/linux.png" heading="One more thing: Linux is coming" %}
 
-This is quite definitely the request we've received the most ever since the 86Box project started. After a couple false starts over the years, we are glad to announce that **a Linux and macOS version is being worked on**, with initial porting done by [**Cacodemon345**](https://github.com/Cacodemon345), macOS support tweaks by [**dob205**](https://github.com/dob205), and a new cross-platform Qt user interface (pictured below) by [**jgilge**](https://github.com/jgilje), all newcomers to the project.
+This is quite definitely the request we've received the most ever since the 86Box project started. After a couple false starts over the years, we are glad to announce that **a Linux and macOS version is being worked on**, with initial porting done by [**Cacodemon345**](https://github.com/Cacodemon345), macOS support tweaks by [**dob205**](https://github.com/dob205), and a new cross-platform Qt user interface (pictured below) by [**jgilje**](https://github.com/jgilje), all newcomers to the project.
 
 As of writing, the user interface is not finished yet, as it took us some time to determine the right **UI toolkit** to use. However, v3.0 already has some of the groundwork done: **64-bit Windows builds** of 86Box are now available (though 32-bit builds are still recommended on 64-bit systems due to the slight performance impact), as we have located and fixed bugs related to the 64-bit dynamic recompiler, which is required for x64 and ARM64 Linux distributions as well as macOS on Intel and Apple Silicon.
 

_posts/2022-02-16-86box-v3-2.md

@@ -14,7 +14,7 @@ This is the February 2022 update to 86Box, and it's one we know many of you have
 
 ## Now with Linux
 
-This Linux version was made possible by the massive work put in by contributors like [**jgilge**](https://github.com/jgilje), [**Cacodemon345**](https://github.com/Cacodemon345), [**ts-korhonen**](https://github.com/ts-korhonen) and [**dob205**](https://github.com/dob205), who developed the cross-platform Qt user interface or otherwise helped with freeing our code from the shackles of Win32. This new interface should look and feel **almost exactly** like the old Windows one. A **macOS version** is also in the works, also powered by the new interface and supporting both Intel and Apple Silicon, though it wasn't ready in time for this release.
+This Linux version was made possible by the massive work put in by contributors like [**jgilje**](https://github.com/jgilje), [**Cacodemon345**](https://github.com/Cacodemon345), [**ts-korhonen**](https://github.com/ts-korhonen) and [**dob205**](https://github.com/dob205), who developed the cross-platform Qt user interface or otherwise helped with freeing our code from the shackles of Win32. This new interface should look and feel **almost exactly** like the old Windows one. A **macOS version** is also in the works, also powered by the new interface and supporting both Intel and Apple Silicon, though it wasn't ready in time for this release.
 
 Linux builds are distributed as [**AppImage**](https://appimage.org) binaries for maximum compatibility. We've tested these on distributions as old as **Ubuntu 16.04** and as new as **Manjaro 21.2.2**, but if you run into issues on your specific distro, [please let us know](/#social). Binaries for **x86_64**, **ARM32** and **ARM64** architectures are available; 32-bit x86 is currently not available due to a [packaging issue](https://github.com/AppImageCrafters/AppRun/issues/37). Of course, building 86Box from source and running it with system libraries is still an option, and there's a [community-maintained Arch Linux AUR package](https://aur.archlinux.org/packages/86box-git) which does just that.