Docs: run convert-ly for 2.14.0.

[lilypond.git] / Documentation / usage / running.itely

diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely
index 3fe520836e386053c4e7af471ba02f0beae1af5c..4d32d67e50414b7774a0515fac05e99db828823e 100644 (file)
--- a/Documentation/usage/running.itely
+++ b/Documentation/usage/running.itely
@@ -8,7 +8,7 @@
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.12.0"
+@c \version "2.14.0"
 
 
 @node Running lilypond
@@ -223,7 +223,7 @@ havoc, for example
 The @code{-dsafe} option works by evaluating in-line Scheme
 expressions in a special safe module.  This safe module is derived from
 GUILE @file{safe-r5rs} module, but adds a number of functions of the
-LilyPond API.  These functions are listed in @file{scm/@/safe@/-lily@/.scm}.
+LilyPond API.  These functions are listed in @file{scm/safe-lily.scm}.
 
 In addition, safe mode disallows @code{\include} directives and
 disables the use of backslashes in @TeX{} strings.
@@ -446,10 +446,10 @@ subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
 This selects the language for the warning messages.
 
 @item LILYPOND_GC_YIELD
-With this variable the memory footprint and performance can be
-adjusted.  It is a percentage tunes memory management behavior.  With
-higher values, the program uses more memory, with smaller values, it
-uses more CPU time.  The default value is @code{70}.
+A variable, as a percentage, that tunes memory management
+behavior.  A higher values means the program uses more memory, a
+smaller value means more CPU time is used.  The default value is
+@code{70}.
 
 @end table
 
@@ -752,7 +752,7 @@ problem:
 @unnumberedsubsec Apparent error in @code{../ly/init.ly}
 
 Various obscure error messages may appear about syntax errors in
-@code{../ly/init.ly} if the input file is not correctly formed,
+@file{../ly/init.ly} if the input file is not correctly formed,
 for example, if it does not contain correctly
 matched braces or quote signs.
 
@@ -768,7 +768,7 @@ of a lyrics block and the terminating brace, (@code{@}}).  Without
 this separation the brace is taken to be part of the syllable.  It
 is always advisable to ensure there is white space before and after
 @emph{every} brace.  For the importance of this when using lyrics,
-see @ruser{Lyrics explained}.
+see @ruser{Entering lyrics}.
 
 This error message can also appear if a terminating quote sign,
 (@code{"}), is omitted.  In this case an accompanying error message
@@ -810,4 +810,4 @@ staff by inserting
 
 @noindent
 at its start.  For details, see @qq{Spacing of non-staff lines} in
-@ruser{Vertical spacing inside a system}.
+@ruser{Flexible vertical spacing within systems}.