about summary refs log tree commit diff
diff options
context:
space:
mode:
authorDan Connolly <dckc@madmode.com>2016-02-19T05·29-0600
committerDan Connolly <dckc@madmode.com>2016-02-19T05·29-0600
commitb39ec410eeb59ed8ae8c2808a79a21578ef801e6 (patch)
treeacfcf7241d7cb2b226e74384fa0cf088aed3f73e
parent7251a81bde29fe1a17aa5b29dd74a4200239b010 (diff)
context for introducing runtime dependencies
The first occurrence of "runtime dependencies" wasn't related to the surrounding narrative.
-rw-r--r--doc/manual/introduction/about-nix.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/manual/introduction/about-nix.xml b/doc/manual/introduction/about-nix.xml
index 66679ac9a85a..0c58984ac489 100644
--- a/doc/manual/introduction/about-nix.xml
+++ b/doc/manual/introduction/about-nix.xml
@@ -62,9 +62,10 @@ directories such as
 so if a package builds correctly on your system, this is because you
 specified the dependency explicitly.</para>
 
-<para>Runtime dependencies are found by scanning binaries for the hash
-parts of Nix store paths (such as <literal>r8vvq9kq…</literal>).  This
-sounds risky, but it works extremely well.</para>
+<para>Once a package is built, runtime dependencies are found by
+scanning binaries for the hash parts of Nix store paths (such as
+<literal>r8vvq9kq…</literal>).  This sounds risky, but it works
+extremely well.</para>
 
 </simplesect>