[SCM] UNNAMED PROJECT branch, master, updated. 20090201-1-28-g58e5fef

[Daniel Baumann]

The following commit has been merged in the master branch:
commit 58e5fefd387e4ee24b9324b3af70fcff3104046d
Author: Richard Nelson <unixabg at gmail.com>
Date:   Thu Feb 19 14:22:05 2009 -0600

    ch4.1 consistency fixes

diff --git a/xml/chapters/overview.xml b/xml/chapters/overview.xml
index 3422972..3e33e63 100644
--- a/xml/chapters/overview.xml
+++ b/xml/chapters/overview.xml
@@ -10,7 +10,7 @@
 
 <section id="live-helper">
 <title>&live-helper;</title>
-<para>&live-helper; is a collection of scripts that build Debian Live systems.</para>
+<para>&live-helper; is a collection of scripts called helper commands, to build Debian Live systems.</para>
 
 <para>The idea behind live-helper is a framework that uses a configuration directory to completely automate and customize all aspects of building a Live image.</para>
 
@@ -28,9 +28,9 @@
 
 <para>Unlike <command>debhelper</command>, &live-helper; contains a tool to generate a skeleton configuration directory, <filename>lh_config</filename>. This could be considered to be similar to tools such as <command>dh-make</command>. For more information about <filename>lh_config</filename>, please see <xref linkend="lh_config"/>.</para>
 
-<para>Besides the common <filename>config/common</filename>, which is used by all &live-helper; commands, some additional files can be used to configure the behavior of specific helpers. These files are typically named <command>config/foo</command> or <command>config/stage</command> (where "stage", of course, is replaced with the name of the stage that they belong to, and "helper" with the name of the helper).</para>
+<para>Besides the common <filename>config/common</filename>, which is used by all &live-helper; helper commands, some additional files can be used to configure the behavior of specific helper commands. These files are typically named <command>config/foo</command> or <command>config/stage</command> (where "stage", of course, is replaced with the name of the stage that they belong to, and "helper" with the name of the helper).</para>
 
-<para>For example, <command>lh_bootstrap_debootstrap</command> uses files named <filename>config/bootstrap</filename> and <filename>config/bootstrap_debootstrap</filename> to read the options it will use. Generally, these files contain variables with values assigned, one variable per line. Some programs in &live-helper; use pairs of values or slightly more complicated variable assignments.</para>
+<para>For example, the <command>lh_bootstrap_debootstrap</command> helper command uses files named <filename>config/bootstrap</filename> and <filename>config/bootstrap_debootstrap</filename> to read the options it will use. Generally, these files contain variables with values assigned, one variable per line. Some programs in &live-helper; use pairs of values or slightly more complicated variable assignments.</para>
 
 <para>&live-helper; respects environment variables which are present in the context of the shell it is running. If variables can be read from config files, then they override environment variables, and if command line options are used, they override values from config files. If no value for a given variable can be found (and is thus unset), &live-helper; will automatically set it to a default value.</para>
 

-- 
UNNAMED PROJECT