Fix some dangling references

1 files changed, 18 insertions, 20 deletions

diff --git a/doc/manual/src/glossary.md b/doc/manual/src/glossary.md
index c8bdf4fd2..56af9cd85 100644
--- a/doc/manual/src/glossary.md
+++ b/doc/manual/src/glossary.md
@@ -3,7 +3,7 @@
   - derivation  
     A description of a build action. The result of a derivation is a
     store object. Derivations are typically specified in Nix expressions
-    using the [`derivation` primitive](#ssec-derivation). These are
+    using the [`derivation` primitive](expressions/derivations.md). These are
     translated into low-level *store derivations* (implicitly by
     `nix-env` and `nix-build`, or explicitly by `nix-instantiate`).
 
@@ -53,20 +53,19 @@
     paths.
 
   - reachable  
-    A store path `Q` is reachable from another store path `P` if `Q` is
-    in the [closure](#gloss-closure) of the
-    [references](#gloss-reference) relation.
+    A store path `Q` is reachable from another store path `P` if `Q`
+    is in the *closure* of the *references* relation.
 
   - closure  
     The closure of a store path is the set of store paths that are
     directly or indirectly “reachable” from that store path; that is,
-    it’s the closure of the path under the
-    [references](#gloss-reference) relation. For a package, the closure
-    of its derivation is equivalent to the build-time dependencies,
-    while the closure of its output path is equivalent to its runtime
-    dependencies. For correct deployment it is necessary to deploy whole
-    closures, since otherwise at runtime files could be missing. The
-    command `nix-store -qR` prints out closures of store paths.
+    it’s the closure of the path under the *references* relation. For
+    a package, the closure of its derivation is equivalent to the
+    build-time dependencies, while the closure of its output path is
+    equivalent to its runtime dependencies. For correct deployment it
+    is necessary to deploy whole closures, since otherwise at runtime
+    files could be missing. The command `nix-store -qR` prints out
+    closures of store paths.
     
     As an example, if the store object at path `P` contains a reference
     to path `Q`, then `Q` is in the closure of `P`. Further, if `Q`
@@ -76,7 +75,7 @@
     A store path produced by a derivation.
 
   - deriver  
-    The deriver of an [output path](#gloss-output-path) is the store
+    The deriver of an *output path* is the store
     derivation that built it.
 
   - validity  
@@ -87,16 +86,15 @@
   - user environment  
     An automatically generated store object that consists of a set of
     symlinks to “active” applications, i.e., other store paths. These
-    are generated automatically by [`nix-env`](#sec-nix-env). See
-    [???](#sec-profiles).
+    are generated automatically by
+    [`nix-env`](command-ref/nix-env.md). See *profiles*.
 
   - profile  
-    A symlink to the current [user environment](#gloss-user-env) of a
-    user, e.g., `/nix/var/nix/profiles/default`.
+    A symlink to the current *user environment* of a user, e.g.,
+    `/nix/var/nix/profiles/default`.
 
   - NAR  
     A *N*ix *AR*chive. This is a serialisation of a path in the Nix
-    store. It can contain regular files, directories and symbolic links.
-    NARs are generated and unpacked using `nix-store --dump` and
-    `nix-store
-            --restore`.
+    store. It can contain regular files, directories and symbolic
+    links.  NARs are generated and unpacked using `nix-store --dump`
+    and `nix-store --restore`.