aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorValentin Gagarin <valentin.gagarin@tweag.io>2022-06-21 14:25:30 +0200
committerValentin Gagarin <valentin.gagarin@tweag.io>2022-08-04 12:37:47 +0200
commit7c656d90ca2c3364fd72543c0aa27115d96ac463 (patch)
tree7122d29b5ef6028fb5dafffbccaf4d200e137fb1 /doc
parent631ca18ee62502dd2e51a8f3c9e2ab656b8382ec (diff)
simplify description of diagram
try not to be too fancy, it's just for reading the diagram out loud.
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/src/architecture/store/store.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/src/architecture/store/store.md b/doc/manual/src/architecture/store/store.md
index f662ed3e7..b3517f9b6 100644
--- a/doc/manual/src/architecture/store/store.md
+++ b/doc/manual/src/architecture/store/store.md
@@ -110,7 +110,7 @@ Store objects are therefore implemented as the pair of
The following diagram shows a radical simplification of how Nix interacts with the operating system:
It uses files as build inputs, and build outputs are files again.
-On the operating system, files are either "dead" data, or "live" as processes, which in turn operate on files, or can bring them to life.
+On the operating system, files can be run as processes, which in turn operate on files.
A build function also amounts to an operating system process (not depicted).
```