From 286e7a57c4984eeb0d39bfac6e6078b404e07482 Mon Sep 17 00:00:00 2001 From: Benjamin Hipple Date: Wed, 14 Nov 2018 21:40:47 -0500 Subject: [PATCH] docs: fix minor grammar issues in the manual --- doc/stdenv.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/stdenv.xml b/doc/stdenv.xml index ef45ec301a6b..d27adc0de5a6 100644 --- a/doc/stdenv.xml +++ b/doc/stdenv.xml @@ -2077,7 +2077,7 @@ someVar=$(stripHash $name) Nix itself considers a build-time dependency merely something that should previously be built and accessible at build time—packages themselves are on their own to perform any additional setup. In most cases, that is fine, - and the downstream derivation can deal with it's own dependencies. But for a + and the downstream derivation can deal with its own dependencies. But for a few common tasks, that would result in almost every package doing the same sort of setup work---depending not on the package itself, but entirely on which dependencies were used. @@ -2131,10 +2131,10 @@ someVar=$(stripHash $name) n + 1 dependencies, as only those ones match the compiler's target platform. The hostOffset variable is defined with the current dependency's host offset - targetOffset with its target offset, before it's setup hook - is sourced. Additionally, since most environment hooks don't care about the - target platform, That means the setup hook can append to the right bash - array by doing something like + targetOffset with its target offset, before its setup hook is + sourced. Additionally, since most environment hooks don't care about the + target platform, That means the setup hook can append to the right bash array + by doing something like addEnvHooks "$hostOffset" myBashFunction @@ -2142,7 +2142,7 @@ addEnvHooks "$hostOffset" myBashFunction The existence of setups hooks has long been documented - and packages inside Nixpkgs are free to use these mechanism. Other packages, + and packages inside Nixpkgs are free to use this mechanism. Other packages, however, should not rely on these mechanisms not changing between Nixpkgs versions. Because of the existing issues with this system, there's little benefit from mandating it be stable for any period of time.