diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index c2873429..43ce6154 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -1,4 +1,4 @@
-# SPDX-FileCopyrightText: 2026 AerynOS Developers
+# SPDX-FileCopyrightText: 2026 aerynOS Developers
 # SPDX-License-Identifier: MPL-2.0
 
 name: CI
diff --git a/.typos.toml b/.typos.toml
index a61e2a10..41f1ce2d 100644
--- a/.typos.toml
+++ b/.typos.toml
@@ -1,4 +1,4 @@
-# SPDX-FileCopyrightText: 2026 AerynOS Developers
+# SPDX-FileCopyrightText: 2026 aerynOS Developers
 # SPDX-License-Identifier: MPL-2.0
 
 [default]
diff --git a/astro.config.mjs b/astro.config.mjs
index 92aae807..399ebb6b 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -19,7 +19,7 @@ export default defineConfig({
         light: "@/images/logo-light-mode.svg",
         replacesTitle: false,
       },
-      title: "AerynOS Docs",
+      title: "aerynOS Docs",
       // Multilingual reference implementation:
       // locales: {
       //   root: { label: "English", lang: "en" },
@@ -39,7 +39,7 @@ export default defineConfig({
         {
           icon: "github",
           label: "GitHub",
-          href: "https://github.com/AerynOS/dotdev",
+          href: "https://github.com/aerynOS/dotdev",
         },
         {
           icon: "zulip",
@@ -49,12 +49,12 @@ export default defineConfig({
         {
           icon: "mastodon",
           label: "Mastodon",
-          href: "https://hachyderm.io/@AerynOS",
+          href: "https://hachyderm.io/@aerynOS",
         },
       ],
       customCss: ["@/styles/global.css"],
       editLink: {
-        baseUrl: "https://github.com/AerynOS/dotdev/edit/main/",
+        baseUrl: "https://github.com/aerynOS/dotdev/edit/main/",
       },
       lastUpdated: true,
       components: {
@@ -85,7 +85,7 @@ export default defineConfig({
       ],
       sidebar: [
         {
-          label: "AerynOS",
+          label: "aerynOS",
           items: [
             { slug: "aerynos" },
             { slug: "aerynos/overview" },
diff --git a/public/favicon.svg b/public/favicon.svg
index 5a317807..f8f70c1a 100644
--- a/public/favicon.svg
+++ b/public/favicon.svg
@@ -8,8 +8,8 @@
    version="1.1"
    id="svg1"
    inkscape:version="1.4.3 (0d15f75042, 2025-12-25)"
-   sodipodi:docname="AerynOS.svg"
-   inkscape:export-filename="AerynOS (icon).png"
+   sodipodi:docname="aerynOS.svg"
+   inkscape:export-filename="aerynOS (icon).png"
    inkscape:export-xdpi="65.360001"
    inkscape:export-ydpi="65.360001"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
diff --git a/src/assets/macros/README.md b/src/assets/macros/README.md
index aab98f96..6c0d6179 100644
--- a/src/assets/macros/README.md
+++ b/src/assets/macros/README.md
@@ -1,3 +1,3 @@
-Update this directory from github.com/AerynOS/moss/ (boulder/data/)
+Update this directory from github.com/aerynOS/moss/ (boulder/data/)
 Rebuilds will pick up new macro changes.
 Markdown files still need to be created per group.
diff --git a/src/content/docs/Developers/Stone/V1/index.mdx b/src/content/docs/Developers/Stone/V1/index.mdx
index 9df36e0c..cf2c467c 100644
--- a/src/content/docs/Developers/Stone/V1/index.mdx
+++ b/src/content/docs/Developers/Stone/V1/index.mdx
@@ -7,7 +7,7 @@ copyright: "Copyright © 2025 aerynOS Developers"
 ---
 import DirectoryList from '@components/DirectoryList.astro';
 
-The v1 of the Stone format is the version currently employed by AerynOS, and is the first revision of our format.
+The v1 of the Stone format is the version currently employed by aerynOS, and is the first revision of our format.
 
 :::tip
 The contents below extend the version-agnostic components of the Stone format.
diff --git a/src/content/docs/Developers/Stone/index.mdx b/src/content/docs/Developers/Stone/index.mdx
index 8ee3c0d2..8af6faef 100644
--- a/src/content/docs/Developers/Stone/index.mdx
+++ b/src/content/docs/Developers/Stone/index.mdx
@@ -8,7 +8,7 @@ copyright: "Copyright © 2025 aerynOS Developers"
 import DirectoryList from '@components/DirectoryList.astro';
 
 The Stone format is a binary format designed to be type-safe and version-aware.
-It is used to package and distribute software in AerynOS, in fact both the packages themselves
+It is used to package and distribute software in aerynOS, in fact both the packages themselves
 and the index file of repositories use the Stone format.
 
 Anything encoded in the Stone format is called a *stone*.
diff --git a/src/content/docs/Developers/Stone/prelude.mdx b/src/content/docs/Developers/Stone/prelude.mdx
index b95a2360..d750adb2 100644
--- a/src/content/docs/Developers/Stone/prelude.mdx
+++ b/src/content/docs/Developers/Stone/prelude.mdx
@@ -22,7 +22,7 @@ fields can be handled separately from version and format detection. This is a 32
 It's the [magic number](https://en.wikipedia.org/wiki/Magic_number_(programming)) of the Stone format.
 
 The `magic` field always contains `['\0', 'M', 'O', 'S']`.
-It is defined after AerynOS's package manager: `moss`.
+It is defined after aerynOS's package manager: `moss`.
 
 In the Rust language it is defined as:
 
diff --git a/src/content/docs/Developers/index.mdx b/src/content/docs/Developers/index.mdx
index e4e2af98..b4984533 100644
--- a/src/content/docs/Developers/index.mdx
+++ b/src/content/docs/Developers/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Developers
 lastUpdated: 2025-03-28T05:28:00Z
-description: AerynOS developer documentation
+description: aerynOS developer documentation
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -13,6 +13,6 @@ import DirectoryList from '@components/DirectoryList.astro';
     This documentation is only a stub and serves as a placeholder for future content. In time, the full format and payloads of of `moss` will be documented, along with other technologies such as `blsforme`, `os-info`, etc.
 </Aside>
 
-AerynOS includes some bespoke technologies and formats that are used to package, distribute, and introspect deployed software. This section of the documentation provides an overview of these technologies and formats.
+aerynOS includes some bespoke technologies and formats that are used to package, distribute, and introspect deployed software. This section of the documentation provides an overview of these technologies and formats.
 
 <DirectoryList/>
diff --git a/src/content/docs/FAQ/aerynos-features.mdx b/src/content/docs/FAQ/aerynos-features.mdx
index 2f85d96b..3c0fbffa 100644
--- a/src/content/docs/FAQ/aerynos-features.mdx
+++ b/src/content/docs/FAQ/aerynos-features.mdx
@@ -1,7 +1,7 @@
 ---
-title: AerynOS Features
+title: aerynOS Features
 lastUpdated: 2026-01-15T12:25:00Z
-description: How to use the key features of AerynOS
+description: How to use the key features of aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -25,13 +25,13 @@ sudo moss sync
 
 Hold down or mash your Space key repeatedly after your computer starts up.
 
-### How do I verify the integrity of my install states in AerynOS?
+### How do I verify the integrity of my install states in aerynOS?
 
 ```sudo moss state verify```
 
 Tack on ```--help``` to see the options for verify.
 
-### How do I clean out older install states in AerynOS?
+### How do I clean out older install states in aerynOS?
 
 ```sudo moss state prune```
 
diff --git a/src/content/docs/FAQ/filesystems.mdx b/src/content/docs/FAQ/filesystems.mdx
index 04cebb42..ffdba2c7 100644
--- a/src/content/docs/FAQ/filesystems.mdx
+++ b/src/content/docs/FAQ/filesystems.mdx
@@ -1,7 +1,7 @@
 ---
 title: Filesystems
 lastUpdated: 2026-01-15T12:25:00Z
-description: Information about filesystem support on AerynOS
+description: Information about filesystem support on aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -10,26 +10,26 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 ### Why do you recommend the xfs filesystem for the root partition?
 
-[Testing has shown](https://github.com/AerynOS/os-tools/blob/main/moss-filesystem-performance.md) that, due to how moss saves rollback states, xfs is by far the quickest filesystem in practice for AerynOS root partition usage.
+[Testing has shown](https://github.com/aerynOS/os-tools/blob/main/moss-filesystem-performance.md) that, due to how moss saves rollback states, xfs is by far the quickest filesystem in practice for aerynOS root partition usage.
 
 We currently do not recommend either ext4 or f2fs root partitions, because testing has shown that they offer very poor performance on the first update (sudo moss sync -u) after a cold start of your computer compared to xfs.
 
-### Do you support installing AerynOS on ext4?
+### Do you support installing aerynOS on ext4?
 
-We currently **strongly recommend** that you use **xfs** on your root partition for the best experience with moss and AerynOS.
+We currently **strongly recommend** that you use **xfs** on your root partition for the best experience with moss and aerynOS.
 
-### Do you support installing AerynOS on f2fs?
+### Do you support installing aerynOS on f2fs?
 
-We currently **strongly recommend** that you use **xfs** on your root partition for the best experience with moss and AerynOS.
+We currently **strongly recommend** that you use **xfs** on your root partition for the best experience with moss and aerynOS.
 
-### Do you support installing AerynOS on btrfs?
+### Do you support installing aerynOS on btrfs?
 
 Not yet
 
-### Do you support installing AerynOS on bcachefs?
+### Do you support installing aerynOS on bcachefs?
 
 Not yet
 
-### Do you support installing AerynOS on ZFS?
+### Do you support installing aerynOS on ZFS?
 
 Not at this stage. We may or may not decide to support it at some unspecified point in the future, provided we can guarantee that we are legally in the clear to do so.
diff --git a/src/content/docs/FAQ/general-faq.mdx b/src/content/docs/FAQ/general-faq.mdx
index 7a8e7065..133498f7 100644
--- a/src/content/docs/FAQ/general-faq.mdx
+++ b/src/content/docs/FAQ/general-faq.mdx
@@ -8,9 +8,9 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 # Project identity
 
-### What does AerynOS mean and how do I pronounce it?
+### What does aerynOS mean and how do I pronounce it?
 
-AerynOS is a stylized spelling of "Erin", alluding to the project's Irish roots.
+aerynOS is a stylized spelling of "Erin", alluding to the project's Irish roots.
 It is pronounced exactly the same as "Erin" - "AIR-in" OS.
 It's also a play on "aer" and the phonetic "air" sound,
 indicative of our desire to produce an open, trusted and high-performance operating system.
@@ -19,7 +19,7 @@ It's pronounced as "AIR-in" OS.
 
 ### What was Serpent OS?
 
-Serpent OS is the former name of AerynOS. We [announced our rebrand](https://aerynos.com/blog/2025/02/14/evolve-this-os/) back in February 2025, which culminated with the inaugural release of AerynOS 2025.03 on March 25th, 2025. Per the announcement, our desire to rebrand was chiefly driven due to effectively being lumbered with a hastily chosen name, that poorly reflected the project's goals and aspirations.
+Serpent OS is the former name of aerynOS. We [announced our rebrand](https://aerynos.com/blog/2025/02/14/evolve-this-os/) back in February 2025, which culminated with the inaugural release of aerynOS 2025.03 on March 25th, 2025. Per the announcement, our desire to rebrand was chiefly driven due to effectively being lumbered with a hastily chosen name, that poorly reflected the project's goals and aspirations.
 
 The project itself remains the same, with the same goals and aspirations, but with a new name and a fresh coat of paint.
 
@@ -39,7 +39,7 @@ For now, log out and back in again and they will show up.
 
 ### How do I configure custom kernel command line parameters applied at each boot?
 
-See the [blsforme repo readme](https://github.com/AerynOS/blsforme/?tab=readme-ov-file#filesystem-layout) for the expected format.
+See the [blsforme repo readme](https://github.com/aerynOS/blsforme/?tab=readme-ov-file#filesystem-layout) for the expected format.
 
 Typically, it is necessary to change the installed system state with `moss` for command-line snippets to take effect.
 
@@ -61,25 +61,25 @@ See above.
 
 For now, we encourage users to use flatpaks for the applications we do not yet carry in our repository.
 
-Currently, we are focusing on adding must-have packages for platform bring-up, for things that give us a development edge, or for things that help us showcase AerynOS capabilities.
+Currently, we are focusing on adding must-have packages for platform bring-up, for things that give us a development edge, or for things that help us showcase aerynOS capabilities.
 
-If the use-case for the package you are proposing is in line with the ethos above, you can make a package request [here](https://github.com/AerynOS/recipes/issues/new/choose)
+If the use-case for the package you are proposing is in line with the ethos above, you can make a package request [here](https://github.com/aerynOS/recipes/issues/new/choose)
 
-### Where can I learn how to package for AerynOS?
+### Where can I learn how to package for aerynOS?
 
 Consult the packaging documentation [here](/packaging/).
 
-In addition, consult the AerynOS [recipes/ repository](https://github.com/AerynOS/recipes).
+In addition, consult the aerynOS [recipes/ repository](https://github.com/aerynOS/recipes).
 
-Finally, join the [AerynOS Zulip space](https://aerynos.zulipchat.com/join/fuqokhsomj5mzqj6akqaiqlr/) and make sure to join the #Onboarding channel in the General - Public space.
+Finally, join the [aerynOS Zulip space](https://aerynos.zulipchat.com/join/fuqokhsomj5mzqj6akqaiqlr/) and make sure to join the #Onboarding channel in the General - Public space.
 
 # Project Questions
 
-### Which distribution is AerynOS derived from?
+### Which distribution is aerynOS derived from?
 
-AerynOS has been bootstrapped and built from scratch and is not based on any other distro.
+aerynOS has been bootstrapped and built from scratch and is not based on any other distro.
 
-This implies that AerynOS has its own:
+This implies that aerynOS has its own:
 
 - package manager (`moss`)
 - package build tool (`boulder`)
@@ -88,21 +88,21 @@ This implies that AerynOS has its own:
   - the builder-as-a-service middleware (`avalanche`)
   - the package repository manager (`vessel`)
 
-This also implies that AerynOS does NOT build upon or use either:
+This also implies that aerynOS does NOT build upon or use either:
 
 - `.rpm` related tooling from Red Hat
 - `.deb` related tooling from the Debian Project
 - Arch-related tooling
 
-### When will AerynOS be considered stable?
+### When will aerynOS be considered stable?
 
-AerynOS is taking on the ambitious task of creating a distribution from scratch, whilst building its own tooling and solutions for this.
+aerynOS is taking on the ambitious task of creating a distribution from scratch, whilst building its own tooling and solutions for this.
 
 As such, there is no official ETA.
 
 Now that the project has hit alpha status, you will see frequent updates and progress reports.
 
-### What is AerynOS' position on the use of LLMs
+### What is aerynOS' position on the use of LLMs
 
 Contributions must not include content generated by large language models or other probabilistic tools like ChatGPT, Claude, and Copilot.
 
@@ -117,6 +117,6 @@ This ban of LLM-generated content applies to all parts of the projects, includin
 
 #### Project-related use of LLMs
 
-We heavily discourage the use of LLM chat bots as a replacement for reading AerynOS's documentation.
+We heavily discourage the use of LLM chat bots as a replacement for reading aerynOS's documentation.
 
 Support requests referencing misleading or false LLM output relating to the project may be ignored, since it is a waste of time for us to "debug" where things went wrong based on this output before human support was sought. Once you're ready to submit your code, create a pull request, and one of our maintainers will review it.
diff --git a/src/content/docs/FAQ/index.mdx b/src/content/docs/FAQ/index.mdx
index c683bcc5..a0e2b949 100644
--- a/src/content/docs/FAQ/index.mdx
+++ b/src/content/docs/FAQ/index.mdx
@@ -1,13 +1,13 @@
 ---
 title: FAQ
 lastUpdated: 2025-03-28T05:28:00Z
-description: Frequently Asked Questions about AerynOS
+description: Frequently Asked Questions about aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 import DirectoryList from '@components/DirectoryList.astro';
 
-Our FAQ section provides answers to frequently asked questions about AerynOS. If you have any questions that are not answered here, please feel free to reach out to us via [Zulip](https://aerynos.zulipchat.com).
+Our FAQ section provides answers to frequently asked questions about aerynOS. If you have any questions that are not answered here, please feel free to reach out to us via [Zulip](https://aerynos.zulipchat.com).
 
 The FAQ section, by it's nature, is a work in progress and subject to change.
 
diff --git a/src/content/docs/FAQ/installation.mdx b/src/content/docs/FAQ/installation.mdx
index 07c6ef7d..b46ea6ef 100644
--- a/src/content/docs/FAQ/installation.mdx
+++ b/src/content/docs/FAQ/installation.mdx
@@ -1,7 +1,7 @@
 ---
 title: Installation FAQ
 lastUpdated: 2026-01-15T12:25:00Z
-description: Installation FAQ for AerynOS
+description: Installation FAQ for aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -10,9 +10,9 @@ import { Aside } from "@astrojs/starlight/components";
 
 # Installation Questions
 
-### Which CPUs does AerynOS support?
+### Which CPUs does aerynOS support?
 
-AerynOS is currently only compiled for the x86-64-v2 target architecture, which means that it will run on CPUs supporting x86-64-v2 or greater psABI feature levels.
+aerynOS is currently only compiled for the x86-64-v2 target architecture, which means that it will run on CPUs supporting x86-64-v2 or greater psABI feature levels.
 
 Checking the currently supported x86-64 psABI feature level of a system can be done by typing the following command in a terminal as a normal user:
 
@@ -29,34 +29,34 @@ On an x86-64-v2 based system, you will see the following output:
 ```
 
 <Aside type="note">
-    If the x86-64-v3 and x86-64-v4 psABI feature levels were supported, they would also show `(supported, searched)` next to them. AerynOS will still work on these systems.
+    If the x86-64-v3 and x86-64-v4 psABI feature levels were supported, they would also show `(supported, searched)` next to them. aerynOS will still work on these systems.
 </Aside>
 
-### Does AerynOS offer NVIDIA GPU support?
+### Does aerynOS offer NVIDIA GPU support?
 
 Due to the way NVIDIA distributes its drivers, maintaining them in a distro is labor-intensive and frustrating when they do not work as advertised.
 
-Given AerynOS is in the Alpha development stage, only limited, best effort NVIDIA enablement related to cards supported by the so-called nvidia-open-gpu-kernel-modules is currently offered.
+Given aerynOS is in the Alpha development stage, only limited, best effort NVIDIA enablement related to cards supported by the so-called nvidia-open-gpu-kernel-modules is currently offered.
 
-You can check the status of NVIDIA support in [AerynOS/recipes#435](https://github.com/AerynOS/recipes/issues/435)
+You can check the status of NVIDIA support in [aerynOS/recipes#435](https://github.com/aerynOS/recipes/issues/435)
 
-### Does AerynOS support being installed alongside another OS?
+### Does aerynOS support being installed alongside another OS?
 
 Officially? Not yet.
 
-You can try, but there is no guarantee that AerynOS won't eat your other OS.
+You can try, but there is no guarantee that aerynOS won't eat your other OS.
 
 You have been warned.
 
-### What is the recommended partition layout for AerynOS?
+### What is the recommended partition layout for aerynOS?
 
-In practice, we recommend that you install AerynOS to a separate drive with:
+In practice, we recommend that you install aerynOS to a separate drive with:
 
 - A >=256MB ESP FAT32 partition (type 1 in fdisk).
   -   This must be manually formatted for the installer to recognize it.
 - A 4GB XBOOTLDR FAT32 partition (type 142 in fdisk, bls_boot in gparted).
   - This must be manually formatted for the installer to recognize it.
-  - This partition is large, because it is where the AerynOS kernel+initramfs and (in the future) rescue image files will be saved.
+  - This partition is large, because it is where the aerynOS kernel+initramfs and (in the future) rescue image files will be saved.
 - A >20 GB system xfs partition
   - This must be manually formatted for the installer to recognize it.
   - The larger the xfs system (/ or root) partition is, the more OS /usr directory rollback states it can support in /.moss/.
@@ -86,4 +86,4 @@ nvme1n1
 ermo@virgil:~
 ```
 
-NB: Remember, there is nothing stopping you from creating an extra partition, formatting it with a filesystem of your choice, and then configuring /etc/fstab to mount it as /home after AerynOS has been installed. You can do this if you want to use a different filesystem than xfs for your /home folders for whatever reason.
+NB: Remember, there is nothing stopping you from creating an extra partition, formatting it with a filesystem of your choice, and then configuring /etc/fstab to mount it as /home after aerynOS has been installed. You can do this if you want to use a different filesystem than xfs for your /home folders for whatever reason.
diff --git a/src/content/docs/FAQ/lacking-features.mdx b/src/content/docs/FAQ/lacking-features.mdx
index 7c6873ed..4da1f601 100644
--- a/src/content/docs/FAQ/lacking-features.mdx
+++ b/src/content/docs/FAQ/lacking-features.mdx
@@ -1,7 +1,7 @@
 ---
 title: Lacking Features
 lastUpdated: 2026-01-15T12:25:00Z
-description: What are the features known to be missing in AerynOS?
+description: What are the features known to be missing in aerynOS?
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -12,18 +12,18 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 Secure Boot is a UEFI firmware security feature that ensures only digitally signed, trusted software, such as operating system loaders and drivers, can run during the startup process. This prevents malicious rootkits or an unauthorized OS from loading. It is a mandatory requirement for Windows 11 and is looked for as an additional security feature on Linux distributions.
 
-The AerynOS project is committed to providing Secure Boot support for its users in the future. However, this will come further down the line.
+The aerynOS project is committed to providing Secure Boot support for its users in the future. However, this will come further down the line.
 
 ### Dual booting from the same drive
 
-Officially, this is not yet supported when running AerynOS. We know of some more experienced users who have successfully installed AerynOS alongside other operating systems however this is done at their own risk.
+Officially, this is not yet supported when running aerynOS. We know of some more experienced users who have successfully installed aerynOS alongside other operating systems however this is done at their own risk.
 
-Our tooling is currently developed purely for making sure AerynOS is installed correctly and makes no consideration for other operating systems. As such, we highly recommend users avoid trying to dual boot with another OS from the same drive.
+Our tooling is currently developed purely for making sure aerynOS is installed correctly and makes no consideration for other operating systems. As such, we highly recommend users avoid trying to dual boot with another OS from the same drive.
 
-If you have multiple drives in your system, you could dedicate one drive to AerynOS and another to your other OS.
+If you have multiple drives in your system, you could dedicate one drive to aerynOS and another to your other OS.
 
 ### Disk encryption
 
 Disk encryption is a security feature that encrypts the data on a hard drive or solid-state drive (SSD) to protect it from unauthorized access. This is done by using a key to encrypt the data before it is written to the drive and decrypting it when it is read.
 
-The AerynOS project is committed to providing disk encryption support for its users in the future. However, this will come further down the line.
+The aerynOS project is committed to providing disk encryption support for its users in the future. However, this will come further down the line.
diff --git a/src/content/docs/FAQ/socials.mdx b/src/content/docs/FAQ/socials.mdx
index 3b2a5767..13d44b49 100644
--- a/src/content/docs/FAQ/socials.mdx
+++ b/src/content/docs/FAQ/socials.mdx
@@ -1,22 +1,22 @@
 ---
 title: Social engagement
 lastUpdated: 2026-01-15T12:25:00Z
-description: FAQ around social engagement for AerynOS
+description: FAQ around social engagement for aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 # Social engagement
 
-### Is it ok to share links to video content of AerynOS in action in the Zulip rooms?
+### Is it ok to share links to video content of aerynOS in action in the Zulip rooms?
 
-Yes! We absolutely love seeing people using AerynOS in the wild!
+Yes! We absolutely love seeing people using aerynOS in the wild!
 
-- Please first share them as a post in the [Show and Tell category](https://github.com/orgs/AerynOS/discussions/categories/show-and-tell),
-- Then, share a link to your post in the [AerynOS Zulip space](https://aerynos.zulipchat.com/join/fuqokhsomj5mzqj6akqaiqlr/) in the #Show-and-Tell channel in the General - Public space so the link to the video doesn't get lost in the Zulip chat.
+- Please first share them as a post in the [Show and Tell category](https://github.com/orgs/aerynOS/discussions/categories/show-and-tell),
+- Then, share a link to your post in the [aerynOS Zulip space](https://aerynos.zulipchat.com/join/fuqokhsomj5mzqj6akqaiqlr/) in the #Show-and-Tell channel in the General - Public space so the link to the video doesn't get lost in the Zulip chat.
 
 ### Why don't you have a Discord server?
 
-AerynOS is an open-source project that values transparency, collaboration, and community engagement. When looking at Discord, it is a closed-source platform that we believe **has different priorities**, specifically around monetization and data collection.
+aerynOS is an open-source project that values transparency, collaboration, and community engagement. When looking at Discord, it is a closed-source platform that we believe **has different priorities**, specifically around monetization and data collection.
 
-To this end, AerynOS would much rather promote the use of an open-source community platform such as Zulip. In the time we have been using Zulip, we have been very happy with the platform and how it has enabled us to build a strong and engaged community.
+To this end, aerynOS would much rather promote the use of an open-source community platform such as Zulip. In the time we have been using Zulip, we have been very happy with the platform and how it has enabled us to build a strong and engaged community.
diff --git a/src/content/docs/Packaging/Recipes/System Accounts/overview.mdx b/src/content/docs/Packaging/Recipes/System Accounts/overview.mdx
index 94f1f2d5..f6705897 100644
--- a/src/content/docs/Packaging/Recipes/System Accounts/overview.mdx	
+++ b/src/content/docs/Packaging/Recipes/System Accounts/overview.mdx	
@@ -1,14 +1,14 @@
 ---
 title: 'Overview'
 lastUpdated: 2024-09-08T00:15:31Z
-description: "Stateless management of AerynOS user accounts"
+description: "Stateless management of aerynOS user accounts"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 import { Aside } from '@astrojs/starlight/components';
 
-As a stateless distribution, AerynOS does not permit the modification of `/etc/passwd` and co by packages or triggers. Instead, we integrate `nss-systemd` and `userdb`.
+As a stateless distribution, aerynOS does not permit the modification of `/etc/passwd` and co by packages or triggers. Instead, we integrate `nss-systemd` and `userdb`.
 
 <Aside type="caution">
 
diff --git a/src/content/docs/Packaging/Recipes/System Accounts/users.mdx b/src/content/docs/Packaging/Recipes/System Accounts/users.mdx
index 1e733f9c..16742e6e 100644
--- a/src/content/docs/Packaging/Recipes/System Accounts/users.mdx	
+++ b/src/content/docs/Packaging/Recipes/System Accounts/users.mdx	
@@ -8,7 +8,7 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 System accounts should *always* be marked as `locked`. Refer to the [JSON User Record](https://systemd.io/USER_RECORD/) documentation for information on all supported fields.
 
-In AerynOS we only ship user definitions without `privileged` or `signature` fields.
+In aerynOS we only ship user definitions without `privileged` or `signature` fields.
 
 ## Example
 
diff --git a/src/content/docs/Packaging/Recipes/Triggers/overview.mdx b/src/content/docs/Packaging/Recipes/Triggers/overview.mdx
index d44ac7cf..cacf120b 100644
--- a/src/content/docs/Packaging/Recipes/Triggers/overview.mdx
+++ b/src/content/docs/Packaging/Recipes/Triggers/overview.mdx
@@ -6,7 +6,7 @@ license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
-AerynOS supports the use of triggers, or actions, that run at the end of package installations. Given the significantly different architecture of AerynOS, these triggers may not be quite what you are used to in other distributions or package managers.
+aerynOS supports the use of triggers, or actions, that run at the end of package installations. Given the significantly different architecture of aerynOS, these triggers may not be quite what you are used to in other distributions or package managers.
 
 ## Basic mechanism
 
diff --git a/src/content/docs/Packaging/Recipes/build-deps.mdx b/src/content/docs/Packaging/Recipes/build-deps.mdx
index ecd1170c..0d5dbdee 100644
--- a/src/content/docs/Packaging/Recipes/build-deps.mdx
+++ b/src/content/docs/Packaging/Recipes/build-deps.mdx
@@ -8,7 +8,7 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 Every build of a recipe by `boulder` will create an entirely new root, with only the absolute minimum support dependencies in place. In order to build most software, you will need to add to the `builddeps` key in `stone.yml`. Luckily, our tooling supports more than one kind of dependency.
 
-Note that AerynOS packages are also capable of storing **providers** that make the following kinds of dependencies work.
+Note that aerynOS packages are also capable of storing **providers** that make the following kinds of dependencies work.
 
 ## `$name` - standard deps
 
diff --git a/src/content/docs/Packaging/Recipes/index.mdx b/src/content/docs/Packaging/Recipes/index.mdx
index 8013074e..aa4dd4bd 100644
--- a/src/content/docs/Packaging/Recipes/index.mdx
+++ b/src/content/docs/Packaging/Recipes/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: 'Recipes'
 lastUpdated: 2024-09-07T23:44:45Z
-description: "The `stone.yaml` recipe format and `boulder` form the core of all package builds in AerynOS"
+description: "The `stone.yaml` recipe format and `boulder` form the core of all package builds in aerynOS"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Packaging/Recipes/upstreams.mdx b/src/content/docs/Packaging/Recipes/upstreams.mdx
index 9a986f6f..4c114949 100644
--- a/src/content/docs/Packaging/Recipes/upstreams.mdx
+++ b/src/content/docs/Packaging/Recipes/upstreams.mdx
@@ -38,7 +38,7 @@ upstreams
 
 ## Git sources
 
-A git source may be used, when providing either a `tag` or `ref`. In AerynOS we forbid the use of `branch` names in packaging, as they may mutate and break subsequent builds. Ideally a full git ref should be used.
+A git source may be used, when providing either a `tag` or `ref`. In aerynOS we forbid the use of `branch` names in packaging, as they may mutate and break subsequent builds. Ideally a full git ref should be used.
 
 <Aside type="caution">
   Git repositories do work well with `boulder` right now, however some `submodule` based builds are under active testing.
diff --git a/src/content/docs/Packaging/Workflow/basic-workflow.mdx b/src/content/docs/Packaging/Workflow/basic-workflow.mdx
index 1ad86686..d163e6c2 100644
--- a/src/content/docs/Packaging/Workflow/basic-workflow.mdx
+++ b/src/content/docs/Packaging/Workflow/basic-workflow.mdx
@@ -25,9 +25,9 @@ Every time a package is built, `boulder` calls out to `moss` to have it construc
 
 The packages in this buildroot are resolved from one or more moss `stone.index` files, sorted in descending priority, such that the highest priority repository "wins" when package providers are resolved.
 
-The lowest priority repository will typically be the official AerynOS upstream package repository.
+The lowest priority repository will typically be the official aerynOS upstream package repository.
 
-If higher priority repositories are added, packages from these will in turn override the packages available in the official AerynOS upstream package repository.
+If higher priority repositories are added, packages from these will in turn override the packages available in the official aerynOS upstream package repository.
 
 The next section deals with how to create and register a higher priority local moss-format repository, which is colloquially referred to as a "local repo".
 
@@ -81,7 +81,7 @@ This is what `local-x86_64.kdl` should look like after the above commands have b
 local-x86_64 {
   repositories {
     volatile {
-      description "AerynOS volatile stream (CDN)"
+      description "aerynOS volatile stream (CDN)"
       base-uri "https://cdn.aerynos.dev/"
       channel "main"
       version "stream/volatile"
@@ -123,12 +123,12 @@ moss repo list
 
 #### Package resolution order
 
-In the above priority tower, each moss-format package would first get resolved via the `local` repository (priority 100), then from the `volatile` repository (priority 10), and finally from the `unstable` repository (priority 0). The latter of which is the official upstream AerynOS moss-format `.stone` package repository.
+In the above priority tower, each moss-format package would first get resolved via the `local` repository (priority 100), then from the `volatile` repository (priority 10), and finally from the `unstable` repository (priority 0). The latter of which is the official upstream aerynOS moss-format `.stone` package repository.
 
 
 #### Disabling moss-format repositories
 
-Users of AerynOS should generally _not_ have the `volatile` repository be enabled, because this repository is where new `.stone` packages land right after being built. This means the repository can potentially be in an undefined and volatile state when building large build queues (hence the name).
+Users of aerynOS should generally _not_ have the `volatile` repository be enabled, because this repository is where new `.stone` packages land right after being built. This means the repository can potentially be in an undefined and volatile state when building large build queues (hence the name).
 
 Therefore, it can be useful to disable moss-format repositories without deleting their definitions from the local system:
 
@@ -165,7 +165,7 @@ moss repo list
 To actually build a recipe, it is recommended that new packagers start out by building `nano`.
 
 ```bash
-# Go into the root of the AerynOS recipe directory 
+# Go into the root of the aerynOS recipe directory 
 gotoaosrepo
 # change to the directory holding the nano recipe
 chpkg nano
@@ -183,7 +183,7 @@ just mv-local
 just ls-local
 ```
 
-Note that the basic packaging workflow in AerynOS assumes that you are using a local repository.
+Note that the basic packaging workflow in aerynOS assumes that you are using a local repository.
 
 If you are building multiple package recipes, you will need to `just build` and `just mv-local` for each package recipe sequentially.
 
@@ -220,6 +220,6 @@ This will effectively make the new system state "forget" the nano version instal
 
 ## Ending notes
 
-If you have made it this far, congratulations! You should now understand the basic workflow of packaging and managing repositories with AerynOS.
+If you have made it this far, congratulations! You should now understand the basic workflow of packaging and managing repositories with aerynOS.
 
-Tip: execute `just -l` to see a list of supported `just` 'recipes', which are common actions that have been automated by the AerynOS developers.
+Tip: execute `just -l` to see a list of supported `just` 'recipes', which are common actions that have been automated by the aerynOS developers.
diff --git a/src/content/docs/Packaging/Workflow/checking-for-updates.mdx b/src/content/docs/Packaging/Workflow/checking-for-updates.mdx
index 50889a59..ba37738a 100644
--- a/src/content/docs/Packaging/Workflow/checking-for-updates.mdx
+++ b/src/content/docs/Packaging/Workflow/checking-for-updates.mdx
@@ -10,7 +10,7 @@ import { Aside } from '@astrojs/starlight/components';
 
 ## Use `ent` to check for package updates
 
-This guide will walk you through the process using `ent`, a tool built by the AerynOS team to check for package updates. `ent` checks recipes against upstream sources to determine whether updates are available.
+This guide will walk you through the process using `ent`, a tool built by the aerynOS team to check for package updates. `ent` checks recipes against upstream sources to determine whether updates are available.
 
 `ent` is not installed on your system by default. To install `ent` using `moss`, use the following command:
 
diff --git a/src/content/docs/Packaging/Workflow/creating-a-new-recipe.mdx b/src/content/docs/Packaging/Workflow/creating-a-new-recipe.mdx
index 6e9065e4..c86035e4 100644
--- a/src/content/docs/Packaging/Workflow/creating-a-new-recipe.mdx
+++ b/src/content/docs/Packaging/Workflow/creating-a-new-recipe.mdx
@@ -8,9 +8,9 @@ copyright: "Copyright © 2025 aerynOS Developers"
 import { Aside } from '@astrojs/starlight/components';
 
 
-This guide details the process of creating a new package recipe that is not yet present in the [AerynOS repository](https://github.com/AerynOS/recipes). We will use Nano as the running example, but the same steps apply to any new package. 
+This guide details the process of creating a new package recipe that is not yet present in the [aerynOS repository](https://github.com/aerynOS/recipes). We will use Nano as the running example, but the same steps apply to any new package. 
 
-Before creating the package recipe yourself, please double check that there isn't already an outstanding PR for the package you want to include. Please also check if someone has created a new package request issue in the [AerynOS recipes repository](https://github.com/AerynOS/recipes).
+Before creating the package recipe yourself, please double check that there isn't already an outstanding PR for the package you want to include. Please also check if someone has created a new package request issue in the [aerynOS recipes repository](https://github.com/aerynOS/recipes).
 
 ## Prepare your workspace
 
@@ -79,7 +79,7 @@ Using Nano as an example, the generated `stone.yaml` file will look like this:
 
 ```yaml
 #
-# SPDX-FileCopyrightText: © 2025- AerynOS Developers
+# SPDX-FileCopyrightText: © 2025- aerynOS Developers
 #
 # SPDX-License-Identifier: MPL-2.0
 #
@@ -164,7 +164,7 @@ license     :
 
 ### Step 4 - Translate prerequisites into build dependencies
 
-Map each upstream requirement to the package name that exists in AerynOS. Use `pkg-config()` helpers when libraries provide `.pc` files. Toolchain components like `gcc` and `make` are already available inside the build environment, so you do not have to list them.
+Map each upstream requirement to the package name that exists in aerynOS. Use `pkg-config()` helpers when libraries provide `.pc` files. Toolchain components like `gcc` and `make` are already available inside the build environment, so you do not have to list them.
 
 | Upstream prerequisite | Recipe build dependency           |
 |-----------------------|-----------------------------------|
@@ -192,7 +192,7 @@ Combining all the prior steps gives you a complete `stone.yaml`:
 
 ```yaml
 #
-# SPDX-FileCopyrightText: © 2025- AerynOS Developers
+# SPDX-FileCopyrightText: © 2025- aerynOS Developers
 #
 # SPDX-License-Identifier: MPL-2.0
 #
diff --git a/src/content/docs/Packaging/Workflow/index.mdx b/src/content/docs/Packaging/Workflow/index.mdx
index b4881619..ee73c95f 100644
--- a/src/content/docs/Packaging/Workflow/index.mdx
+++ b/src/content/docs/Packaging/Workflow/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Workflow
 lastUpdated: 2024-12-27T17:30:00Z
-description: Understanding how moss and boulder make use of repositories in AerynOS
+description: Understanding how moss and boulder make use of repositories in aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Packaging/Workflow/preparing-for-packaging.mdx b/src/content/docs/Packaging/Workflow/preparing-for-packaging.mdx
index d1e012ce..2c46cbe7 100644
--- a/src/content/docs/Packaging/Workflow/preparing-for-packaging.mdx
+++ b/src/content/docs/Packaging/Workflow/preparing-for-packaging.mdx
@@ -1,7 +1,7 @@
 ---
 title: 'Preparing for packaging'
 lastUpdated: 2026-01-25T12:00:00+00:00
-description: "Preparing for packaging on AerynOS"
+description: "Preparing for packaging on aerynOS"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Packaging/Workflow/prerequisites.mdx b/src/content/docs/Packaging/Workflow/prerequisites.mdx
index 7e6bc115..12146dbb 100644
--- a/src/content/docs/Packaging/Workflow/prerequisites.mdx
+++ b/src/content/docs/Packaging/Workflow/prerequisites.mdx
@@ -6,13 +6,13 @@ license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
-To set up a AerynOS system to be able to build package recipes, a few prerequisites need to be
+To set up a aerynOS system to be able to build package recipes, a few prerequisites need to be
 installed, and a new directory for storing local build artifacts needs to be set up.
 
 
 ## Installing the `build-essential` package
 
-We maintain a `build-essential` metapackage that should contain the basics for getting started with packaging on AerynOS.
+We maintain a `build-essential` metapackage that should contain the basics for getting started with packaging on aerynOS.
 
 ```bash
 sudo moss sync -u
@@ -20,16 +20,16 @@ sudo moss it build-essential
 ```
 
 
-## Activating the AerynOS helper scripts
+## Activating the aerynOS helper scripts
 
-The easiest way to create a local repository is to use the helper script distributed with the AerynOS recipe repository in the `tools/` directory.
+The easiest way to create a local repository is to use the helper script distributed with the aerynOS recipe repository in the `tools/` directory.
 
 Start by cloning the recipes/ git repository:
 
 ```bash
 mkdir -pv Projects/aerynos/
 pushd Projects/aerynos
-git clone https://github.com/AerynOS/recipes
+git clone https://github.com/aerynOS/recipes
 ```
 
 After the recipes/ git repository has been cloned, symlink helpers.bash into `~/.bashrcd.d/`:
diff --git a/src/content/docs/Packaging/Workflow/submitting-a-pr.mdx b/src/content/docs/Packaging/Workflow/submitting-a-pr.mdx
index 747bbee4..f1910d99 100644
--- a/src/content/docs/Packaging/Workflow/submitting-a-pr.mdx
+++ b/src/content/docs/Packaging/Workflow/submitting-a-pr.mdx
@@ -1,20 +1,20 @@
 ---
 title: 'Submitting a PR'
 lastUpdated: 2026-01-11T21:22:00
-description: "How to submit a PR into the AerynOS repository"
+description: "How to submit a PR into the aerynOS repository"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 import { Aside } from "@astrojs/starlight/components";
 
 
-# Submitting packages to AerynOS repository
+# Submitting packages to aerynOS repository
 
-Once you have prepared your package, you can submit it to the AerynOS repository by creating a pull request (PR). There are certain guidelines to follow when submitting a PR:
+Once you have prepared your package, you can submit it to the aerynOS repository by creating a pull request (PR). There are certain guidelines to follow when submitting a PR:
 
 ## Naming Pull Requests
 
-To keep git summaries readable, AerynOS requires the following git summary format
+To keep git summaries readable, aerynOS requires the following git summary format
 
 - `name: Add at v<version>`
 - `name: Update to v<version>`
@@ -49,7 +49,7 @@ The last point about the test plan is particularly important, as it ensures that
 
 #### Example commit message
 
-An example commit message for the AerynOS recipe repository is structured as follows:
+An example commit message for the aerynOS recipe repository is structured as follows:
 
 ```
 brobdingnar: Update to v1.2.3
diff --git a/src/content/docs/Packaging/Workflow/updating-an-existing-recipe.mdx b/src/content/docs/Packaging/Workflow/updating-an-existing-recipe.mdx
index 46469f58..2d12a394 100644
--- a/src/content/docs/Packaging/Workflow/updating-an-existing-recipe.mdx
+++ b/src/content/docs/Packaging/Workflow/updating-an-existing-recipe.mdx
@@ -8,9 +8,9 @@ copyright: "Copyright © 2025 aerynOS Developers"
 import { Aside } from '@astrojs/starlight/components';
 
 
-This guide details the process of updating a package that is already present in the [AerynOS repository](https://github.com/AerynOS/recipes). We will use GNU Nano as the running example, but the same steps apply to any existing package. 
+This guide details the process of updating a package that is already present in the [aerynOS repository](https://github.com/aerynOS/recipes). We will use GNU Nano as the running example, but the same steps apply to any existing package. 
 
-Before updating the package yourself, please double check that there isn't already an outstanding PR for the update you want to make. Please also check if someone has created an update request issue in the [AerynOS recipes repository](https://github.com/AerynOS/recipes).
+Before updating the package yourself, please double check that there isn't already an outstanding PR for the update you want to make. Please also check if someone has created an update request issue in the [aerynOS recipes repository](https://github.com/aerynOS/recipes).
 
 ## Prepare your workspace
 
@@ -65,7 +65,7 @@ This command does the following:
 
 ## Wider updates to a package
 
-If there are further changes required to the `stone.yaml` recipe file, you can either use a text editor (such as Nano itself) or a code editor (such as Zed which is pre-installed on AerynOS) to make changes those changes. Guidance on how to make changes to a stone.yaml file are covered in the [Creating a new package recipe](/packaging/workflow/creating-a-new-recipe/) page.
+If there are further changes required to the `stone.yaml` recipe file, you can either use a text editor (such as Nano itself) or a code editor (such as Zed which is pre-installed on aerynOS) to make changes those changes. Guidance on how to make changes to a stone.yaml file are covered in the [Creating a new package recipe](/packaging/workflow/creating-a-new-recipe/) page.
 
 ## Build and test the package
 
diff --git a/src/content/docs/Packaging/index.mdx b/src/content/docs/Packaging/index.mdx
index 0de94575..3475f96f 100644
--- a/src/content/docs/Packaging/index.mdx
+++ b/src/content/docs/Packaging/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Packaging
 lastUpdated: 2024-09-07T23:42:18Z
-description: Get to grips with packaging for AerynOS
+description: Get to grips with packaging for aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Users/Desktops/cosmic.mdx b/src/content/docs/Users/Desktops/cosmic.mdx
index ee410918..ac4b8b6f 100644
--- a/src/content/docs/Users/Desktops/cosmic.mdx
+++ b/src/content/docs/Users/Desktops/cosmic.mdx
@@ -8,11 +8,11 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 import { Aside } from '@astrojs/starlight/components';
 
-The [COSMIC Desktop](https://system76.com/cosmic) from [System76](https://system76.org) is a highly popular choice with AerynOS users. COSMIC is notable for being written in Rust and using a modern multiprocess architecture, while being Wayland-only. For many, this makes AerynOS and COSMIC an ideal partnership.
+The [COSMIC Desktop](https://system76.com/cosmic) from [System76](https://system76.org) is a highly popular choice with aerynOS users. COSMIC is notable for being written in Rust and using a modern multiprocess architecture, while being Wayland-only. For many, this makes aerynOS and COSMIC an ideal partnership.
 
-### Installing COSMIC on AerynOS
+### Installing COSMIC on aerynOS
 
-AerynOS currently only offers one iso with a GNOME live environment. However, `lichen` is a net based installer that allows users to select their Desktop Environment at install time. As such, you can install AerynOS COSMIC edition directly from the GNOME based AerynOS installer ISO.
+aerynOS currently only offers one iso with a GNOME live environment. However, `lichen` is a net based installer that allows users to select their Desktop Environment at install time. As such, you can install aerynOS COSMIC edition directly from the GNOME based aerynOS installer ISO.
 
 If you are already using GNOME, you are able to install Cosmic Desktop side by side and select which Desktop Environment to use in `GDM` at login. You do this by installing one of three package sets:
 
diff --git a/src/content/docs/Users/Desktops/gnome.mdx b/src/content/docs/Users/Desktops/gnome.mdx
index 022054c2..fab3bd2e 100644
--- a/src/content/docs/Users/Desktops/gnome.mdx
+++ b/src/content/docs/Users/Desktops/gnome.mdx
@@ -6,9 +6,9 @@ license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
-The default desktop environment for the AerynOS live environment and for installs using `lichen` is [GNOME](https://www.gnome.org/). We utilize Wayland display server protocol and do not offer X11 (or any fork of X11).
+The default desktop environment for the aerynOS live environment and for installs using `lichen` is [GNOME](https://www.gnome.org/). We utilize Wayland display server protocol and do not offer X11 (or any fork of X11).
 
-GNOME has been chosen as the default environment due to our familiarity with the GNOME software stack and therefore our ability to maintain it whilst we work on fleshing out the AerynOS tooling and infrastructure.
+GNOME has been chosen as the default environment due to our familiarity with the GNOME software stack and therefore our ability to maintain it whilst we work on fleshing out the aerynOS tooling and infrastructure.
 
 It is recommended to install GNOME using `lichen`, rather than adding to an existing install.
 
diff --git a/src/content/docs/Users/Desktops/plasma.mdx b/src/content/docs/Users/Desktops/plasma.mdx
index aa741598..3df51a8b 100644
--- a/src/content/docs/Users/Desktops/plasma.mdx
+++ b/src/content/docs/Users/Desktops/plasma.mdx
@@ -7,9 +7,9 @@ copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 
-AerynOS now offers [KDE Plasma](https://kde.org/plasma-desktop/) as a Desktop Environment though it is currently considered beta status. You can track the progress of identifying and resolving Plasma related issues on [Github](https://github.com/AerynOS/recipes/issues/952).
+aerynOS now offers [KDE Plasma](https://kde.org/plasma-desktop/) as a Desktop Environment though it is currently considered beta status. You can track the progress of identifying and resolving Plasma related issues on [Github](https://github.com/aerynOS/recipes/issues/952).
 
-### Installing Plasma on an existing AerynOS install
+### Installing Plasma on an existing aerynOS install
 
 If you are already using GNOME, you are able to install KDE Plasma side by side and select which Desktop Environment to use in `GDM` at login. You do this by installing one of three package sets:
 
diff --git a/src/content/docs/Users/Desktops/window-managers/sway.mdx b/src/content/docs/Users/Desktops/window-managers/sway.mdx
index e7492f67..5ea6b8aa 100644
--- a/src/content/docs/Users/Desktops/window-managers/sway.mdx
+++ b/src/content/docs/Users/Desktops/window-managers/sway.mdx
@@ -8,9 +8,9 @@ copyright: "Copyright © 2025 aerynOS Developers"
 
 [Sway](https://swaywm.org/) is a dynamic tiling window manager designed as a drop-in replacement for i3, but built for Wayland. It offers a lightweight workflow that is well suited to machines where users prefer keyboard driven navigation over graphical shell integrations.
 
-### Installing Sway on AerynOS
+### Installing Sway on aerynOS
 
-Sway is currently packaged as a single minimal session that you can add to any existing AerynOS installation. Install the package set with `moss`:
+Sway is currently packaged as a single minimal session that you can add to any existing aerynOS installation. Install the package set with `moss`:
 
 ```bash
 sudo moss install pkgset-aeryn-sway-minimal
diff --git a/src/content/docs/Users/Getting Started/booting-the-live-environment.mdx b/src/content/docs/Users/Getting Started/booting-the-live-environment.mdx
index 57c1d6b0..4b63ea43 100644
--- a/src/content/docs/Users/Getting Started/booting-the-live-environment.mdx	
+++ b/src/content/docs/Users/Getting Started/booting-the-live-environment.mdx	
@@ -1,7 +1,7 @@
 ---
 title: 'Booting the Live Environment'
 lastUpdated: 2024-09-10T23:57:02+08:00
-description: "Booting into the AerynOS Live Environment"
+description: "Booting into the aerynOS Live Environment"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -16,16 +16,16 @@ Currently NVIDIA Drivers are not implemented by the live environment and will fa
 
 1. Insert the bootable USB drive into your system and boot from the USB drive.
 2. Adjust or override your BIOS settings to boot from the USB drive.
-3. You should see the AerynOS boot process, and you will be presented with the live environment.
-4. **If utilizing Ventoy** select the AerynOS ISO file to boot from.
+3. You should see the aerynOS boot process, and you will be presented with the live environment.
+4. **If utilizing Ventoy** select the aerynOS ISO file to boot from.
 
 ## Testing the Live Environment
 
 <Aside type="tip">
-For a representative experience, you will need to install AerynOS. The live environment will run slower than an installed system due to the limitations of running from a USB drive.
+For a representative experience, you will need to install aerynOS. The live environment will run slower than an installed system due to the limitations of running from a USB drive.
 </Aside>
 
-Once you have booted into the live environment, you can test AerynOS without installing it on your system.
+Once you have booted into the live environment, you can test aerynOS without installing it on your system.
 
 - Explore the desktop environment.
 - Test the pre-installed applications.
diff --git a/src/content/docs/Users/Getting Started/creating-the-live-environment.mdx b/src/content/docs/Users/Getting Started/creating-the-live-environment.mdx
index 66f1f2de..4151ca50 100644
--- a/src/content/docs/Users/Getting Started/creating-the-live-environment.mdx	
+++ b/src/content/docs/Users/Getting Started/creating-the-live-environment.mdx	
@@ -1,7 +1,7 @@
 ---
 title: Creating the Live Environment
 lastUpdated: 2024-09-10T23:43:21+08:00
-description: Creating a live environment to boot into and run the AerynOS installer
+description: Creating a live environment to boot into and run the aerynOS installer
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -12,25 +12,25 @@ import { Aside } from '@astrojs/starlight/components';
 
 ## Prerequisites
 
-- Instructions for [Downloading AerynOS](/users/getting-started/downloading/).
+- Instructions for [Downloading aerynOS](/users/getting-started/downloading/).
 - You will need a spare USB drive that you don't mind wiping.
 
 {/*
 ## Option 1: Using Ventoy on a USB drive
 
-Ventoy is an open source tool to create bootable USB drives that can boot multiple operating systems by placing their respective ISO files on the USB drive. This flexibility is particularly useful as it allows users to have a single USB drive for installation of multiple operating systems. Support for AerynOS was added in version [1.1.10](https://www.ventoy.net/en/doc_news.html).
+Ventoy is an open source tool to create bootable USB drives that can boot multiple operating systems by placing their respective ISO files on the USB drive. This flexibility is particularly useful as it allows users to have a single USB drive for installation of multiple operating systems. Support for aerynOS was added in version [1.1.10](https://www.ventoy.net/en/doc_news.html).
 
 Ventoy has several options for creating a bootable USB drive. These instructions with vary depending on your current OS. You can find the instructions for creating a bootable Ventoy USB drive on the [Ventoy website](https://www.ventoy.net/en/doc_start.html).
 
 1. Follow the instructions for creating a bootable Ventoy USB drive.
-2. Copy the latest AerynOS ISO to the root directory of the "Ventoy" drive
+2. Copy the latest aerynOS ISO to the root directory of the "Ventoy" drive
 */}
 
 ## Option 1: Preparing an install medium using Etcher
 
 1. Download the latest version of [Balena Etcher](https://etcher.balena.io/) for your OS.
 2. Launch the application
-3. Select the latest AerynOS ISO you have already downloaded
+3. Select the latest aerynOS ISO you have already downloaded
 4. Select the inserted USB stick
 5. Flash!
 6. Ensure the USB drive is properly ejected after flashing the ISO to avoid data corruption.
diff --git a/src/content/docs/Users/Getting Started/downloading.mdx b/src/content/docs/Users/Getting Started/downloading.mdx
index aa80ab82..8d7f644c 100644
--- a/src/content/docs/Users/Getting Started/downloading.mdx	
+++ b/src/content/docs/Users/Getting Started/downloading.mdx	
@@ -1,7 +1,7 @@
 ---
-title: Downloading AerynOS
+title: Downloading aerynOS
 lastUpdated: 2025-01-13T10:49:00+07:00
-description: Downloading the AerynOS ISO file and verifying the checksums
+description: Downloading the aerynOS ISO file and verifying the checksums
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -10,7 +10,7 @@ import { Aside } from '@astrojs/starlight/components';
 
 ## Downloading the ISO
 
-1. Visit the [AerynOS download page](https://aerynos.com/download/).
+1. Visit the [aerynOS download page](https://aerynos.com/download/).
 2. Use the direct download or bittorrent option to get the latest release.
 3. Download the checksum file
 
@@ -19,7 +19,7 @@ import { Aside } from '@astrojs/starlight/components';
 Before creating a bootable USB drive, it's important to verify the checksums to ensure the integrity of the downloaded ISO file.
 
 <Aside type="tip">
-    AerynOS utilizes a GNOME based live environment for installation. Our installer `lichen` is a netinstaller that can be used to install GNOME, KDE Plasma, Cosmic or a terminal-only environment based on your requirements.
+    aerynOS utilizes a GNOME based live environment for installation. Our installer `lichen` is a netinstaller that can be used to install GNOME, KDE Plasma, Cosmic or a terminal-only environment based on your requirements.
 </Aside>
 
 ### Linux
@@ -38,7 +38,7 @@ sha256sum -c <checksum_file>
 You should see a message indicating that the checksums match if the ISO file is valid.
 
 ```bash
-AerynOS-2026.01-GNOME-live-x86_64.iso: OK
+aerynOS-2026.01-GNOME-live-x86_64.iso: OK
 ```
 
 If the checksums do not match, download the ISO file again and repeat the verification process.
diff --git a/src/content/docs/Users/Getting Started/index.mdx b/src/content/docs/Users/Getting Started/index.mdx
index 868b52bb..c9156422 100644
--- a/src/content/docs/Users/Getting Started/index.mdx	
+++ b/src/content/docs/Users/Getting Started/index.mdx	
@@ -1,7 +1,7 @@
 ---
 title: Getting Started
 lastUpdated: 2024-09-10T23:25:15+08:00
-description: Getting started with AerynOS
+description: Getting started with aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Users/Getting Started/installing-aerynos.mdx b/src/content/docs/Users/Getting Started/installing-aerynos.mdx
index 6ec26dfe..b71306e8 100644
--- a/src/content/docs/Users/Getting Started/installing-aerynos.mdx	
+++ b/src/content/docs/Users/Getting Started/installing-aerynos.mdx	
@@ -1,7 +1,7 @@
 ---
-title: 'Installing AerynOS'
+title: 'Installing aerynOS'
 lastUpdated: 2024-09-10T23:57:02+08:00
-description: "Installing AerynOS on your system"
+description: "Installing aerynOS on your system"
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -13,7 +13,7 @@ import { Aside } from '@astrojs/starlight/components';
 For the easiest experience, we recommend using gparted which is included in the live environment.
 
 1. Load up gparted from the live environment.
-2. Create a gpt partition table on the drive you want to install AerynOS on.
+2. Create a gpt partition table on the drive you want to install aerynOS on.
 3. Create a >=256mb FAT32 partition for ESP with the boot and esp flags
 4. Create a 4gb FAT32 partition for XBOOTLDR with the bls_boot flag
 5. Utilize the rest of the space for a xfs root partition
@@ -22,9 +22,9 @@ Once you have finished, your partition layout should look like this:
 
 ![gparted](src/images/getting-started/gparted.png)
 
-## Install AerynOS
+## Install aerynOS
 
-From the app menu, select the "Install AerynOS" option. This is a shortcut to opening a terminal and running the following command:
+From the app menu, select the "Install aerynOS" option. This is a shortcut to opening a terminal and running the following command:
 
 ```bash
 sudo lichen
@@ -42,4 +42,4 @@ Follow the instructions on the screen to complete your installation. You will be
 8. Filesystem type for root partition
 9. Desktop environment
 
-If you follow all the steps above, `lichen` will download the packages from our repository and install the latest version of AerynOS onto your system. Once completed, you can reboot your system and enjoy your new AerynOS installation!
+If you follow all the steps above, `lichen` will download the packages from our repository and install the latest version of aerynOS onto your system. Once completed, you can reboot your system and enjoy your new aerynOS installation!
diff --git a/src/content/docs/Users/Getting Started/requirements.mdx b/src/content/docs/Users/Getting Started/requirements.mdx
index 65a45f2b..bf91058d 100644
--- a/src/content/docs/Users/Getting Started/requirements.mdx	
+++ b/src/content/docs/Users/Getting Started/requirements.mdx	
@@ -1,7 +1,7 @@
 ---
 title: Requirements
 lastUpdated: 2024-09-10T23:00:44+08:00
-description: Requirements for AerynOS
+description: Requirements for aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
@@ -18,12 +18,12 @@ import { Aside } from '@astrojs/starlight/components';
 
 ## Installer Requirements
 
-To successfully create a bootable USB drive for installing AerynOS, the following requirements must be met:
+To successfully create a bootable USB drive for installing aerynOS, the following requirements must be met:
 
 - **Network:** An active internet connection is required for installation
 - **USB Flash Drive:** Ensure you have a USB flash drive with at least 4GB of free space.
 
-- **Image Flashing Software:** Utilize one of the following recommended tools to flash the AerynOS ISO image onto the USB drive:
+- **Image Flashing Software:** Utilize one of the following recommended tools to flash the aerynOS ISO image onto the USB drive:
   - **Ventoy:** A versatile tool that allows you to create a multi-boot USB drive. [Please note this currently doesn't work](https://github.com/ventoy/Ventoy/issues/3550)
   - **Balena Etcher:** A simple and user-friendly tool for creating bootable USB drives.
   - **dd:** A Linux command-line utility available on most Linux distributions for creating bootable USB drives.
diff --git a/src/content/docs/Users/System Management/configuration-locations.mdx b/src/content/docs/Users/System Management/configuration-locations.mdx
index 445be58b..5262d1e3 100644
--- a/src/content/docs/Users/System Management/configuration-locations.mdx	
+++ b/src/content/docs/Users/System Management/configuration-locations.mdx	
@@ -6,7 +6,7 @@ license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
-AerynOS ships configuration in a stateless layout. Packages deliver defaults in `/usr/share/defaults`, while administrator and user changes live elsewhere so updates can proceed without overwriting your work.
+aerynOS ships configuration in a stateless layout. Packages deliver defaults in `/usr/share/defaults`, while administrator and user changes live elsewhere so updates can proceed without overwriting your work.
 
 ## System defaults
 
diff --git a/src/content/docs/Users/System Management/index.mdx b/src/content/docs/Users/System Management/index.mdx
index a3c812cb..88077294 100644
--- a/src/content/docs/Users/System Management/index.mdx	
+++ b/src/content/docs/Users/System Management/index.mdx	
@@ -1,7 +1,7 @@
 ---
 title: System Management
 lastUpdated: 2025-09-28T16:14:34Z
-description: Keep an AerynOS system healthy with stateless configuration guidance and moss lifecycle tasks.
+description: Keep an aerynOS system healthy with stateless configuration guidance and moss lifecycle tasks.
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/Users/index.mdx b/src/content/docs/Users/index.mdx
index 80b11140..2ce516cb 100644
--- a/src/content/docs/Users/index.mdx
+++ b/src/content/docs/Users/index.mdx
@@ -1,7 +1,7 @@
 ---
 title: Users
 lastUpdated: 2024-09-10T00:04:48Z
-description: Documentation for daily users of AerynOS
+description: Documentation for daily users of aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
diff --git a/src/content/docs/AerynOS/contribute.mdx b/src/content/docs/aerynOS/contribute.mdx
similarity index 73%
rename from src/content/docs/AerynOS/contribute.mdx
rename to src/content/docs/aerynOS/contribute.mdx
index 770ade5f..6490debf 100644
--- a/src/content/docs/AerynOS/contribute.mdx
+++ b/src/content/docs/aerynOS/contribute.mdx
@@ -1,16 +1,16 @@
 ---
 title: Contributing
 lastUpdated: 2025-11-04T16:20:00Z
-description: Contributing to AerynOS
+description: Contributing to aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 import { Aside } from "@astrojs/starlight/components";
 
-## Financial contributions to AerynOS
+## Financial contributions to aerynOS
 
-AerynOS is an independent effort run by a handful of volunteers. The team is currently targeting an income of 500€ per month to cover:
+aerynOS is an independent effort run by a handful of volunteers. The team is currently targeting an income of 500€ per month to cover:
 
 1. Infrastructure and project costs
 2. Repayment to project stakeholders for initial project seed funding
@@ -20,10 +20,10 @@ We currently accept donations via Stripe and Ko-Fi. For the latest information o
 
 ## Contributing to our codebases
 
-AerynOS utilizes GitHub to manage code changes, including updates to our websites. Each repository will have its own Readme that will include instructions on how to make updates to it. They can be found [here](https://github.com/orgs/AerynOS/repositories). To specifically make contributions to our websites, you can visit the following repositories:
+aerynOS utilizes GitHub to manage code changes, including updates to our websites. Each repository will have its own Readme that will include instructions on how to make updates to it. They can be found [here](https://github.com/orgs/aerynOS/repositories). To specifically make contributions to our websites, you can visit the following repositories:
 
-- AerynOS.com site [repo](https://github.com/AerynOS/dotdev)
-- AerynOS.dev site [repo](https://github.com/AerynOS/dotcom)
+- aerynOS.com site [repo](https://github.com/aerynOS/dotdev)
+- aerynOS.dev site [repo](https://github.com/aerynOS/dotcom)
 
 ## Other contributions
 
diff --git a/src/content/docs/AerynOS/index.mdx b/src/content/docs/aerynOS/index.mdx
similarity index 87%
rename from src/content/docs/AerynOS/index.mdx
rename to src/content/docs/aerynOS/index.mdx
index 9d088930..be5d520b 100644
--- a/src/content/docs/AerynOS/index.mdx
+++ b/src/content/docs/aerynOS/index.mdx
@@ -1,5 +1,5 @@
 ---
-title: AerynOS
+title: aerynOS
 lastUpdated: 2025-03-28T05:28:00Z
 description: Documentation about the project and its technologies
 license: "CC-BY-SA-4.0"
@@ -7,6 +7,6 @@ copyright: "Copyright © 2025 aerynOS Developers"
 ---
 import DirectoryList from '@components/DirectoryList.astro';
 
-AerynOS is an independent Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment. In this section of the documentation, you can find high level information about the project itself and what sets it apart from other distributions.
+aerynOS is an independent Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment. In this section of the documentation, you can find high level information about the project itself and what sets it apart from other distributions.
 
 <DirectoryList/>
diff --git a/src/content/docs/AerynOS/overview.mdx b/src/content/docs/aerynOS/overview.mdx
similarity index 82%
rename from src/content/docs/AerynOS/overview.mdx
rename to src/content/docs/aerynOS/overview.mdx
index 71157305..b56bb2ac 100644
--- a/src/content/docs/AerynOS/overview.mdx
+++ b/src/content/docs/aerynOS/overview.mdx
@@ -1,21 +1,21 @@
 ---
 title: Overview
 lastUpdated: 2025-03-28T05:28:00Z
-description: Overview of the AerynOS project and its technologies
+description: Overview of the aerynOS project and its technologies
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 import { Aside } from '@astrojs/starlight/components';
 
-AerynOS is a Linux-based operating system designed to eliminate years of technical baggage. It is an engineering led effort in that the distribution is produced entirely by the tooling we have developed. Every new feature, technology, or enabling is carefully considered, drawing on our own experiences and by studying the impact in similar decision spaces in other projects.
+aerynOS is a Linux-based operating system designed to eliminate years of technical baggage. It is an engineering led effort in that the distribution is produced entirely by the tooling we have developed. Every new feature, technology, or enabling is carefully considered, drawing on our own experiences and by studying the impact in similar decision spaces in other projects.
 
 Despite being heavily engineering led, we are not averse to design. We aim to provide the best in class user experience atop a solid, innovative foundation, whilst ensuring we have the scope and scalability to meet the needs of the future.
 
 In essence, we're producing a distribution based on sound technical principles, in order to deliver a "daily driver" that truly looks after itself. Its aim is to get out of the way when you need it to, and provide the tools you need when you need them.
 
-If anything, AerynOS is "operating-system-as-infrastructure", providing a solid foundation for your daily computing needs. We're not just a distribution, we're a platform for the future.
+If anything, aerynOS is "operating-system-as-infrastructure", providing a solid foundation for your daily computing needs. We're not just a distribution, we're a platform for the future.
 
 <Aside type="caution">
-    Remember, AerynOS is still in development. Despite our goals, we must be clear that we've deemed ourselves to be alpha quality software.
+    Remember, aerynOS is still in development. Despite our goals, we must be clear that we've deemed ourselves to be alpha quality software.
 </Aside>
diff --git a/src/content/docs/AerynOS/philosophy.mdx b/src/content/docs/aerynOS/philosophy.mdx
similarity index 89%
rename from src/content/docs/AerynOS/philosophy.mdx
rename to src/content/docs/aerynOS/philosophy.mdx
index 74808959..7aa74d00 100644
--- a/src/content/docs/AerynOS/philosophy.mdx
+++ b/src/content/docs/aerynOS/philosophy.mdx
@@ -1,18 +1,18 @@
 ---
 title: Philosophy
 lastUpdated: 2026-08-09T16:00:00Z
-description: The philosophy of AerynOS
+description: The philosophy of aerynOS
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 ---
 
 import { Aside } from '@astrojs/starlight/components';
 
-<Aside type="tip" title= "AerynOS Mission Statement">
+<Aside type="tip" title= "aerynOS Mission Statement">
     Develop modern, ergonomic tooling and processes that in turn enable efficient delivery of an atomic, reliable, predictable, and performant Operating System, which is a joy to use and maintain for its developers, packagers, and users alike.
 </Aside>
 
-AerynOS is the collective output of brand new tooling and associated processes, engineered from the ground up to deliver a Linux distribution that focuses on reliability, up front predictability, proven performance and efficiency.
+aerynOS is the collective output of brand new tooling and associated processes, engineered from the ground up to deliver a Linux distribution that focuses on reliability, up front predictability, proven performance and efficiency.
 
 Our ground up approach has enabled us to provide atomic updates without requiring reboots or having to utilize containers for package delivery. Part of our design philosophy is to deliver "just enough" flexibility and customizability to end users, without becoming a meta-distribution, and without compromising on predictability or reliability.
 
@@ -20,13 +20,13 @@ Our ground up approach has enabled us to provide atomic updates without requirin
 
 Most Linux distributions follow the [Filesystem Hierarchy Standard](https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf) which sets the structure for all files and directories on a Unix-like system. In traditional FHS based Linux distributions, package files can be installed to multiple directories, these can be directories or files that users may interact with (such as config files).
 
-In AerynOS, packages are forbidden from containing any files outside of the `/usr` directory. The `/usr` directory exclusively belongs to the system with the user not intended to make any changes in this directory whatsoever. Files written under the `/usr` directory by a user will get removed (or reverted) the next time the system is updated.
+In aerynOS, packages are forbidden from containing any files outside of the `/usr` directory. The `/usr` directory exclusively belongs to the system with the user not intended to make any changes in this directory whatsoever. Files written under the `/usr` directory by a user will get removed (or reverted) the next time the system is updated.
 
-In order to enable this, some packages and/or configurations are altered in AerynOS to ensure they can operate in the absence of a user provided configuration. This forces AerynOS to have sane defaults baked in at all levels, and eliminates 3-way merge conflicts on package updates. There are no conflicts, because everything in `/etc` and `/var` directories belongs to the user. In this way, if a user deletes their configuration files located in the `/etc` directory, this will revert the system back to factory defaults.
+In order to enable this, some packages and/or configurations are altered in aerynOS to ensure they can operate in the absence of a user provided configuration. This forces aerynOS to have sane defaults baked in at all levels, and eliminates 3-way merge conflicts on package updates. There are no conflicts, because everything in `/etc` and `/var` directories belongs to the user. In this way, if a user deletes their configuration files located in the `/etc` directory, this will revert the system back to factory defaults.
 
-The stateless Linux concept was originally proposed by Red Hat in 2004 and the idea has continued to evolve from there. AerynOS leans towards the approach developed by Clear Linux, and we are refining it further.
+The stateless Linux concept was originally proposed by Red Hat in 2004 and the idea has continued to evolve from there. aerynOS leans towards the approach developed by Clear Linux, and we are refining it further.
 
-However, it might still be necessary to create or update system configuration files in lockstep with package installation. In AerynOS, the only way for files to get created or updated under `/etc` or `/var` during package installation is via package "triggers". Triggers are small scripts that are run at the tail end of package installation. AerynOS supports two forms of package triggers: Transaction scope triggers and System scope triggers.
+However, it might still be necessary to create or update system configuration files in lockstep with package installation. In aerynOS, the only way for files to get created or updated under `/etc` or `/var` during package installation is via package "triggers". Triggers are small scripts that are run at the tail end of package installation. aerynOS supports two forms of package triggers: Transaction scope triggers and System scope triggers.
 
 ### Transaction Triggers
 
@@ -40,11 +40,11 @@ System triggers do not run in an isolated container, but instead are run in the
 
 An atomic update is a series of changes to a system that are treated as a single, indivisible operation. If any part of this update fails, then the entire update is canceled with all prior parts of the incomplete update being rolled back. This means that either an update completes fully as intended, or the system is left in the state it was in before the update was attempted. This is important because partial updates often cause significant issues such as bricked installs.
 
-AerynOS' approach to atomic updates is fairly different to the approach taken by other Linux distributions, which mostly use an A/B switch model using specific read-only filesystems to swap the whole system upon reboot. Atomic updates in AerynOS are managed by its package manager `moss` (which we also refer to as a "system state manager"). As such, AerynOS is not tied to using read-only filesystems and this allows for the use of XFS, ext4 and F2FS. In the future, additional filesystems will be tested and considered.
+aerynOS' approach to atomic updates is fairly different to the approach taken by other Linux distributions, which mostly use an A/B switch model using specific read-only filesystems to swap the whole system upon reboot. Atomic updates in aerynOS are managed by its package manager `moss` (which we also refer to as a "system state manager"). As such, aerynOS is not tied to using read-only filesystems and this allows for the use of XFS, ext4 and F2FS. In the future, additional filesystems will be tested and considered.
 
-As mentioned above, AerynOS utilizes a stateless design where packages can only be installed to the `/usr` directory. The knowledge that packages can only be installed to this directory allows AerynOS to innovate in its approach to atomic updates.
+As mentioned above, aerynOS utilizes a stateless design where packages can only be installed to the `/usr` directory. The knowledge that packages can only be installed to this directory allows aerynOS to innovate in its approach to atomic updates.
 
-AerynOS packages are packaged up as bespoke `.stone` moss-format files. Hence, AerynOS does not use or rely on e.g. Debian `.deb` format package files or Fedora/RHEL `.rpm` format package files. These `.stone` files contain a deduplicated set of hashed files compressed using zstd. 
+aerynOS packages are packaged up as bespoke `.stone` moss-format files. Hence, aerynOS does not use or rely on e.g. Debian `.deb` format package files or Fedora/RHEL `.rpm` format package files. These `.stone` files contain a deduplicated set of hashed files compressed using zstd. 
 
 ### Content Addressable Store (CAS)
 
@@ -62,21 +62,21 @@ Our BLS (Bootloader Specification) compliant boot management tool, `blsforme` ad
 
 ## Self healing
 
-As part of our boot management solution, every moss transaction ID is encoded into the kernel command line and is picked up during early boot into our initramfs, before `/sysroot` is pivoted to. Every kernel is correctly synchronized with the right rootfs based on the moss transaction it was associated to. Given that every transaction creates a new bootloader entry, AerynOS prunes all but the last 5 transactions from the bootloader list to keep it manageable.
+As part of our boot management solution, every moss transaction ID is encoded into the kernel command line and is picked up during early boot into our initramfs, before `/sysroot` is pivoted to. Every kernel is correctly synchronized with the right rootfs based on the moss transaction it was associated to. Given that every transaction creates a new bootloader entry, aerynOS prunes all but the last 5 transactions from the bootloader list to keep it manageable.
 
 ### What are the implications of this?
 
 On a Gnome based system, if you were to delete `gtk3`, `GDM`, and `gnome-shell` you would not be able to log back into the gnome session (as you've just deleted some really important part of the gnome session!). In this case, on boot you would be greeted by a Linux console login prompt, which would only let you log into your user's command line shell, which is less than ideal.
 
-In AerynOS, instead of this scenario, you can enter the bootloader (by mashing your spacebar) on reboot, and in the bootloader. Select the second to last entry and this will automatically switch to the `/usr` filesystem transaction where `gtk3`, `GDM` and `gnome-shell` had not yet been deleted. On activating this entry with the Enter key, you will boot back into a working GDM for a graphical user experience.
+In aerynOS, instead of this scenario, you can enter the bootloader (by mashing your spacebar) on reboot, and in the bootloader. Select the second to last entry and this will automatically switch to the `/usr` filesystem transaction where `gtk3`, `GDM` and `gnome-shell` had not yet been deleted. On activating this entry with the Enter key, you will boot back into a working GDM for a graphical user experience.
 
-Taking this a step further, if you were to remove `glibc`, given how integral it is to the functioning of AerynOS and how it specifically includes the `renameat2` function used by `moss` to complete transactions, the system would be left in a state where the atomic update did not complete and the whole system would be broken. In a traditional Linux distribution, this will be very difficult, or impossible to resolve without resorting to a fresh reinstall.
+Taking this a step further, if you were to remove `glibc`, given how integral it is to the functioning of aerynOS and how it specifically includes the `renameat2` function used by `moss` to complete transactions, the system would be left in a state where the atomic update did not complete and the whole system would be broken. In a traditional Linux distribution, this will be very difficult, or impossible to resolve without resorting to a fresh reinstall.
 
-In AerynOS, however, upon trying to boot into this last transaction, the system will discover that there is an issue with the transaction and will atomically roll back to the prior bootloader entry with the associated correct `/usr` directory that works. This rollback process only takes around a second (or a couple of seconds, depending on your hardware) and you will automatically be dropped back into a live working AerynOS system.
+In aerynOS, however, upon trying to boot into this last transaction, the system will discover that there is an issue with the transaction and will atomically roll back to the prior bootloader entry with the associated correct `/usr` directory that works. This rollback process only takes around a second (or a couple of seconds, depending on your hardware) and you will automatically be dropped back into a live working aerynOS system.
 
 ### Could this happen?
 
-Whilst it is unlikely that a user would ever knowingly delete these very important packages (though it could happen). The more likely scenario on traditional Linux distributions is that there is a partial update that may have deleted very important aspects for a functioning system with the newer versions not having been yet installed before the update stopped. By the design features mentioned above, this is impossible on AerynOS.
+Whilst it is unlikely that a user would ever knowingly delete these very important packages (though it could happen). The more likely scenario on traditional Linux distributions is that there is a partial update that may have deleted very important aspects for a functioning system with the newer versions not having been yet installed before the update stopped. By the design features mentioned above, this is impossible on aerynOS.
 
 ## Repository Management 
 
@@ -89,9 +89,9 @@ As a rolling release distribution, packages are landed in our volatile stream fi
 
 ## System model
 
-By default, AerynOS operates as a standard "imperative" Linux Distribution. We have implemented the concept of an (optional!) install-time declarative system-model where a user can define (within the `/etc/moss/system-model.kdl` file), which exact packages and from which repository they want these packages.
+By default, aerynOS operates as a standard "imperative" Linux Distribution. We have implemented the concept of an (optional!) install-time declarative system-model where a user can define (within the `/etc/moss/system-model.kdl` file), which exact packages and from which repository they want these packages.
 
-`moss` will then keep the system in sync with this system-model as updates arrive. Combining the use of addressable tags, our system-model approach goes further and enables users to define a specific tag on our unstable repository, becoming more akin to a fixed point release model. The user can change the tag they wish to fix to, or revert back to the rolling release model at any time. This flexibility enables users to replicate their system-model across different installs and share system-models with the AerynOS team for troubleshooting purposes.
+`moss` will then keep the system in sync with this system-model as updates arrive. Combining the use of addressable tags, our system-model approach goes further and enables users to define a specific tag on our unstable repository, becoming more akin to a fixed point release model. The user can change the tag they wish to fix to, or revert back to the rolling release model at any time. This flexibility enables users to replicate their system-model across different installs and share system-models with the aerynOS team for troubleshooting purposes.
 
 ## Package Management 
 
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index e8dfdee3..817c898c 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -1,13 +1,13 @@
 ---
 title: Documentation
-description: Documentation for all projects under the AerynOS umbrella.
+description: Documentation for all projects under the aerynOS umbrella.
 license: "CC-BY-SA-4.0"
 copyright: "Copyright © 2025 aerynOS Developers"
 template: splash
 editUrl: false
 hero:
-  title: AerynOS Docs
-  tagline: Documentation for all projects under the AerynOS umbrella.
+  title: aerynOS Docs
+  tagline: Documentation for all projects under the aerynOS umbrella.
   image:
     file: ../../images/logo.svg
   actions:
@@ -23,11 +23,11 @@ hero:
       icon: zulip
       variant: primary
     - text: Forums
-      link: https://github.com/orgs/AerynOS/discussions
+      link: https://github.com/orgs/aerynOS/discussions
       icon: github
       variant: primary
     - text: Mastodon
-      link: https://hachyderm.io/@AerynOS
+      link: https://hachyderm.io/@aerynOS
       icon: mastodon
       variant: primary
     - text: Bluesky
diff --git a/src/images/icon.svg b/src/images/icon.svg
index 5a317807..f8f70c1a 100644
--- a/src/images/icon.svg
+++ b/src/images/icon.svg
@@ -8,8 +8,8 @@
    version="1.1"
    id="svg1"
    inkscape:version="1.4.3 (0d15f75042, 2025-12-25)"
-   sodipodi:docname="AerynOS.svg"
-   inkscape:export-filename="AerynOS (icon).png"
+   sodipodi:docname="aerynOS.svg"
+   inkscape:export-filename="aerynOS (icon).png"
    inkscape:export-xdpi="65.360001"
    inkscape:export-ydpi="65.360001"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
diff --git a/src/images/logo-light-mode.svg b/src/images/logo-light-mode.svg
index 03c77684..2a337490 100644
--- a/src/images/logo-light-mode.svg
+++ b/src/images/logo-light-mode.svg
@@ -8,7 +8,7 @@
    version="1.1"
    id="svg1"
    inkscape:version="1.4.3 (0d15f75042, 2025-12-25)"
-   sodipodi:docname="AerynOS darker rust.svg"
+   sodipodi:docname="aerynOS darker rust.svg"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
    xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
    xmlns="http://www.w3.org/2000/svg"
diff --git a/src/images/logo.svg b/src/images/logo.svg
index 5a317807..f8f70c1a 100644
--- a/src/images/logo.svg
+++ b/src/images/logo.svg
@@ -8,8 +8,8 @@
    version="1.1"
    id="svg1"
    inkscape:version="1.4.3 (0d15f75042, 2025-12-25)"
-   sodipodi:docname="AerynOS.svg"
-   inkscape:export-filename="AerynOS (icon).png"
+   sodipodi:docname="aerynOS.svg"
+   inkscape:export-filename="aerynOS (icon).png"
    inkscape:export-xdpi="65.360001"
    inkscape:export-ydpi="65.360001"
    xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
diff --git a/src/utils/git.ts b/src/utils/git.ts
index 908295e3..b99bc487 100644
--- a/src/utils/git.ts
+++ b/src/utils/git.ts
@@ -10,13 +10,13 @@ export interface CommitInfo {
   committer: CommitterInfo;
 }
 
-export const REPO = "AerynOS/dotdev";
+export const REPO = "aerynOS/dotdev";
 
 const cache = new Map<string, CommitterInfo>();
 
 const baseHeaders = {
   Accept: "application/vnd.github+json",
-  "User-Agent": "AerynOS/docs (https://aerynos.dev)",
+  "User-Agent": "aerynOS/docs (https://aerynos.dev)",
 };
 
 const GITHUB_OPTIONS: RequestInit = process.env.GITHUB_TOKEN