release: 0.1.1

[lilypond.git] / Documentation / mudela-man.doc

diff --git a/Documentation/mudela-man.doc b/Documentation/mudela-man.doc
index afcf5c4c19290d3c9b6cb60ba5faeed878839330..8e3d0de2eacf9b944db34439b28191449f16cf04 100644 (file)
--- a/Documentation/mudela-man.doc
+++ b/Documentation/mudela-man.doc
@@ -15,6 +15,8 @@
 \def\postexample{\par\medskip}
 \def\file#1{{\texttt{#1}}}
 
+\emph{This document is not complete yet}
+
 \section{Introduction}
 
 This document describes the the GNU LilyPond input format, which is an
@@ -24,13 +26,13 @@ short.\footnote{If anybody comes up with a better name, we'd gladly
   take this. Gourlay already uses Musical Description Language,
   G-Sharp Score Definition Language. We're not being original here}
 
-The first aim of Mudela is to define a piece of music, 
-being complete from both from a musical typesetting, 
-as from a musical performing point of view.
+The first aim of Mudela is to define a piece of music, being complete
+from both from a musical typesetting, as from a musical performing
+point of view.
 
 The Musical Definition Language (Mudela), has a logical structure,
 making use of identifiers, that allows for flexible input, and
-definition reuse. See MANIFESTO for reasons and design considerations.
+definition reuse. See \file{MANIFESTO} for reasons and design considerations.
 
 The below included for explanatory purposes only (i.e., for a complete
 and up-to-date definition, see \file{lily/parser.y} and