Docs: Contributor: nitpick

[lilypond.git] / Documentation / learning / common-notation.itely

diff --git a/Documentation/learning/common-notation.itely b/Documentation/learning/common-notation.itely
index b18a6da5ead2d53ecc0cfe6549929961b6cad5ce..4039e26577b277b65244267fdc0b4575dc596b09 100644 (file)
--- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -4,7 +4,8 @@
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
-    version that you are working on.  See TRANSLATION for details.
+    version that you are working on.  For details, see the Contributors'
+    Guide, node Updating translation committishes..
 @end ignore
 
 @c \version "2.12.0"
@@ -187,11 +188,14 @@ accidentals can be printed according to different rules, see
 
 
 @seealso
-Notation Reference: @ruser{Note names in other languages},
-@ruser{Accidentals}, @ruser{Automatic accidentals},
+Notation Reference:
+@ruser{Note names in other languages},
+@ruser{Accidentals},
+@ruser{Automatic accidentals},
 @ruser{Key signature}.
 
-Music Glossary: @rglos{Pitch names}.
+Music Glossary:
+@rglos{Pitch names}.
 
 
 @node Ties and slurs
@@ -216,7 +220,7 @@ first note being tied.
 
 @lilypond[verbatim,quote,relative=2]
 g4~ g c2~
-c4 ~ c8 a8 ~ a2
+c4~ c8 a8~ a2
 @end lilypond
 
 @subheading Slurs
@@ -259,12 +263,14 @@ indicate the @notation{articulation} of notes, and can be used on
 larger groups of notes.  Slurs and ties can be nested.
 
 @lilypond[verbatim,quote,relative=2]
-c2~( c8 fis fis4 ~ fis2 g2)
+c2~( c8 fis fis4~ fis2 g2)
 @end lilypond
 
 
 @seealso
-Notation Reference: @ruser{Ties}, @ruser{Slurs},
+Notation Reference:
+@ruser{Ties},
+@ruser{Slurs},
 @ruser{Phrasing slurs}.
 
 
@@ -354,8 +360,10 @@ c2\< c2\ff\> c2 c2\!
 
 
 @seealso
-Notation Reference: @ruser{Articulations and ornamentations},
-@ruser{Fingering instructions}, @ruser{Dynamics}.
+Notation Reference:
+@ruser{Articulations and ornamentations},
+@ruser{Fingering instructions},
+@ruser{Dynamics}.
 
 
 @node Adding text
@@ -377,7 +385,7 @@ c1^"espr" a_"legato"
 Extra formatting may be added with the @code{\markup} command:
 
 @lilypond[verbatim,quote,relative=2]
-c1^\markup{ \bold espr}
+c1^\markup{ \bold espr }
 a1_\markup{
   \dynamic f \italic \small { 2nd } \hspace #0.1 \dynamic p
 }
@@ -385,7 +393,8 @@ a1_\markup{
 
 
 @seealso
-Notation Reference: @ruser{Writing text}.
+Notation Reference:
+@ruser{Writing text}.
 
 
 @node Automatic and manual beams
@@ -436,7 +445,9 @@ a8 c b4 d8. c16 b4
 
 
 @seealso
-Notation Reference: @ruser{Automatic beams}, @ruser{Manual beams}.
+Notation Reference:
+@ruser{Automatic beams},
+@ruser{Manual beams}.
 
 
 @node Advanced rhythmic commands
@@ -513,7 +524,9 @@ c2 \acciaccatura b16 c2
 
 
 @seealso
-Notation Reference: @ruser{Grace notes}, @ruser{Tuplets},
+Notation Reference:
+@ruser{Grace notes},
+@ruser{Tuplets},
 @ruser{Upbeats}.
 
 
@@ -779,8 +792,8 @@ every system and also controls the extent of bar lines.
 
 
 @seealso
-Notation Reference: @ruser{Keyboard and other multi-staff
-instruments},
+Notation Reference:
+@ruser{Keyboard and other multi-staff instruments},
 @ruser{Displaying staves}.
 
 
@@ -840,9 +853,11 @@ them here. Instead, the following sections introduce these concepts
 and explain them thoroughly.
 
 @seealso
-Learning Manual: @ref{Voices contain music}.
+Learning Manual:
+@ref{Voices contain music}.
 
-Notation Reference: @ruser{Simultaneous notes}.
+Notation Reference:
+@ruser{Simultaneous notes}.
 
 @node Songs
 @section Songs
@@ -1072,7 +1087,8 @@ Here's an example from Rossini's @notation{Figaro}, where
 
 
 @seealso
-Notation Reference: @ruser{Vocal music}.
+Notation Reference:
+@ruser{Vocal music}.
 
 
 @node Lyrics to multiple staves
@@ -1115,7 +1131,8 @@ pieces with variables}.
 
 
 @seealso
-Notation Reference: @ruser{Vocal music}.
+Notation Reference:
+@ruser{Vocal music}.
 
 
 @node Final touches
@@ -1366,10 +1383,8 @@ cross-references at first reading; when you have read all of the
 Learning Manual, you may want to read some sections again and follow
 cross-references for further reading.
 
-If you have not done so already, @emph{please} read
-FIXME FIXME FIXME
-@c @ref{About the documentation}.
-There is a lot of information about LilyPond, so
+If you have not done so already, @emph{please} read @ref{Overview
+of manuals}.  There is a lot of information about LilyPond, so
 newcomers often do not know where they should look for help.  If
 you spend five minutes reading that section carefully, you might
 save yourself hours of frustration looking in the wrong places!