Issue 3584: Let convert-ly -d reflect last effective rather than last applied rule

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

diff --git a/Documentation/usage/updating.itely b/Documentation/usage/updating.itely
index 6d8e73216b7c0e4b7bd9a8403f888622a5d9352b..98d3fe16db5ec6c99a42e277ba935edbeec78d1c 100644 (file)
--- a/Documentation/usage/updating.itely
+++ b/Documentation/usage/updating.itely
@@ -150,9 +150,9 @@ The following options can be given:
 @table @code
 @item -d,--diff-version-update
 increase the @code{\version} string only if the file has actually
-been changed.  Without this option (or when any conversion has
-changed the file), the version header reflects the last considered
-conversion rule.
+been changed.  In that case, the version header will correspond to
+the version after the last actual change.  Without that option,
+the version will reflect the last @emph{attempted} conversion.
 
 @item -e,--edit
 Apply the conversions direct to the input file, modifying it