Update README.md

README.md

@@ -58,7 +58,7 @@ UEFI/GPT:
 
 ### Operating system
 
-As the base operatring system NixOS is used.
+As the base operating system NixOS is used.
 
 ### [Garmr](https://gitlab.com/fwlnx/garmr)
 
@@ -68,45 +68,6 @@ Backend daemon
 
 Web frontend
 
-# OLD concept
-
-### ~Update flow~
-
-~State before the update:~
-
-- ~boot entry `last` is set to version 1 (last known working version)~
-- ~boot entry `current` is also set to version 1~
-- ~on every boot the default boot entry is set to `last` automatically in early boot~
-
-~Update process:~
-
-- ~a new version is downloaded as a btrfs snapshot and put into place as version 2~
-- ~`current` boot entry is modified to boot the new version~
-- ~`current` is set as default boot entry~
-
-- ~device reboots into new version 2 via `current` boot entry~
-- ~early boot sets `last` as default boot entry~
-- ~after successful boot:~
-  - ~the user marks the system as functional which sets the `last` boot entry to the current version~
-- ~if something goes wrong:~
-  - ~the system reboots, now with the `last` entry being the default booting into the last known working system~
-  - ~the user gets displayed an error because `last` and `current` is not the pointing to the same version and `last` is booted indicating an error~
-
-### ~Configuration changes~
-
-- ~User changes current config via HTTP API (Web interface)~
-  - ~Background process puts changes into ansible variables in `/config`~
-- ~When user discards changes git repo under `/config` is reset to original state~
-- ~When change is ready and user triggers commit via HTTP API~
-  - ~Changes form a git commit with name `[$VERSION] $username - $change summary`~
-  - ~Timer is setup to revert to old config in 600s~
-  - ~Changes get applied via ansible~
-- ~User confirms working state via HTTP API~
-  - ~Timer get removed~
-- ~If new change is not confirmed and Timer gets triggered~
-  - ~git commit is reverted~
-  - ~Ansible runs again with old config~
-  - ~User get an error message~
 
 ---