aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorValentin Gagarin <valentin.gagarin@tweag.io>2022-09-23 14:49:47 +0200
committerValentin Gagarin <valentin.gagarin@tweag.io>2022-11-09 01:29:01 +0100
commit98447c1a7f1538f4d3132c0b79ad5b67e136af85 (patch)
treed7e665e1f411c723fb35e4c47f123b6ab34d1d52
parentb5728ace5d5250a6d52df05802c9fc325153dc2c (diff)
clarify subject of sentence
Co-authored-by: Bryan Honof <bryan.honof@tweag.io>
-rw-r--r--doc/manual/src/architecture/architecture.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/src/architecture/architecture.md b/doc/manual/src/architecture/architecture.md
index 972ff2d58..f113cbf4d 100644
--- a/doc/manual/src/architecture/architecture.md
+++ b/doc/manual/src/architecture/architecture.md
@@ -42,7 +42,7 @@ The command line interface and the Nix language are what users interact with mos
> The Nix language itself does not have a notion of *packages* or *configurations*.
> As far as we are concerned here, the inputs and results of a build plan are just data.
-Underlying these is the [Nix store](../glossary.md#gloss-store), a mechanism to keep track of build plans, data, and references between them.
+Underlying the command line interface and the Nix language is the [Nix store](../glossary.md#gloss-store), a mechanism to keep track of build plans, data, and references between them.
It can also execute build plans to produce new data.
A build plan is a series of *build tasks*.