blog: Various copyedit tweaks to 2026-01-31 post

Signed-off-by: Rune Morling <ermo@aerynos.com>

Author: ermo

src/content/docs/blog/2026/31/January 2026 project update/index.mdx

@@ -15,38 +15,43 @@ import { Aside } from "@astrojs/starlight/components";
 
 Kicking off 2026, activity across the AerynOS project has been moving at pace. Following our 2025 retrospective, we have seen a jump in followers across our social media accounts and an influx of people joining our Zulip server and getting involved, whether through general discussion or through packaging.
 
-The team has made good progress across several different workstreams including documentation efforts, packaging updates, improvements to our CDN setup, initial work towards our new branding (website and logo) and design work towards enabling new features in moss.
+The team has made good progress across several different workstreams including documentation efforts, packaging updates, improvements to our CDN setup, initial work towards our new branding (website and logo) and design work towards enabling new features in moss and our infrastructure.
 
 ## What’s new in the distro
 
 Package / stack updates for this iteration include:
 
-- COSMIC 1.0.3
+- COSMIC 1.0.4
 - GNOME 49.3
 - KDE Frameworks 6.22.0
 - KDE Gear 25.12.1
 - KDE Plasma 6.5.5
-- fish 4.3.3
-- firefox 147.0.1
+- brush 0.3.0-dev (bash compatible shell built w/ Rust)
+- dankmaterialshell 1.2.3 (build your own wayland desktop experience in material design style)
+- firefox 147.0.2
+- fish 4.3.3 (user friendly shell built w/ Rust)
+- foot terminal 1.25.0 (fast, wayland-native terminal emulator)
+- ghostty terminal 1.3.0-dev (virtual terminal built w/ zig)
+- glibc 2.43+git.144ba302
+- lact 0.8.3 (gui for tweaking GPU voltages, fan curves and frequencies)
 - linux 6.18.7
-- prism-launcher 10.0.2
-- vscodium v1.108.10359
-- wine 11
+- mangowc 0.10.10 (wayland compositor with eye candy effects)
+- mesa 25.3.4
+- nodejs 24.13.0
+- pipewire 1.4.10
+- prism-launcher 10.0.2 (minecraft launcher)
 - qemu 10.2.0
+- quickshell 0.2.1 (building blocks for wayland compositor-based desktop experiences)
 - ruby 4.0.1
-- zed: 0.218.7
-- brush 0.3.0-dev
-- foot terminal 1.25.0
-- ghostty terminal 1.3.0-dev
-- lact 0.8.3
-- quickshell 0.2.1
-- dankmaterialshell 1.2.3
-- pipewire 1.4.10
-- glibc 2.42+git.453e6b8d
-- nodejs 24.13.0
+- thunderbird 147.0.1
+- vscode 1.108.2
+- vscodium 1.108.10359
+- wine 11
+- zed 0.218.7 (text editor built w/ Rust)
 
 ... along with sundry additions and updates.
 
+
 ## Desktop Updates
 
 ### Cosmic
@@ -91,11 +96,11 @@ The latest KDE Plasma update brings:
 
 ### New Wayland Compositor Environments
 
-With increased interest around AerynOS, we have seen new contributors join the community with an interest in packaging up Wayland Compositor Environments. We are seeing active work towards MangoWC and ancillary packages that will make building your own Wayland-based Desktop Experience more feasible on AerynOS.
+With the increased interest surrounding AerynOS, we have seen some new contributors join the community and wanting to package up their favourite wayland compositors and supporting packages. Hence, after some mentoring, MangoWC and a gaggle of ancillary packages were landed this month, and they join the existing Niri and Sway wayland compositors in the package repository.
 
-To this end, we now have foot, quickshell and dankmaterialshell as a few examples of packages we have included in our repository in the last month. These are terminals and shells that are often used with Wayland Compositors and can be used across Niri, Sway and soon MangoWC on AerynOS.
+As a result, if you're the sort who prefers to assemble your own Desktop Experience, we now have foot, quickshell and dankmaterialshell as a few examples of packages you can use as a base to make your Desktop Experience "just so".
 
-As a reminder, we do not include Niri, Sway or MangoWC as options to install directly from our `lichen` installer. Users interested in building their own Desktop Experiences on AerynOS can use our `terminal-only` option and then install their preferred Wayland Compositor and associated packages of choice from the command line.
+As a reminder, we do not include MangoWC, Niri or Sway as options to install directly from our `lichen` installer. Users interested in building their own Desktop Experiences on AerynOS can use our `terminal-only` option and then install their preferred Wayland Compositor and associated packages of choice from the command line.
 
 <iframe title="Show &amp; Tell: MangoWC on AerynOS" width="1280" height="720" src="https://exquisite.tube/videos/embed/1R1WCHZyeGiQPKouVRMBPn" style="border: 0px;" allow="fullscreen" sandbox="allow-same-origin allow-scripts allow-popups allow-forms"></iframe>
 
