Doc: ensure two spaces after end of sentence.

[lilypond.git] / Documentation / notation / world.itely

diff --git a/Documentation/notation/world.itely b/Documentation/notation/world.itely
index 55d7ea0802643ca925afe8b8b5ea7d182e4d2f2d..b7ecce0317e1b7311d63d3dddac89bbfb451a3ef 100644 (file)
--- a/Documentation/notation/world.itely
+++ b/Documentation/notation/world.itely
@@ -3,7 +3,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"
@@ -31,7 +32,7 @@ music.
 * Arabic key signatures::
 * Arabic time signatures::
 * Arabic music example::
-* Further reading::
+* Further reading for Arabic music::
 @end menu
 
 
@@ -340,8 +341,8 @@ Snippets:
 @rlsr{World music}.
 
 
-@node Further reading
-@unnumberedsubsubsec Further reading
+@node Further reading for Arabic music
+@unnumberedsubsubsec Further reading for Arabic music
 
 @enumerate
 
@@ -366,7 +367,7 @@ related through common lower tetra chords, or through modulation.
 @item
 There is not a complete consistency, sometimes even in the same
 text on how key signatures for particular maqams should be
-specified. It is common, however, to use a key signature per
+specified.  It is common, however, to use a key signature per
 group, rather than a different key signature for each different
 maqam.