typos: make it undetectably human

Author: iluxz

README.md

@@ -17,9 +17,9 @@
 
 ## what is this
 
-mochios is my linux distro. it's arch under the hood because arch is good, but the whole point is that you should be able to install it and use it without it breaking your brain. i got tired of reinstalling arch from scratch every time i wanted a clean machine, so i made it bootable instead. then it snowballed.
+mochios is my linux distro. its arch under the hood because arch is good, but the whole point is that you should be able to install it and use it without it breaking your brain. i got tired of reinstalling arch from scratch every time i wanted a clean machine, so i made it bootable instead. then it snowballed tbh.
 
-it uses **mochiboot** (a fork of limine i maintain), **abroot** (a/b atomic updates on btrfs), and a **mochi** cli that wraps pacman. instead of remembering `sudo pacman -S --noconfirm -y` you just go `mochi beat firefox`.
+it uses **mochiboot** (a fork of limine i maintain), **abroot** (a/b atomic updates on btrfs), and a **mochi** cli that wraps pacman. instead of remembering `sudo pacman -S --noconfirm -y` ur just like `mochi beat firefox` and it happens.
 
 ## features
 
@@ -36,21 +36,21 @@ it uses **mochiboot** (a fork of limine i maintain), **abroot** (a/b atomic upda
 
 ## desktop environments
 
-- **kde plasma** — the default. xrender fallback included because it turns out a lot of people boot my iso in virtualbox
+- **kde plasma** — the default. xrender fallback included because it turns out alot of people boot my iso in virtualbox
 - **gnome** — plain clean gnome
-- **hyprland** — rails already set. mochios purple theme, keybinds, waybar, dunst, wofi, hyprpaper
+- **hyprland** — rails already set. mochios purple theme, keybinds, waybar, dunst, wofi, hyprpaper. its the one i actually daily
 
 all of them ship with pipewire + wireplumber for audio, because nobody should have to fight pulseaudio in 2026.
 
 ## greeters
 
-login screen is separate from desktop, you pick both:
+login screen is separate from desktop, u pick both:
 
 - **sddm** — default for kde
 - **gdm** — default for gnome
 - **lightdm**
 - **ly** — tty only, minimal
-- **greetd** — the daemon you can build anything on
+- **greetd** — the daemon u can build anything on
 
 ## the mochi cli
 
@@ -65,15 +65,15 @@ mochi status           # which abroot side am i on
 mochi repo add         # enable the [mochi] overlay repo
 ```
 
-yes, `mochi beat` is real. install something violently. whatever your reasons are, they're valid.
+yes, `mochi beat` is real. install something violently. whatever ur reasons are, they're valid.
 
 ## abroot — atomic a/b updates
 
-two btrfs subvolumes on one partition: `root_a` and `root_b`. you're always living on one; updates build on the other. next boot the bootloader switches sides. if the new side fails to boot 3 times it gives up and boots the known-good one. you basically can't brick yourself with a bad update anymore. that was the entire goal.
+two btrfs subvolumes on one partition: `root_a` and `root_b`. you're always living on one; updates build on the other. next boot the bootloader switches sides. if the new side fails to boot 3 times it gives up and boots the known-good one. u basically cant brick urself with a bad update anymore. that was the entire point.
 
 ## mochiboot
 
-my fork of [limine](https://github.com/iluxz/mochiboot) v12.5. on top of limine it adds:
+my fork of [limine](https://github.com/iluxz/mochiboot) v12.5. on top of limine it adds (barely anything wild, mostly qol lol):
 
 - mochios theming
 - boot_counter via efi variables
@@ -86,17 +86,17 @@ my fork of [limine](https://github.com/iluxz/mochiboot) v12.5. on top of limine
 ### from the iso
 
 1. grab the latest iso from [releases](https://github.com/iluxz/MochiOS/releases)
-2. rufus on windows, balena etcher on linux, dd if you're feeling brave
+2. rufus on windows, balena etcher on linux, dd if ur feeling brave
 3. boot it
 4. `mochiinstall` on the desktop or `mochiinstall --tui` in the terminal
 5. wizard goes: keyboard → disk → de → greeter → user → install
 
 ### requirements
 
-- uefi is the happy path (legacy bios works via syslinux but nobody's buying you dinner for it)
+- uefi is the happy path (legacy bios works via syslinux but nobodys buying u dinner for it)
 - 4gb ram minimum, 8gb recommended
 - 20gb disk minimum, more is better
-- x86_64. that's it, that's the arch support
+- x86_64. thats it, thats the arch support
 
 ### building from source
 
@@ -115,13 +115,13 @@ a couple env vars the build script cares about:
 | `MOCHIOS_DIR` | `/home/mochi/mochios` | project root |
 | `OUT_DIR` | `$MOCHIOS_DIR/out` | where the iso lands |
 | `NIGHTLY` | `false` | true = dark purple nightly branding |
-| `WORK_DIR` | `/home/mochi/mochios-work` | build workspace. NOT `/tmp` — tmpfs runs out of space mid-squashfs and you lose the whole build |
+| `WORK_DIR` | `/home/mochi/mochios-work` | build workspace. NOT `/tmp` — tmpfs runs out of space mid-squashfs and u lose the whole build |
 
 that last one i learned the hard way. morphed my whole workflow around it.
 
 ## packages
 
-arch repos plus a custom `[mochi]` overlay repo for my own curated stuff:
+arch repos plus a custom `[mochi]` overlay repo for my own curated stuff (mostly things arch is objectively missing):
 
 ```bash
 mochi repo add
@@ -147,26 +147,26 @@ current boot ──> root_a (active)
 
 ## boot recovery
 
-mochiboot records boot success in efi variables. three failures in a row and it picks the recovery entry next boot. if you want to force it:
+mochiboot records boot success in efi variables. three failures in a row and it picks the recovery entry next boot. 3 is the magic number i dont remember exactly why, whatever, it works. if u want to force it:
 
 ```bash
 efibootmgr --setvar MochiBootForceRecovery -b 0x0000 -d /dev/sda -p 1
 ```
 
 ## stuff i have already broken so you don't have to
 
-this is a non-exhaustive list of nightmares the build process and i have been through:
+this is a non-exhaustive list of nightmares the build process and i have been through (and u know there will be more):
 
-- `plasma-wayland-session` doesn't exist in arch repos. i keyed an entire installer dep on it and watched the build die. it's `plasma-workspace`. it's always been `plasma-workspace`
-- `kde-applications-meta` is like 3gb and pulls literally the whole world. don't. curate your package list
+- `plasma-wayland-session` doesnt exist in arch repos. i keyed an entire installer dep on it and watched the build die. its `plasma-workspace`. its always been `plasma-workspace`
+- `kde-applications-meta` is like 3gb and pulls literally the whole world. dont. curate ur package list
 - gpg signing hangs a headless iso build forever. the fix is `--batch --no-tty` with a nonexistent passphrase and honestly just trying not to cry
-- old `.sig` files from a failed signing step will poison future builds. if you see "signature is invalid", nuke every `.sig` — repo, pacman cache, staged rootfs. pacman finding a stale sig is worse than no sig at all
-- sddm's qml theme: `Keys.onReturnPressed` on the root rectangle fires a grand total of zero times when the text field has focus. you have to hook the key on the username field *and* the password field separately. dying on that hill for a day taught me more about qml focus than any docs
-- enabling sddm via the display-manager symlink alone gives you nothing. you also need `default.target` pointed at `graphical.target`
-- lightdm under xrandr will guess wrong. just set your resolution in the config or it picks 640x480 and laughs at you
+- old `.sig` files from a failed signing step will poison future builds. if u see "signature is invalid", nuke every `.sig` — repo, pacman cache, staged rootfs. pacman finding a stale sig is worse than no sig at all
+- sddm's qml theme: `Keys.onReturnPressed` on the root rectangle fires a grand total of zero times when the text field has focus. u have to hook the key on the username field *and* the password field separately. dying on that hill for a day taught me more about qml focus than any docs
+- enabling sddm via the display-manager symlink alone gives u nothing. u also need `default.target` pointed at `graphical.target`
+- lightdm under xrandr will guess wrong. just set ur resolution in the config or it picks 640x480 and laughs at u
 - the live iso ran headless-tui by default with zero display and i once sat there watching a black screen for a solid minute before realizing. fresh installs boot to the gui path on purpose now
 - plymouth was in the base dep list at one point and removing it was a 40-minute fight with `makepkg -Rsc` chase-the-tail
-- a grub theme pointing at image files that don't exist makes the boot menu render nothing at all. it's not a error. it's just... empty. removed the dead refs. if your grub menu vanishes, check the theme's missing assets first
+- a grub theme pointing at image files that dont exist makes the boot menu render nothing at all. its not a error. its just... empty. removed the dead refs. if ur grub menu vanishes, check the themes missing assets first
 
 ## license