* Documentation/user/lilypond-book.itely: small cleanups

[lilypond.git] / Documentation / user / invoking.itexi

diff --git a/Documentation/user/invoking.itexi b/Documentation/user/invoking.itexi
index 92c1580d0c3022bb546fa50bfb058c60cae69d5e..67bafae06f01d3064498e207aa2d92177cbee82c 100644 (file)
--- a/Documentation/user/invoking.itexi
+++ b/Documentation/user/invoking.itexi
@@ -40,13 +40,12 @@ The following options are supported:
 
 @table @code
 
-@item -e,--evaluate=@var{code}
-  Evaluates the Scheme @var{code} before parsing @file{.ly}
-files. Multiple @code{-e} options may be given. They will be evaluated
-sequentially. The function @code{set-lily-option} may be invoked to
-set various debugging options.
-
-
+@item -e,--evaluate=@var{expr}
+Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
+Multiple @code{-e} options may be given, they will be evaluated
+sequentially.  The function @code{ly-set-option} allows for access to
+some internal variables.  Use @code{-e '(ly-option-usage')} for more
+information.
 
 @item -f,--format=@var{format}
 @c
@@ -111,12 +110,18 @@ Show the warranty with which GNU LilyPond comes. (It comes with
 
 
 For processing both the @TeX{} and the PostScript output, you must
-have appropriate environment variables set.  Scripts to do this are
-included in @file{buildscripts/out/lilypond-profile} (for sh shells)
-and @file{buildscripts/out/lilypond-login} (for C-shells), and should
-normally be sourced as part of your login process. If these scripts
-are not run from the system wide login process, then you must run it
-yourself.
+have appropriate environment variables set.  The following scripts  do
+this:
+
+@itemize @bullet
+@item @file{buildscripts/out/lilypond-profile}
+(for sh shells)
+@item  @file{buildscripts/out/lilypond-login} (for C-shells)
+@end itemize
+
+They should normally be sourced as part of your login process. If
+these scripts are not run from the system wide login process, then you
+must run it yourself.
 
 @cindex installing LilyPond