diff --git a/src/content/docs/about.mdx b/src/content/docs/about.mdx
index 9805111d..e1a1e41e 100644
--- a/src/content/docs/about.mdx
+++ b/src/content/docs/about.mdx
@@ -1,16 +1,13 @@
 ---
 title: About
-description: About AerynOS
+description: About aerynOS
 ---
 import { CardGrid } from '@astrojs/starlight/components';
 import Asciinema from "@/components/ui/Asciinema.astro";
 import Card from "@/components/ui/Card.astro";
 
 <Card>
-  AerynOS is a modern Linux distribution using atomic updates, cutting-edge
-  tooling and rock-solid reliability. Built by industry veterans with decades
-  of experience, it represents the next evolution in Linux distributions -
-  delivering a safe and efficient system 🐍
+  aerynOS is a modern Linux distribution using atomic updates, cutting-edge tooling and rock-solid reliability. Built by industry veterans with decades of experience, it represents the next evolution in Linux distributions - delivering a safe and efficient system 🐍
 </Card>
 
 Our fully atomic system leverages the [LLVM](https://llvm.org/) toolchain and GNU libstdc++ by default, delivering superior diagnostics and package diversity. We're not afraid to challenge convention - thoughtfully replacing traditional components with modern alternatives that prioritize safety and reliability.
@@ -23,9 +20,9 @@ This is the future of Linux distribution design, built on a foundation of experi
 
 
 ## Daily Driver
-Want a rolling release distribution that just works? We're building AerynOS to be the system that gets out of your way and lets you focus on what matters. Our atomic updates mean you can keep rolling forward without the usual headaches - no manual interventions, no update anxiety. When we say rolling release, we mean it should be as simple as running an update and getting back to work. Join us on this journey as we continuously improve and refine the experience.
+Want a rolling release distribution that just works? We're building aerynOS to be the system that gets out of your way and lets you focus on what matters. Our atomic updates mean you can keep rolling forward without the usual headaches - no manual interventions, no update anxiety. When we say rolling release, we mean it should be as simple as running an update and getting back to work. Join us on this journey as we continuously improve and refine the experience.
 
-![aerynos_alpha](@/images/editions/AerynOS_KDE_May26.png)
+![aerynos_alpha](@/images/editions/aerynOS_KDE_August26.webp)
 
 ## Features
 
@@ -47,6 +44,6 @@ Want a rolling release distribution that just works? We're building AerynOS to b
 
 ## For Contributors
 
-Want to be part of something amazing? AerynOS is a community-driven project where everyone can make a meaningful impact. Our powerful yet simple boulder recipes make packaging accessible to newcomers, while our clean stateless design and predictable `/usr` layout helps you understand exactly how changes will impact the system. Whether you're interested in packaging, development, documentation, testing, or community support - check out our [docs](https://aerynos.dev) to see how easy it is to join our growing community and help shape the future of Linux distributions. 🛠️
+Want to be part of something amazing? aerynOS is a community-driven project where everyone can make a meaningful impact. Our powerful yet simple boulder recipes make packaging accessible to newcomers, while our clean stateless design and predictable `/usr` layout helps you understand exactly how changes will impact the system. Whether you're interested in packaging, development, documentation, testing, or community support - check out our [docs](https://aerynos.dev) to see how easy it is to join our growing community and help shape the future of Linux distributions. 🛠️
 
 <Asciinema id="674948" />
diff --git a/src/content/docs/community.mdx b/src/content/docs/community.mdx
index a7f95536..1f481bac 100644
--- a/src/content/docs/community.mdx
+++ b/src/content/docs/community.mdx
@@ -1,6 +1,6 @@
 ---
 title: Community
-description: Join the AerynOS community and help us redefine the future of linux.
+description: Join the aerynOS community and help us redefine the future of linux.
 tableOfContents: false
 ---
 import Community from "@/components/ui/Community.astro";
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index 1886c57f..d9cdc63c 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -1,5 +1,5 @@
 ---
-title: AerynOS
+title: aerynOS
 description: Experience the future of Linux today
 
 # want to use custom layout for this page
@@ -29,8 +29,8 @@ import BoxSectionBox from '@/components/splash/BoxSectionBox.astro';
 import BoxSectionOutro from '@/components/splash/BoxSectionOutro.astro';
 
 <SplashContent>
-<h1>AerynOS</h1>
-  <p>AerynOS is an independent performance-oriented Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment. The code-base is currently in an alpha "technical preview" stage, which means that it is not yet ready for widespread use. However, we are committed to eventually providing a stable and reliable operating system that will be easy to use and customize.</p>
+<h1>aerynOS</h1>
+  <p>aerynOS is an independent performance-oriented Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment. The code-base is currently in an alpha "technical preview" stage, which means that it is not yet ready for widespread use. However, we are committed to eventually providing a stable and reliable operating system that will be easy to use and customize.</p>
 
   <div class="button-grid">
     <LinkButton href="/download" variant="primary" icon="fa6-solid:download">Get Started</LinkButton>
@@ -39,7 +39,7 @@ import BoxSectionOutro from '@/components/splash/BoxSectionOutro.astro';
     <LinkButton href="https://aerynos.dev/" variant="secondary" iconPlacement="end" icon="fa6-solid:circle-arrow-right">Documentation</LinkButton>
   </div>
 
-  ![aerynos_alpha](@/images/editions/AerynOS_KDE_August26.webp)
+  ![aerynos_alpha](@/images/editions/aerynOS_KDE_August26.webp)
 </SplashContent>
 
 <BoxSection>
@@ -57,7 +57,7 @@ import BoxSectionOutro from '@/components/splash/BoxSectionOutro.astro';
 <SplashContent>
   ## The Future of Linux Updates
 
-  Say goodbye to system-wide reboots for every little change. AerynOS brings you live atomic updates that apply instantly, while ensuring your system stays protected through atomic rollbacks if anything goes wrong.
+  Say goodbye to system-wide reboots for every little change. aerynOS brings you live atomic updates that apply instantly, while ensuring your system stays protected through atomic rollbacks if anything goes wrong.
 
   <Asciinema id="gpwBAQCzOBfVLJq5"/>
 
@@ -65,19 +65,15 @@ import BoxSectionOutro from '@/components/splash/BoxSectionOutro.astro';
 
 <BoxSection>
   <BoxSectionBox icon="fa6-solid:box-archive" title="moss" subTitle="Next-Gen Package Manager">
-    [Experience atomic updates](/tooling/moss) that swap your entire system safely in one go.
-    No more partial updates or broken states - everything works, or nothing changes.
+    [Experience atomic updates](/tooling/moss) that swap your entire system safely in one go. No more partial updates or broken states - everything works, or nothing changes.
   </BoxSectionBox>
   <BoxSectionBox icon="fa6-solid:trowel" title="boulder" subTitle="Rapid Build System">
-    [Build packages at lightning speed](/tooling/boulder) with our advanced caching system.
-    Simple YAML recipes mean you spend less time packaging and more time creating.
+    [Build packages at lightning speed](/tooling/boulder) with our advanced caching system. Simple YAML recipes mean you spend less time packaging and more time creating.
   </BoxSectionBox>
   <BoxSectionBox icon="fa6-solid:hard-drive" title="blsforme" subTitle="Smart Boot Management">
-    [Boot management that thinks ahead](https://github.com/AerynOS/blsforme).
-    Handles complex EFI configurations automatically so you never have to worry about boot issues again.
+    [Boot management that thinks ahead](https://github.com/aerynOS/blsforme). Handles complex EFI configurations automatically so you never have to worry about boot issues again.
   </BoxSectionBox>
   <BoxSectionOutro slot="outro">
-    Ready to see more? [Explore our complete toolkit](/tooling) and discover
-    how AerynOS is reshaping the future of Linux.
+    Ready to see more? [Explore our complete toolkit](/tooling) and discover how aerynOS is reshaping the future of Linux.
   </BoxSectionOutro>
 </BoxSection>
diff --git a/src/content/docs/privacy.mdx b/src/content/docs/privacy.mdx
index 10803fbc..7700ebe6 100644
--- a/src/content/docs/privacy.mdx
+++ b/src/content/docs/privacy.mdx
@@ -15,7 +15,7 @@ Our core policy, in laymans terms, is:
 **Contributions**: We require code contributions to be made under an identifiable name, for the purposes of security audits and git history. Additionally, submitting code is understood to be within compliance with the software license of the project in question, and is outside the purview of the GDPR. When submitted, code contributions form a static part of the git history of a given project and cannot be removed. They can only be removed from the used code and git tree, and will not be removed unless there is a valid, software-engineering reason to do so (i.e. compliance, usefulness).
 
 ## 1. Data protection principles
-AerynOS  is committed to processing data in accordance with its responsibilities under the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation-GDPR).
+aerynOS  is committed to processing data in accordance with its responsibilities under the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation-GDPR).
 
 Article 5 of the GDPR requires that personal data shall be:
 a. processed lawfully, fairly and in a transparent manner in relation to individuals;
@@ -27,40 +27,40 @@ f. processed in a manner that ensures appropriate security of the personal data,
 
 ## 2.General provisions
 
-a. This policy applies to all personal data processed by AerynOS.
+a. This policy applies to all personal data processed by aerynOS.
 b. this policy may be updated at any time, without notice. This policy shall be reviewed at least annually.
-c. By using AerynOS, or our services, you agree to all terms of our Privacy Policy.
+c. By using aerynOS, or our services, you agree to all terms of our Privacy Policy.
 
 ## 3. Lawful, fair and transparent processing
 
-a. To ensure its processing of data is lawful, fair and transparent, AerynOS shall maintain a Register of Services.
+a. To ensure its processing of data is lawful, fair and transparent, aerynOS shall maintain a Register of Services.
 b. The Register of Services shall be reviewed at least annually.
-c. AerynOS services are defined as its primary website, its [Forums](https://aerynsos.com)
+c. aerynOS services are defined as its primary website, its [Forums](https://aerynsos.com)
 and its downloads (packages + OS Image Files).
-c. Individuals have the right to access their personal data and any such requests made to AerynOS shall be dealt with in a timely manner, in line with Article 15 of the GDPR.
+c. Individuals have the right to access their personal data and any such requests made to aerynOS shall be dealt with in a timely manner, in line with Article 15 of the GDPR.
 
 ## 4. Lawful purposes
 
-a. All data processed by AerynOS must be done on one of the following lawful bases: consent, contract, legal obligation, vital interests, public task or legitimate interests.
+a. All data processed by aerynOS must be done on one of the following lawful bases: consent, contract, legal obligation, vital interests, public task or legitimate interests.
 b. Where consent is relied upon as a lawful basis for processing data, evidence of opt-in  consent shall be kept with the personal data.
 c. Where communications are sent to individuals based on their consent, the option for the individual to revoke their consent should be clearly available and systems should be in place to ensure such revocation is reflected accurately.
 
 ## 5. Data minimisation
 
-a. AerynOS shall ensure that personal data are adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed.
+a. aerynOS shall ensure that personal data are adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed.
 
 ## 6. Accuracy
 
-a. AerynOS shall take reasonable steps to ensure personal data is accurate.
+a. aerynOS shall take reasonable steps to ensure personal data is accurate.
 b. Where necessary for the lawful basis on which data is processed, steps shall be put in place to ensure that personal data is kept up to date.
 
 ## 7. Archiving / removal
 
-a. AerynOS will ensure that personal data is kept for no longer than necessary.
-b. AerynOS cannot delete content in many cases, and will not attempt to do so, unless it is not in compliance with community guidelines (i.e. offensive content). Instead AerynOS can delete associated data, by ghosting an account, and therefore removing all personal identifiable information. This is applicable only to our content platforms, as our other services have no access to any kind of personally identifiable information.
-For user account deletion, it is not feasible to achieve this with Phabricator, as it becomes a core part of the state and working tree. Instead, AerynOS will 'ghost' an account, by removing any personally identifying information such as the account username or 'real name' field, and deactivating the account against further login attempts.
-AerynOS cannot, and will not, modify any content containing personally identifying information that the user has submitted, as it would invalidate the history of discussions and software development.
-c. AerynOS services and server network do not deliberately collect any identifying information. AerynOS only provides online services over HTTPS (SSL) and at most the servers create automatic access logs with the IP address and timestamp. These logs are only used in short-term analysis to detect any malicious activity from bad actors and potential security breaches. No personally identifying information is attached to the log files and they are automatically purged within a 4-week window.
+a. aerynOS will ensure that personal data is kept for no longer than necessary.
+b. aerynOS cannot delete content in many cases, and will not attempt to do so, unless it is not in compliance with community guidelines (i.e. offensive content). Instead aerynOS can delete associated data, by ghosting an account, and therefore removing all personal identifiable information. This is applicable only to our content platforms, as our other services have no access to any kind of personally identifiable information.
+For user account deletion, it is not feasible to achieve this with Phabricator, as it becomes a core part of the state and working tree. Instead, aerynOS will 'ghost' an account, by removing any personally identifying information such as the account username or 'real name' field, and deactivating the account against further login attempts.
+aerynOS cannot, and will not, modify any content containing personally identifying information that the user has submitted, as it would invalidate the history of discussions and software development.
+c. aerynOS services and server network do not deliberately collect any identifying information. aerynOS only provides online services over HTTPS (SSL) and at most the servers create automatic access logs with the IP address and timestamp. These logs are only used in short-term analysis to detect any malicious activity from bad actors and potential security breaches. No personally identifying information is attached to the log files and they are automatically purged within a 4-week window.
 
 ## 8. External Content
 At times, we may link to or include third-party content on our website. These include, but are not limited to:
@@ -71,17 +71,17 @@ At times, we may link to or include third-party content on our website. These in
 - [YouTube](https://policies.google.com/privacy?hl=en-US)
 - [GitHub](https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement)
 
-The above links will take you to the terms of service and/or privacy policy for those websites. As such, those particular services **may** set cookies on your machine, or process data separately from AerynOS. As such you should refer to their terms for how your data is processed.
+The above links will take you to the terms of service and/or privacy policy for those websites. As such, those particular services **may** set cookies on your machine, or process data separately from aerynOS. As such you should refer to their terms for how your data is processed.
 
 ## 9. Security
 
-a. AerynOS shall ensure that personal data is stored securely using modern software that is kept-up-to-date.
+a. aerynOS shall ensure that personal data is stored securely using modern software that is kept-up-to-date.
 b. Access to personal data shall be limited to personnel who need access and appropriate security should be in place to avoid unauthorised sharing of information.
 c. When personal data is deleted this should be done safely such that the data is irrecoverable.
 d. Appropriate back-up and disaster recovery solutions shall be in place.
 
 ## 10. Breach
-In the event of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data, the AerynOS shall promptly assess the risk to people’s rights and freedoms and if appropriate report this breach to the relevant Data Protection Authority, usually, the Irish Data Protection Commission.
+In the event of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data, the aerynOS shall promptly assess the risk to people’s rights and freedoms and if appropriate report this breach to the relevant Data Protection Authority, usually, the Irish Data Protection Commission.
 
 END OF POLICY
 
diff --git a/src/content/docs/roadmap.mdx b/src/content/docs/roadmap.mdx
deleted file mode 100644
index 8cd104d9..00000000
--- a/src/content/docs/roadmap.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: Roadmap 
----
-
diff --git a/src/content/docs/team.mdx b/src/content/docs/team.mdx
deleted file mode 100644
index 492a7dce..00000000
--- a/src/content/docs/team.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: Team
----
-
diff --git a/src/content/docs/tooling/boulder.mdx b/src/content/docs/tooling/boulder.mdx
index a3d30e8f..b9a78af8 100644
--- a/src/content/docs/tooling/boulder.mdx
+++ b/src/content/docs/tooling/boulder.mdx
@@ -1,6 +1,6 @@
 ---
 title: Boulder
-description: Learn more about AerynOS
+description: Learn more about aerynOS
 tableOfContents: false
 ## last page in the docs should disable the next button so that it doesn't go to the first blog post
 next: false
@@ -9,12 +9,8 @@ import { Aside } from '@astrojs/starlight/components';
 
 <Aside title="Boulder">This page is awaiting further enhancement. </Aside>
 
-Building on top of the foundations of [moss](/tooling/moss), we needed a lightning quick tool for building packages so that we can
-easily scale up to deliver important updates for our users. We also needed a slick developer experience with heavy
-caching capabilities, and a familiar build *recipe* format anyone can jump into.
+Building on top of the foundations of [moss](/tooling/moss), we needed a lightning quick tool for building packages so that we can easily scale up to deliver important updates for our users. We also needed a slick developer experience with heavy caching capabilities, and a familiar build *recipe* format anyone can jump into.
 
-To do so, we created `stone.yaml`. This YAML file contains some basic metadata, along with rich, shell-based build
-steps complete with centrally configured **macros** for easily creating package builds in a distro-consistent fashion.
-It is designed as a successor to the `package.yml` format from the [ypkg](https://github.com/getsolus/ypkg) tool in [Solus](https://getsol.us).
+To do so, we created `stone.yaml`. This YAML file contains some basic metadata, along with rich, shell-based build steps complete with centrally configured **macros** for easily creating package builds in a distro-consistent fashion. It is designed as a successor to the `package.yml` format from the [ypkg](https://github.com/getsolus/ypkg) tool in [Solus](https://getsol.us).
 
 For more information, please see the [packaging documentation](https://aerynos.dev/packaging/)
diff --git a/src/content/docs/tooling/index.mdx b/src/content/docs/tooling/index.mdx
index 10fc75a4..5a765092 100644
--- a/src/content/docs/tooling/index.mdx
+++ b/src/content/docs/tooling/index.mdx
@@ -5,33 +5,27 @@ tableOfContents: false
 import { Card, CardGrid } from '@astrojs/starlight/components';
 
 
-Here at AerynOS, we love good tooling. Our language of choice is [Rust](https://rust-lang.org)
-for creating lightning quick tooling with high cadence feature work and minimal debt. Our belief
-is that by providing great tooling, the overall maintainer load is greatly reduced, allowing everyone
-to enjoy a greater developer and user experience.
+Here at aerynOS, we love good tooling. Our language of choice is [Rust](https://rust-lang.org) for creating lightning quick tooling with high cadence feature work and minimal debt. Our belief is that by providing great tooling, the overall maintainer load is greatly reduced, allowing everyone to enjoy a greater developer and user experience.
 
 
 {/* <CardGrid stagger> */}
 
   <Card title="<b>moss</b> - package management">
-    The star of the show is certainly moss, the package and system management tool. With **atomic updates** and
-    **deduplication** at the core of the design, it delivers with performance and reliability.
+    The star of the show is certainly moss, the package and system management tool. With **atomic updates** and **deduplication** at the core of the design, it delivers with performance and reliability.
 
     [read more](/tooling/moss)
   </Card>
 
   <Card title="<b>boulder</b> - package building">
-    The build partner for moss is boulder, an extremely powerful, flexible and easy to use package build tool.
-    Making use of a simple `YAML` format and enriched shell scripts, building consistent packages has never been easier.
+    The build partner for moss is boulder, an extremely powerful, flexible and easy to use package build tool. Making use of a simple `YAML` format and enriched shell scripts, building consistent packages has never been easier.
 
     [read more](/tooling/boulder)
   </Card>
 
 
   <Card title="<b>blsforme</b> - boot management">
-    Nobody should need to manage their boot configuration manually. That's exactly why moss leverages the blsforme project
-    to automatically manage the EFI System Partition (and `XBOOTLDR`..) and manage boot entries.
+    Nobody should need to manage their boot configuration manually. That's exactly why moss leverages the blsforme project to automatically manage the EFI System Partition (and `XBOOTLDR`..) and manage boot entries.
 
-    [read more](https://github.com/AerynOS/blsforme)
+    [read more](https://github.com/aerynOS/blsforme)
   </Card>
 {/* </CardGrid> */}
diff --git a/src/content/docs/tooling/moss.mdx b/src/content/docs/tooling/moss.mdx
index fbd02acc..dc075132 100644
--- a/src/content/docs/tooling/moss.mdx
+++ b/src/content/docs/tooling/moss.mdx
@@ -3,29 +3,17 @@ title: Moss
 tableOfContents: false
 ---
 
-Instead of relying on multiple layers of tools to achieve our aims of a composition-first,
-atomically updating OS, we created our own solution: [moss](https://github.com/AerynOS/os-tools).
+Instead of relying on multiple layers of tools to achieve our aims of a composition-first, atomically updating OS, we created our own solution: [moss](https://github.com/aerynOS/os-tools).
 
-moss looks and feels a lot like a regular package manager, however it actually manages the entire
-operating system via content addressable storage. Every single file from every package is deduplicated
-via a hash-based addressing scheme in the moss store, allowing us to produce new system roots on the fly.
+moss looks and feels a lot like a regular package manager, however it actually manages the entire operating system via content addressable storage. Every single file from every package is deduplicated via a hash-based addressing scheme in the moss store, allowing us to produce new system roots on the fly.
 
-In practice, this means that for every **transaction**, we can efficiently create an entirely new root
-filesystem tree using shared assets, for low-cost, filesystem-agnostic "snapshots". Thanks to some clever
-scaffolding and design we can then **immediately** activate the new transaction as the system root without
-requiring a reboot:
+In practice, this means that for every **transaction**, we can efficiently create an entirely new root filesystem tree using shared assets, for low-cost, filesystem-agnostic "snapshots". Thanks to some clever scaffolding and design we can then **immediately** activate the new transaction as the system root without requiring a reboot:
 
   -  Generate new `/usr` under `/.moss/root`
   - "Activate" via a `renameat2()` (`RENAME_EXCHANGE`) call to swap live `/usr` with `/.moss/root/$ID`
 
-In order to achieve this, we mandated that any package build must only contain files in `/usr`, which also
-means all packages in AerynOS are **stateless**. That also adds some complexities such as running transactional
-scoped "triggers" in namespace, and separating from so-called "system triggers".
+In order to achieve this, we mandated that any package build must only contain files in `/usr`, which also means all packages in aerynOS are **stateless**. That also adds some complexities such as running transactional scoped "triggers" in namespace, and separating from so-called "system triggers".
 
-Additionally we required a type-safe binary format for storing our packages, emitted by `boulder`. This creates
-`.stone` archives that are internally deduplicated, use `zstd` compression and `xxhash` for content addressing.
-For more information, please see the [stone format documentation](https://aerynos.dev/developers/stone/).
+Additionally we required a type-safe binary format for storing our packages, emitted by `boulder`. This creates `.stone` archives that are internally deduplicated, use `zstd` compression and `xxhash` for content addressing. For more information, please see the [stone format documentation](https://aerynos.dev/developers/stone/).
 
-With that said, we think we've done a pretty good job at keeping these internals tidy and presenting a classical
-feeling package manager that doesn't sacrifice on user choice or require a steep learning curve, all while providing
-next generation features like atomic updates and content addressable storage, natively.
+With that said, we think we've done a pretty good job at keeping these internals tidy and presenting a classical feeling package manager that doesn't sacrifice on user choice or require a steep learning curve, all while providing next generation features like atomic updates and content addressable storage, natively.
diff --git a/src/content/edition/gnome.mdx b/src/content/edition/gnome.mdx
index 67c0ded6..83a8aef7 100644
--- a/src/content/edition/gnome.mdx
+++ b/src/content/edition/gnome.mdx
@@ -1,6 +1,6 @@
 ---
 title: "GNOME Edition"
-screenshot: "@/images/editions/AerynOS_Gnome_August26.webp"
+screenshot: "@/images/editions/aerynOS_Gnome_August26.webp"
 screenshot_desc: "GNOME Edition"
 version: "2026.08 (alpha) 🧪"
 url: "https://cdn.aerynos.dev/isos/AerynOS-2026.08-GNOME-live-x86_64.iso"
@@ -8,12 +8,12 @@ checksum_url: "https://cdn.aerynos.dev/isos/AerynOS-2026.08-GNOME-live-x86_64.is
 ---
 import { Aside } from '@astrojs/starlight/components';
 
-AerynOS with [GNOME Desktop](https://www.gnome.org/). Solid GTK integration in a clean, functional package that gets out of your way. We built this to actually work - no bloat, no buzzwords, just a damn good desktop that lets you get things done.
+aerynOS with [GNOME Desktop](https://www.gnome.org/). Solid GTK integration in a clean, functional package that gets out of your way. We built this to actually work - no bloat, no buzzwords, just a damn good desktop that lets you get things done.
 
-We use this Gnome Edition to serve as a vehicle for our alpha `lichen` live installer which is able to install all of our GNOME, KDE Plasma, Cosmic and a 'Terminal Only' versions of AerynOS. It will always pull the latest packages from our repository at the time of installation.
+We use this Gnome Edition to serve as a vehicle for our alpha `lichen` live installer which is able to install all of our GNOME, KDE Plasma, Cosmic and a 'Terminal Only' versions of aerynOS. It will always pull the latest packages from our repository at the time of installation.
 
 You can use the 'Terminal Only' version to assemble your own Desktop Experience with MangoWC, Niri or Sway.
 
-<Aside type="tip">***Ventoy*** is currently [not compatible with AerynOS](https://github.com/ventoy/Ventoy/issues/3550). Use tools such as Etcher or `dd` with a separate USB stick instead.</Aside>
+<Aside type="tip">***Ventoy*** is currently [not compatible with aerynOS](https://github.com/ventoy/Ventoy/issues/3550). Use tools such as Etcher or `dd` with a separate USB stick instead.</Aside>
 
-<Aside type="caution">Our alpha `lichen` installer intentionally does not support dual boot scenarios at this stage. To install AerynOS, your PC needs to be `x86_64-v2` capable (Intel 1st gen Core/AMD FX-4/6/8xxx and up), have working UEFI firmware, and have an entire disk reserved for AerynOS.</Aside>
+<Aside type="caution">Our alpha `lichen` installer intentionally does not support dual boot scenarios at this stage. To install aerynOS, your PC needs to be `x86_64-v2` capable (Intel 1st gen Core/AMD FX-4/6/8xxx and up), have working UEFI firmware, and have an entire disk reserved for aerynOS.</Aside>
diff --git a/src/data/constants.ts b/src/data/constants.ts
index 980f973d..e2ca38ee 100644
--- a/src/data/constants.ts
+++ b/src/data/constants.ts
@@ -1,12 +1,12 @@
 import ogImageSrc from "@/images/logo.png";
 
 export const SITE = {
-  title: "AerynOS",
-  tagline: "Top-quality Hardware Tools",
-  description: "ScrewFast offers top-tier hardware tools and expert construction services to meet all your project needs. Start exploring and contact our sales team for superior quality and reliability.",
-  description_short: "ScrewFast offers top-tier hardware tools and expert construction services to meet all your project needs.",
+  title: "aerynOS",
+  tagline: "A alpha performance focused Linux distribution",
+  description: "aerynOS is an independent performance-oriented Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment. The code-base is currently in an alpha technical preview stage, which means that it is not yet ready for widespread use. However, we are committed to eventually providing a stable and reliable operating system that will be easy to use and customize.",
+  description_short: "aerynOS is an independent performance-oriented Linux-based operating system that diverges significantly from traditional distributions whilst still aiming to provide a familiar and comfortable environment.",
   url: "https://aerynos.com",
-  author: "Emil Gulamov",
+  author: "aerynOS Team",
 };
 
 export const SEO = {
@@ -48,19 +48,19 @@ export const COMMUNITY = [
   {
     title: "GitHub Discussions",
     description: "Join the conversation on GitHub.",
-    url: "https://github.com/AerynOS",
+    url: "https://github.com/aerynOS",
     icon: "tabler:brand-github",
   },
   {
     title: "X",
     description: "Join our community on X.",
-    url: "https://x.com/AerynOS_Linux",
+    url: "https://x.com/aerynOS_Linux",
     icon: "tabler:brand-x",
   },
   {
     title: "Mastodon",
     description: "Join our community on Mastodon.",
-    url: "https://hachyderm.io/@AerynOS",
+    url: "https://hachyderm.io/@aerynOS",
     icon: "tabler:brand-mastodon",
   },
 ];
diff --git a/src/images/editions/AerynOS_GNOME.jpg b/src/images/editions/AerynOS_GNOME.jpg
deleted file mode 100644
index 36ef17e0..00000000
Binary files a/src/images/editions/AerynOS_GNOME.jpg and /dev/null differ
diff --git a/src/images/editions/AerynOS_GNOME.png b/src/images/editions/AerynOS_GNOME.png
deleted file mode 100644
index 3e93ef37..00000000
Binary files a/src/images/editions/AerynOS_GNOME.png and /dev/null differ
diff --git a/src/images/editions/AerynOS_Gnome_May26.png b/src/images/editions/AerynOS_Gnome_May26.png
deleted file mode 100644
index 8a2f33dd..00000000
Binary files a/src/images/editions/AerynOS_Gnome_May26.png and /dev/null differ
diff --git a/src/images/editions/AerynOS_KDE_May26.png b/src/images/editions/AerynOS_KDE_May26.png
deleted file mode 100644
index b50c6f18..00000000
Binary files a/src/images/editions/AerynOS_KDE_May26.png and /dev/null differ
diff --git a/src/images/editions/AerynOS_Gnome_August26.webp b/src/images/editions/aerynOS_Gnome_August26.webp
similarity index 100%
rename from src/images/editions/AerynOS_Gnome_August26.webp
rename to src/images/editions/aerynOS_Gnome_August26.webp
diff --git a/src/images/editions/AerynOS_KDE_August26.webp b/src/images/editions/aerynOS_KDE_August26.webp
similarity index 100%
rename from src/images/editions/AerynOS_KDE_August26.webp
rename to src/images/editions/aerynOS_KDE_August26.webp
diff --git a/src/images/editions/aerynos_alpha.png b/src/images/editions/aerynos_alpha.png
deleted file mode 100644
index 588c193e..00000000
Binary files a/src/images/editions/aerynos_alpha.png and /dev/null differ
diff --git a/src/images/editions/cosmic_prealpha.png b/src/images/editions/cosmic_prealpha.png
deleted file mode 100644
index 04b18d07..00000000
Binary files a/src/images/editions/cosmic_prealpha.png and /dev/null differ
diff --git a/src/images/editions/gnome_alpha.png b/src/images/editions/gnome_alpha.png
deleted file mode 100644
index db2f03e9..00000000
Binary files a/src/images/editions/gnome_alpha.png and /dev/null differ
diff --git a/src/images/editions/gnome_prealpha_dark.png b/src/images/editions/gnome_prealpha_dark.png
deleted file mode 100644
index 700efce6..00000000
Binary files a/src/images/editions/gnome_prealpha_dark.png and /dev/null differ
diff --git a/src/pages/manifest.json.ts b/src/pages/manifest.json.ts
index a5efae9e..30f66d65 100644
--- a/src/pages/manifest.json.ts
+++ b/src/pages/manifest.json.ts
@@ -44,8 +44,8 @@ export const GET: APIRoute = async () => {
   );
 
   const manifest = {
-    short_name: "AerynOS",
-    name: "AerynOS",
+    short_name: "aerynOS",
+    name: "aerynOS",
     icons,
     display: "minimal-ui",
     id: "/",
diff --git a/src/schema_org/index.ts b/src/schema_org/index.ts
index 1f699cb9..e4611534 100644
--- a/src/schema_org/index.ts
+++ b/src/schema_org/index.ts
@@ -20,9 +20,9 @@ export function schema_web_page({
     "isPartOf": {
       "@type": "WebSite",
       "url": "https://aerynos.com",
-      "name": "AerynOS",
+      "name": "aerynOS",
       "description": "Redefining Linux for the modern era.",
     },
     "inLanguage": "en-US"
   }
-}
\ No newline at end of file
+}