about summary refs log tree commit diff
path: root/doc/manual/writing-nix-expressions.xml
diff options
context:
space:
mode:
authorEelco Dolstra <e.dolstra@tudelft.nl>2004-11-09T14·06+0000
committerEelco Dolstra <e.dolstra@tudelft.nl>2004-11-09T14·06+0000
commit32c73268502e35af54953e23038018edb8ce5685 (patch)
tree64a21b6279e62a94113587e16847f2774573d74a /doc/manual/writing-nix-expressions.xml
parent92ee003dc985e6f8331270068b10ca52e9cef793 (diff)
* Typos.
Diffstat (limited to 'doc/manual/writing-nix-expressions.xml')
-rw-r--r--doc/manual/writing-nix-expressions.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/writing-nix-expressions.xml b/doc/manual/writing-nix-expressions.xml
index d1ded020eb71..d29f76f19aef 100644
--- a/doc/manual/writing-nix-expressions.xml
+++ b/doc/manual/writing-nix-expressions.xml
@@ -441,7 +441,7 @@ Hello, world!</screen>
 <para>Generally, however, using <command>nix-env</command> 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:
 
 <programlisting>
@@ -467,7 +467,7 @@ Hello, world!</screen>
 </para>
 
 <para>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 <envar>out</envar> is now
 <quote>valid</quote>.  If you try to build the derivation again, Nix
 will see that the path is already valid and finish immediately.  If a