From 32c73268502e35af54953e23038018edb8ce5685 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Tue, 9 Nov 2004 14:06:56 +0000 Subject: [PATCH] * Typos. --- doc/manual/writing-nix-expressions.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/manual/writing-nix-expressions.xml b/doc/manual/writing-nix-expressions.xml index d1ded020e..d29f76f19 100644 --- a/doc/manual/writing-nix-expressions.xml +++ b/doc/manual/writing-nix-expressions.xml @@ -441,7 +441,7 @@ Hello, world! Generally, however, using nix-env is not the best way to test components, since you may not want to install them into your profile right away (they might not work properly, after -all). A better way is to write a short file containging the +all). A better way is to write a short file containing the following: @@ -467,7 +467,7 @@ Hello, world! Nix has a transactional semantics. Once a build finishes -succesfully, Nix makes a note of this in its database: it registers +successfully, Nix makes a note of this in its database: it registers that the path denoted by out is now valid. If you try to build the derivation again, Nix will see that the path is already valid and finish immediately. If a