X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Frunning.itely;h=88cb790510e2df3fe9657df2493d9196085c5ba3;hb=46d29e0127e80e9b61460987ee940e36ee05006a;hp=0b992069c119cda3091e249d79fd87630f9c39d5;hpb=651180d1740e69825d07eb83e1454b3cf534b734;p=lilypond.git

diff --git a/Documentation/user/running.itely b/Documentation/user/running.itely
index 0b992069c1..88cb790510 100644
--- a/Documentation/user/running.itely
+++ b/Documentation/user/running.itely
@@ -130,7 +130,7 @@ Example: @code{lilypond -fpng filename.ly}
 
 @item -d,--define-default=@var{var}=@var{val}
 This sets the internal program option @var{var} to the Scheme value
-@var{val}. If @var{val} is not supplied, then @var{#t} is used. To
+@var{val}.  If @var{val} is not supplied, then @var{#t} is used.  To
 switch off an option, @code{no-} may be prefixed to @var{var}, e.g.
 
 @cindex point and click, command line
@@ -311,7 +311,7 @@ accomplished in a safe way using @command{sudo}.
 
 Setting up a jail is a slightly delicate matter, as we must be sure that
 LilyPond is able to find whatever it needs to compile the source
-@emph{inside the jail}. A typical setup comprises the following items:
+@emph{inside the jail}.  A typical setup comprises the following items:
 
 @table @asis
 @item Setting up a separate filesystem
@@ -383,9 +383,9 @@ 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
+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}.
+uses more CPU time.  The default value is @code{70}.
 
 @end table
 
@@ -564,7 +564,7 @@ interfaces is quite unlikely; be prepared to tweak scheme code
 manually.
 
 @verbatim
-There are a few things that the convert-ly cannot handle. Here's a list
+There are a few things that the convert-ly cannot handle.  Here's a list
 of limitations that the community has complained about.
 
 This bug report structure has been chosen because convert-ly has a
@@ -573,12 +573,12 @@ Thus this is just a wishlist, placed here for reference.
 
 1.6->2.0:
  Doesn't always convert figured bass correctly, specifically things like {<
->}. Mats' comment on working around this:
+>}.  Mats' comment on working around this:
    To be able to run convert-ly
    on it, I first replaced all occurencies of '{<' to some dummy like '{#'
-   and similarly I replaced '>}' with '&}'. After the conversion, I could
+   and similarly I replaced '>}' with '&}'.  After the conversion, I could
    then change back from '{ #' to '{ <' and from '& }' to '> }'.
- Doesn't convert all text markup correctly. In the old markup syntax,
+ Doesn't convert all text markup correctly.  In the old markup syntax,
  it was possible to group a number of markup commands together within
 parentheses, e.g.
    -#'((bold italic) "string")
@@ -625,7 +625,7 @@ converted.
 @cindex reporting bugs
 
 If you have input that results in a crash or an erroneous output, then
-that is a bug. There is a list of current bugs on our google bug tracker,
+that is a bug.  There is a list of current bugs on our google bug tracker,
 
 @uref{http://code.google.com/p/lilypond/issues/list}