aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorValentin Gagarin <valentin@fricklerhandwerk.de>2022-04-22 10:44:00 +0200
committerValentin Gagarin <valentin.gagarin@tweag.io>2022-08-04 12:37:46 +0200
commit23ee0b24f7c0fd43ccf6f99b87941df4cb071689 (patch)
treef96bc0a27fba80148f4fa2731a4dfb5fb5b61e77 /doc
parent804e8bd7473516b087f39161bd34730e26480517 (diff)
correctly use comma for nesting
Co-authored-by: John Ericson <git@JohnEricson.me>
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/src/design/overview.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/src/design/overview.md b/doc/manual/src/design/overview.md
index 20a3fe653..b1adb143b 100644
--- a/doc/manual/src/design/overview.md
+++ b/doc/manual/src/design/overview.md
@@ -16,7 +16,7 @@ In practice this amounts to a set of files in a file system.
The command line and Nix language are what users interact with most.
Underlying everything is the *Nix store*, a mechanism to keep track of build plans, data, and references between them.
-It can also execute *build instructions* captured in the build plans, to produce new data.
+It can also execute *build instructions*, captured in the build plans, to produce new data.
It uses the file system as a persistence layer, and a database to keep track of references.
This chapter describes Nix starting at the bottom with the store layer, then working its way up to the user-facing components described in the rest of the manual.