Docs: fix broken xref in translations

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

diff --git a/Documentation/notation/world.itely b/Documentation/notation/world.itely
index b1efe869d450783f4b56c2046b11f607f4942b43..c2fe01d4f2d0846603ce024935c6110bb648de1e 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"
@@ -27,7 +28,7 @@ music.
 
 @menu
 * References for Arabic music::
-* Arabic note names ::
+* Arabic note names::
 * Arabic key signatures::
 * Arabic time signatures::
 * Arabic music example::
@@ -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.