Docs: LM: Follow-ups to suggestions from Jonathan Wilkes

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index e099c737049d24eda7cb9c4261dac566747877b0..e1db15797fad57ee47d4e35f8ba6ed8b8b6aa8c3 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -215,9 +215,9 @@ typographical details may seem academic.  But it is not.  In
 larger pieces with monotonous rhythms, spacing corrections lead to
 subtle variations in the layout of every line, giving each one a
 distinct visual signature.  Without this signature all lines would
-look the same, and they become like a labyrinth.  If a musician
-looks away once or has a lapse in concentration, he/she may easily
-lose their place on the page.
+look the same, and they become like a labyrinth.  A distinct visual
+signature helps to keep musicians from losing their place on the
+page when they look away or have a lapse in concentration.
 
 Similarly, the strong visual look of bold symbols on heavy staff
 lines stands out better when the music is far away from the
@@ -282,8 +282,8 @@ typographical style must also be accessible to the user.
 
 @item Finally, we continually refine the formatting algorithms, so
 we need a flexible approach to rules.  The C++ language forces a
-certain method of grouping rules that does not mesh well with how
-music notation works.
+certain method of grouping rules that cannot readily be applied to
+formatting music notation.
 
 @end itemize
 
@@ -619,8 +619,8 @@ easy to type:
 @end example
 
 @noindent
-to create a quarter note on middle C and an eighth note on D
-above middle C.
+to create a quarter note on middle C (C1) and an eighth note on
+the D above middle C (D1).
 
 @lilypond[quote]
 {

diff --git a/Documentation/user/scheme-tutorial.itely b/Documentation/user/scheme-tutorial.itely
index fd9e0d2461992e4263157d192dfb775cf1c0b24c..18f79c2d15bfa021aedd3565c9e8100e91fabaf2 100644 (file)
--- a/Documentation/user/scheme-tutorial.itely
+++ b/Documentation/user/scheme-tutorial.itely
@@ -41,7 +41,7 @@ notably Windows, you may need to set the environment variable
 @code{GUILE_LOAD_PATH} to the directory @code{../usr/shr/guile/1.8}
 in the LilyPond installation (for the full path to this directory
 see @ref{Other sources of information}).  Alternatively, Windows
-users may simply chosoe @q{Run} from the Start menu and enter
+users may simply choose @q{Run} from the Start menu and enter
 @q{guile}.
 
 The most basic concept in a language is data typing: numbers, character

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 0b82794f0e9bac394e362746da441cfaa20dba26..b80d9a8c330975963e62b813888b9734f3b4a577 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -1242,7 +1242,9 @@ the input, not relative to the @code{c''} in the initial
 To determine the number of staves in a piece, LilyPond looks at
 the beginning of the first expression.  If there is a single note,
 there is one staff; if there is a simultaneous expression, there
-is more than one staff.
+is more than one staff.  The following example shows a complex
+expression, but as it begins with a single note it will be set
+out on a single staff.
 
 @lilypond[verbatim,quote]
 \relative c'' {

diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely
index 1fcdc521adff90bb55a470446d36a1575b02b1c7..304fe5aa75dd4f5424f9d3347e0f5adb1f09881f 100644 (file)
--- a/Documentation/user/tweaks.itely
+++ b/Documentation/user/tweaks.itely
@@ -819,7 +819,8 @@ from arbitrary text strings, which would appear as @code{"a text
 string"}; for more details about symbols and strings, see @ref{Scheme
 tutorial}.
 
-The @code{\override} command needed to print the lyrics in italics is:
+So we see that the @code{\override} command needed to print the lyrics
+in italics is:
 
 @example
 \override LyricText #'font-shape = #'italic