From 51e6bed25e073afac5a7b5e11033769a615d0473 Mon Sep 17 00:00:00 2001 From: Valentin Gagarin Date: Fri, 22 Apr 2022 10:54:43 +0200 Subject: [PATCH] do not mention implementation details Co-authored-by: John Ericson --- doc/manual/src/design/overview.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/manual/src/design/overview.md b/doc/manual/src/design/overview.md index b1adb143b..0cead62ab 100644 --- a/doc/manual/src/design/overview.md +++ b/doc/manual/src/design/overview.md @@ -17,7 +17,6 @@ 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 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.