Doc: Resolve some FIXMEs.

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

diff --git a/Documentation/learning/common-notation.itely b/Documentation/learning/common-notation.itely
index 102261a5422d0e8ac953dd8ae47aab3aa17b2c70..02ecf443aa8d425c5382dbd4f270c93869f0ccbb 100644 (file)
--- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -1127,7 +1127,6 @@ introduction to the rest of the manual.
 
 @menu
 * Organizing pieces with variables::
-* Version number::
 * Adding titles::
 * Absolute note names::
 * After the tutorial::
@@ -1227,38 +1226,6 @@ places.  The following example uses the above variables:
 @end example
 
 
-@node Version number
-@subsection Version number
-
-@cindex versioning
-@cindex version
-@cindex version number
-@cindex upgrades
-@cindex future upgrades
-@cindex updating files
-@cindex files, updating
-
-@funindex \version
-@funindex version
-@funindex convert-ly
-
-The @code{\version} statement records the version of LilyPond that
-was used to write the file:
-
-@example
-\version @w{"@version{}"}
-@end example
-
-@noindent
-By convention, this is placed at the top of your LilyPond file.
-
-These annotations make future upgrades of LilyPond go more
-smoothly.  Changes in the syntax are handled with a special
-program, @command{convert-ly}, and it uses @code{\version} to
-determine what rules to apply.  For details, see
-@rprogram{Updating files with convert-ly}.
-
-
 @node Adding titles
 @subsection Adding titles
 
@@ -1399,11 +1366,10 @@ 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
-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!
+If you have not done so already, @emph{please} read @ref{How to
+read the 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!