Update FAQ.md

Author: castrojo

docs/FAQ.md

@@ -23,7 +23,7 @@ You can always do what you want, but Bluefin is designed with a certain workflow
 - Containerize your developer environments rather than commingle them with the OS. You can define them per project in a `devcontainers.json` file managed by Git.
 - Stick to flatpaks and homebrew. The ideal is to leave the core OS image unchanged. Layering packages creates a maintenance burden that may be unnecessary to take on.
 - Follow the XDG standards for overriding core OS files. The `/etc`, `/var`, `/usr/local`, and `/opt` directories are writable, and many applications will look here for overrides of the read-only files shipped with the OS image in `/usr`. Add to this your home directory, which contains the `~/.local` and `~/.config` subdirectories, which often allow per-user overrides of system defaults. When you’re [using your UNIX system correctly](https://www.youtube.com/watch?v=JOeY07qKU9c), the read-only part is invisible!
-- Isolate the old-school jank in a container. Mangling packages on your host is for those throwback [paleoosaurs](https://en.wikipedia.org/wiki/Palaeosaurus) among us; you know the type.
+- Isolate the old-school jank in a container. Mangling packages on your host is for those throwback [paleosaurs](https://en.wikipedia.org/wiki/Palaeosaurus) among us; you know the type.
 - Don’t overthink rebooting. Just turn off your PC when you’re not using it, and let the OS updates happen automatically, as they will.
 - Bluefin performs best on Linux friendly hardware like the Framework series of laptops. Check hardware compatibility before making the commitment.
 - Keep Bluefin’s ecosystem healthy by donating to application developers.