Use two spaces after a period; thanks Michael Rasmussen!

[lilypond.git] / Documentation / user / tweaks.itely

diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely
index 6d24d3a4225f396c2e5434c3c823690c88a3038d..695b0c53911c3b26b0e0b846599c1faa50a784c8 100644 (file)
--- a/Documentation/user/tweaks.itely
+++ b/Documentation/user/tweaks.itely
@@ -1,5 +1,5 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
-@c This file is part of lilypond.tely
+@c This file is part of lilypond-learning.tely
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
@@ -52,7 +52,7 @@ The easiest solution is to increase the distance between the object
 instead) and the note.  In LilyPond, this is called the
 @code{padding} property; it is measured in staff spaces.  For most
 objects, this value is around 1.0 or less (it varies with each
-object). We want to increase it, so let's try 1.5
+object).  We want to increase it, so let's try 1.5
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
   % temporary code to break this example:
@@ -135,7 +135,7 @@ no text, this tweak does nothing (and does @strong{not} wait until
 the next bit of text).  To change the behavior of everything after
 the command, omit the @code{\once}.  To stop this tweak, use a
 @code{\revert}.  This is explained in depth in
-@ref{The \override command}.
+@ruser{The \override command}.
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=3]
   % temporary code to break this example:
@@ -157,20 +157,20 @@ c4^"piu mosso" d e f
 
 @seealso
 
-This manual: @ref{The \override command}, @ref{Common tweaks}.
+This manual: @ruser{The \override command}, @ruser{Common tweaks}.
 
 
 @node Fixing overlapping notation
 @section Fixing overlapping notation
 
-In @ref{Moving objects}, we saw how to move a @code{TextScript}
+In @ruser{Moving objects}, we saw how to move a @code{TextScript}
 object.  The same mechanism can be used to move other types of
 objects; simply replace @code{TextScript} with the name of
 another object.
 
 To find the object name, look at the @q{@strong{see also}} at
 bottom of the relevant documentation page.  For example, at
-the bottom of @ref{Dynamics}, we see
+the bottom of @ruser{Dynamics}, we see
 
 @quotation
 @seealso
@@ -247,7 +247,7 @@ Note in the second example how important it is to figure out what
 context handles a certain object.  Since the @code{MetronomeMark} object
 is handled in the @code{Score} context, property changes in the
 @code{Voice} context will not be noticed.  For more details, see
-@ref{Constructing a tweak}.
+@ruser{Constructing a tweak}.
 
 @cindex extra-offset
 
@@ -307,8 +307,8 @@ voices:
 } >>
 @end lilypond
 
-To make sure that the just blanked stem doesn't squeeze the too much
-tie, we also lengthen the stem, by setting the @code{length} to
+To make sure that the just-blanked stem doesn't squeeze the tie too much,
+we also lengthen the stem, by setting the @code{length} to
 @code{8},
 
 @lilypond[quote,fragment,relative=2,verbatim]
@@ -377,7 +377,7 @@ of room left on those.
 
 When investigating layout issues, @code{annotate-spacing} is
 an invaluable tool.  This command prints the values of various
-layout spacing commands; see @ref{Displaying spacing} for more
+layout spacing commands; see @ruser{Displaying spacing}, for more
 details.  From the output of @code{annotate-spacing}, we can
 see which margins we may wish to alter.
 
@@ -431,7 +431,7 @@ a system.
 
 @item
 Alter the horizontal spacing via @code{SpacingSpanner}.  See
-@ref{Changing horizontal spacing} for more details.
+@ruser{Changing horizontal spacing}, for more details.
 
 @lilypond[verbatim,quote]
 \score {
@@ -461,8 +461,8 @@ We have seen how LilyPond output can be heavily modified using
 commands like
 @code{\override TextScript #'extra-offset = ( 1 . -1)}.  But
 we have even more power if we use Scheme.  For a full explantion
-of this, see the @ref{Scheme tutorial} and
-@ref{Interfaces for programmers}.
+of this, see the @ruser{Scheme tutorial}, and
+@ruser{Interfaces for programmers}.
 
 We can use Scheme to simply @code{\override} commands,