* Manual updates.

1 files changed, 24 insertions, 3 deletions

diff --git a/doc/manual/glossary.xml b/doc/manual/glossary.xml
index 2c4f55c7e..cf0da3824 100644
--- a/doc/manual/glossary.xml
+++ b/doc/manual/glossary.xml
@@ -3,10 +3,16 @@
 <glosslist>
 
 
-<glossentry><glossterm>derivation</glossterm>
+<glossentry id="gloss-derivation"><glossterm>derivation</glossterm>
 
   <glossdef><para>A description of a build action.  The result of a
-  derivation is a store object.</para></glossdef>
+  derivation is a store object.  Derivations are typically specified
+  in Nix expressions using the <link
+  linkend="ssec-derivation"><function>derivation</function>
+  primitive</link>.  These are translated into low-level
+  <emphasis>store derivations</emphasis> (implicitly by
+  <command>nix-env</command> and <command>nix-build</command>, or
+  explicitly by <command>nix-instantiate</command>).</para></glossdef>
 
 </glossentry>
 
@@ -73,7 +79,22 @@
 </glossentry>
 
 
+<glossentry><glossterm>closure</glossterm>
+
+  <glossdef><para>The closure of a store path is the set of store
+  paths that are directly or indirectly “reachable” from that store
+  path.  For instance, if the store object at path
+  <varname>P</varname> contains a reference to path
+  <varname>Q</varname>, then <varname>Q</varname> is in the closure of
+  <varname>P</varname>.  For correct deployment it is necessary to
+  deploy whole closures, since otherwise at runtime files could be
+  missing.  The command <command>nix-store -qR</command> prints out
+  closures of store paths.</para></glossdef>
+
+</glossentry>
+
+
 </glosslist>
 
 
-</appendix>
\ No newline at end of file
+</appendix>