aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
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.