From 34bb806f747d5edc16119e38e2ac44e6b236ac12 Mon Sep 17 00:00:00 2001 From: Ivan Kozik Date: Sat, 10 Aug 2013 21:36:16 +0000 Subject: Fix typos, especially those that end up in the Nix manual --- doc/manual/conf-file.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/manual/conf-file.xml') diff --git a/doc/manual/conf-file.xml b/doc/manual/conf-file.xml index 754c4d029..c37a2da47 100644 --- a/doc/manual/conf-file.xml +++ b/doc/manual/conf-file.xml @@ -101,8 +101,8 @@ flag, e.g. --option gc-keep-outputs false. This option defines the maximum number of jobs that Nix will try to build in parallel. The default is 1. You should generally set it to the number - of CPUs in your system (e.g., 2 on a Athlon 64 - X2). It can be overriden using the () command line switch. @@ -119,7 +119,7 @@ flag, e.g. --option gc-keep-outputs false. enableParallelBuilding is set to true, the builder passes the flag to GNU Make. - It can be overriden using the command line switch and defaults to 1. The value 0 means that the builder should use all available CPU cores in the @@ -134,10 +134,10 @@ flag, e.g. --option gc-keep-outputs false. This option defines the maximum number of seconds that a builder can go without producing any data on standard output or - standard error. This is useful (for instance in a automated + standard error. This is useful (for instance in an automated build system) to catch builds that are stuck in an infinite loop, or to catch remote builds that are hanging due to network - problems. It can be overriden using the command line switch. @@ -153,10 +153,10 @@ flag, e.g. --option gc-keep-outputs false. This option defines the maximum number of seconds that a - builder can run. This is useful (for instance in a automated + builder can run. This is useful (for instance in an automated build system) to catch builds that are stuck in an infinite loop but keep writing to their standard output or standard error. It - can be overriden using the command line switch. -- cgit v1.2.3