Update

lrs.md

@@ -20,7 +20,7 @@ The definition here is not strict but rather [fuzzy](fuzzy.md), it is in a form
 - Being [free culture](free_culture.md), i.e. LRS programs are free as a whole, including art assets, data etc.
 - Minimizing [dependencies](dependency.md), even those such as standard library or relying on OS concepts such as files or threads, even indirect ones such as build systems and even non-software ones (e.g. avoiding [floating point](float.md), GPU, 64bit etc.).
 - Very portable, non-discriminating, i.e. being written in a portable language (C, [comun](comun.md) etc.), using as little resources as possible (RAM, CPU, ...) and so on.
-- [Future-proof](future_proof.md), [self-contained](self_contained.md), [finished](finished.md) as much as possible, not controlled by anyone (should follow from other points). This may even include attributes such as physical durability and design that maximizes the devices life.
+- [Future-proof](future_proof.md), [self-contained](self_contained.md) (just compile and run, no unnecessary config files, daemons, database services, ...), [finished](finished.md) as much as possible, not controlled by anyone (should follow from other points). This may even include attributes such as physical durability and design that maximizes the devices life.
 - [Hacking](hacking.md) friendly and inviting to improvements and customization, highly adhering to [hacker culture](hacking.md).
 - Built on top of other LRS technology such as the [C99](c.md) language, Unix OS, our own libraries etc.
 - Simple permissive licensing (being suckless legally) with great preference of [public domain](public_domain.md), e.g. with [CC0](cc0.md) + patent [waivers](waiver.md).