Docs: run convert-ly for 2.14.0.

[lilypond.git] / Documentation / usage / updating.itely

diff --git a/Documentation/usage/updating.itely b/Documentation/usage/updating.itely
index 71bb0edfcb39fa1cf4d5e83c9140645f5c92461d..755c530632e8b108c748eddf8c1e4a2133dd9106 100644 (file)
--- a/Documentation/usage/updating.itely
+++ b/Documentation/usage/updating.itely
@@ -4,10 +4,11 @@
     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"
+@c \version "2.14.0"
 
 
 @node Updating files with convert-ly
@@ -77,8 +78,8 @@ convert-ly -e myfile.ly
 
 @noindent
 in the directory containing the file.  This will upgrade
-@code{myfile.ly} in-place and preserve the original file in
-@code{myfile.ly~}.
+@file{myfile.ly} in-place and preserve the original file in
+@file{myfile.ly~}.
 
 @warning{@command{convert-ly} always converts up to the last
 syntax change handled by it.  This means that the @code{\version}
@@ -176,7 +177,7 @@ convert-ly """D:/My Scores/Ode.ly""" > "D:/My Scores/new Ode.ly"
 If the simple @command{convert-ly -e *.ly} command fails because the
 expanded command line becomes too long, the @command{convert-ly}
 command may be placed in a loop instead.  This example for UNIX
-will upgrade all @code{.ly} files in the current directory
+will upgrade all @file{.ly} files in the current directory
 
 @example
 for f in *.ly; do convert-ly -e $f; done;