···21212222* The commit message follows the same semantics as [nixpkgs][nixpkgs].
2323 * You can use a `#` symbol to specify ambiguities. For example,
2424- `develop#zsh: <rest of commit message>` would tell me that your updating the
2424+ `develop#zsh: <rest of commit message>` would tell me that you're updating the
2525 `zsh` subprofile living under the `develop` profile.
26262727[nixpkgs-fmt]: https://github.com/nix-community/nixpkgs-fmt
+1-1
doc/integrations/cachix.md
···11# Cachix
22The system will automatically pull a cachix.nix at the root if one exists.
33-This is usually created automatically by a `sudo cachix use`. If your more
33+This is usually created automatically by a `sudo cachix use`. If you're more
44inclined to keep the root clean, you can drop any generated files in the
55`cachix` directory into the `profiles/cachix` directory without further
66modification.
+2-2
doc/start/from-nixos.md
···11# From NixOS
2233## Generate Configuration
44-Assuming your happy with your existing partition layout, you can generate a
44+Assuming you're happy with your existing partition layout, you can generate a
55basic NixOS configuration for your system using:
66```sh
77flk up
···2828> them directly into a host module of your own making, and commit that instead.
2929# Installation
30303131-Once your ready to deploy `hosts/my-host.nix`:
3131+Once you're ready to deploy `hosts/my-host.nix`:
3232```sh
3333flk my-host switch
3434```