@@ -131,7 +136,8 @@ The team have started work on refactoring error handling in `moss` with an early
 This is useful when troubleshooting, as it allows us to diagnose whether there is an issue with the user's internet connection, or with the package itself on our server.
 
 This error handling workstream will continue in the background to further improve the quality of human readable error output in our tooling.
- 
+
+
 ## Wider Project Updates
 
 ### Website redesign
@@ -148,9 +154,9 @@ If you are interested or experienced in website design and want to help out, joi
 
 Last year, the team set up Cloudflare as a CDN for our package repository and saw an improvement in download speeds. This was our first real experience administering Cloudflare and we left it pretty much in its default configuration.
 
-This month, we spent a little time tweaking which parts of our repository it was caching for how long. The result has been a big jump in the cache hit rate. Prior to the change, our best days would see around a 20% hit rate, which has now jumped to around 47%.
+This month, we spent a little time tweaking which parts of our repository it was caching for how long. The result has been a respectable jump in the cache hit rate.
 
-The end result should serve to increase the consistency and raw speed of downloads within moss when using AerynOS.
+The end result should serve to increase the consistency and speed of downloads within moss when using AerynOS from the unstable stream.
 
 ### Documentation
 
@@ -180,6 +186,7 @@ As and when we do make the transition to Codeberg, we would also like to sponsor
 
 Sponsorship, where we are able, is another way we feel we can support the open source community and as our own sponsorship / income grows, we will be in a better position to contribute to the upstream projects on which we rely.
 
+
 ## ISO refresh
 
 We are releasing our newest Alpha ISO, AerynOS 2026.01, which includes the updates we've worked on since the start of December, and which features the 6.18.7 kernel.
@@ -188,21 +195,6 @@ As usual, this is a Live GNOME ISO that merely serves as a delivery vehicle for
 
 The link for our 2026.01 ISO can be found on our [download](/download/) page.
 
-## Next Steps
-
-We have spent the month of January taking stock of our future development direction, including short and medium term goals.
-
-This has resulted in several nice refactors to how moss works internally, which will in turn make it significantly easier for us to implement some of the medium term features we have planned. It has also already helped us land a few planned features, such as better error messages and the in-progress `moss fetch` feature, which can be used to download .stones in advance for testing purposes.
-
-Next to that, we are also steadily working towards delivering the Versioned Repos, phase2 infrastructure feature set, which is about teaching moss how to seamlessly auto-update itself across breaking on-disk moss-format changes with no user-interaction.
-
-Currently, we are focusing on defining the necessary repository disk-layout and the format of the file at the root of the moss-format repo. This  will show moss which updates need to be made in which order before the new package repository versions -- containing new packages that rely on new package-management features -- can be used.
-
-Once complete, we will likely move our current repository layout to a `legacy` folder and test that older installs can update seamlessly in the process.
-
-Due to the work done during 2025 on the infrastructure code-base, enabling the seamless format-upgrade process is now a short-term goal, which -- when achieved -- will in turn open up the ability to focus on medium term goals that were previously gated on this specific functionality.
-
-We're very, very excited about what this will enable us to do in the future!
 
 ## Supporting the project
 
@@ -216,8 +208,25 @@ If you are following along with our project and are in a position to support us,
 
 <Kofi />
 
-## Thank You!
+### Thank You!
 
 We are very grateful for your support, be it financial or via project contributions in the form of carefully written bug reports, code contributions, design contributions, documentation updates, general feedback, package updates and overall enthusiasm around the project.
 
 In that vein, we would also like to give [Framework Computers](https://frame.work) a shout out for their generous support in the form of hardware sponsorship for project members now and in the past.
+
+
+## Next Steps
+
+We have spent the month of January taking stock of our future development direction, including short and medium term goals.
+
+This has resulted in several nice refactors to how moss works internally, which will in turn make it significantly easier for us to implement some of the medium term features we have planned. It has also already helped us prepare a few planned features, such as better error messages and the in-progress `moss fetch` feature, which can be used to download .stones in advance for testing purposes.
+
+Next to that, we are steadily working towards delivering the Versioned Repos, phase2 infrastructure feature set, which is about teaching moss how to seamlessly auto-update itself across breaking on-disk moss-format changes with no user-interaction.
+
+Currently, we are focusing on defining the necessary repository disk-layout and the format of the file at the root of the moss-format repo. This  will show moss which updates need to be made in which order before the new package repository versions -- containing new packages that rely on new package-management features -- can be used.
+
+Once complete, we will likely move our current repository layout to a `legacy` folder and test that older installs can update seamlessly in the process.
+
+Due to the work done during 2025 on the infrastructure code-base, enabling the seamless format-upgrade process is now a short-term goal, which -- when achieved -- will in turn open up the ability to focus on medium term goals that were previously gated on this specific functionality.
+
+We're very, very excited about what this will enable us to do in the future!