Doc: automated-engraving: tweaks. Fixes menu structure and appearance.

[lilypond.git] / Documentation / automated-engraving / input-format.itexi

diff --git a/Documentation/automated-engraving/input-format.itexi b/Documentation/automated-engraving/input-format.itexi
index 5cf8d4c3db42a175902a0f0327bf42a914aa1460..49cc252f01a6f245b057db3abd305bf6e1e18360 100644 (file)
--- a/Documentation/automated-engraving/input-format.itexi
+++ b/Documentation/automated-engraving/input-format.itexi
@@ -1,4 +1,4 @@
-\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
+@c -*- coding: utf-8; mode: texinfo; -*-
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
@@ -32,8 +32,8 @@ typable, e.g.,
 Are a quarter note C1 and eighth note D1, as in this example:
 
 @divClass{float-center}
-@divEnd
 @sourceimage{simple-notation,,,.png}
+@divEnd
 
 On a microscopic scale, such syntax is easy to use. On a larger scale,
 syntax also  needs structure.  How else can  you enter  complex pieces
@@ -62,7 +62,7 @@ and >>.
 
 @verbatim
 
-  &lt<c4 d4 e4>>
+  <<c4 d4 e4>>
 
 @end verbatim
 
@@ -81,7 +81,7 @@ This expression is put in sequence by enclosing it in braces, i.e.,
 
 @verbatim
 
-   { <<c4 d4 e4>&gt f4  }
+   { <<c4 d4 e4>> f4  }
 @end verbatim
 
 
@@ -151,8 +151,5 @@ total
 @end ignore
 
 @divClass{float-right}
-@divEnd
 Next: @ref{conclusion,wrapping it up}, the conclusion.
-
-@bye
-
+@divEnd