Update content

Author: Numerio

content/docs/development/api-changes.md

@@ -5,7 +5,7 @@ weight: 2
 
 # API Changes
 
-Differences between the VitruvianOS native API and BeOS/Haiku.
+Differences between the Vitruvian native APIs and BeOS/Haiku.
 
 ## Images
 

content/docs/development/filesystem-layout.md

@@ -5,7 +5,7 @@ weight: 3
 
 # Filesystem Layout
 
-VitruvianOS runs on a standard Linux filesystem hierarchy, but maps BeOS/Haiku path conventions onto it so that application source code written for BeOS or Haiku compiles and runs without path changes.
+Vitruvian runs on a standard Linux filesystem hierarchy, but maps BeOS/Haiku path conventions onto it so that application source code written for BeOS or Haiku compiles and runs without path changes.
 
 ## Boot Filesystem
 
@@ -15,7 +15,7 @@ The reference boot filesystems are **XFS** (standard desktop installs) and **Squ
 
 BeOS and Haiku expose their filesystem tree under `/boot`. In VitruvianOS, `/boot` maps directly to the Linux root `/`, rather than to a separate `/system` subtree:
 
-| BeOS/Haiku path | VitruvianOS path |
+| BeOS/Haiku path | Vitruvian path |
 |-----------------|-----------------|
 | `/boot` | `/` |
 | `/boot/home` | `/home` |
@@ -27,7 +27,7 @@ Standard Linux paths (`/usr`, `/lib`, `/etc`, `/proc`, `/dev`, and so on) coexis
 
 ## Extended Attributes
 
-BeOS relies heavily on filesystem extended attributes for file metadata, MIME types, application signatures, and the attribute database that powers live queries. VitruvianOS stores these as Linux extended attributes (`xattr`). XFS is the recommended boot filesystem because it has no practical per-file xattr size limit, which matches BeOS behavior most closely.
+BeOS relies heavily on filesystem extended attributes for file metadata, MIME types, application signatures, and the attribute database that powers live queries. Vitruvian stores these as Linux extended attributes (`xattr`). XFS is the recommended boot filesystem because it has no practical per-file xattr size limit, which matches BeOS behavior most closely.
 
 {{< hint info >}}
 More detail on individual directories and the attribute namespace is coming.

content/docs/getting-started/_index.md

@@ -4,7 +4,7 @@ weight: 1
 bookCollapseSection: true
 ---
 
-Guides to help you get VitruvianOS up and running.
+Guides to help you get Vitruvian up and running.
 
 - [How to Install](how-to-install/) — write a live image to USB and boot
 - [Virtualization](virtualization/) — run VitruvianOS in QEMU, VirtualBox, or UTM

content/docs/getting-started/building.md

@@ -5,7 +5,7 @@ weight: 1
 
 # Building
 
-How to compile VitruvianOS from source on a Debian-based system.
+How to compile Vitruvian from source on a Debian-based system.
 
 ## Prerequisites
 

content/docs/getting-started/faq.md

@@ -7,7 +7,7 @@ weight: 4
 
 ---
 
-## What is VitruvianOS?
+## What is Vitruvian?
 
 VitruvianOS (V\OS) is an operating system based on Linux, inspired by BeOS. It runs the BeOS/Haiku desktop and API on top of a real-time patched Linux kernel, with custom kernel modules — collectively called **Nexus** — providing the missing BeOS-style system services.