+* Do not forget to create @cindex entries for new sections of text.
+
+* Try not to use punctuation between an introductory sentence and
+ display material (music, example code).
+
+* Do not refer to LilyPond in the text. The reader knows what the
+ manual is about. If you do, capitalization is LilyPond.
+
+* If you explicitly refer to `lilypond', the program (or any other
+ command to be executed), say `@command{lilypond}'.
+
+* Do not explicitly refer to the reader/user. There is no one else
+ besides the reader and the writer.
+
+* Do not use abbreviations (don't, won't, etc.). If you do, use a
+ comma after it:
+
+ blabla blabla, i.e., blabla blabla
+
+* Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
+
+* The use of the word `illegal' is inappropriate in most cases. Say
+ `invalid' instead.
+
+* Avoid long stretches of input code. Noone is going to read them in
+ print. Instead refer to an example input file (@inputfileref), these
+ are clickable in HTML.
+
+* Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
+
+* Colon usage
+
+ 0. Do not use a colon to introduce examples, sentences just continue
+
+ in the display material.
+
+ 1. To introduce lists
+ 2. When beginning a quote: "So, he said,..."
+ This usage is rarer. Americans often just use a comma.
+ 3. When adding a defining example at the end of a sentence.
+
+* To produce good looking texinfo output (for both TTY and DVI) some
+ additional formatting rules should be followed.
+
+ . Do not use tabs. They expand to nothing in DVI output.
+
+ . Do not use spaces at the beginning of a line (except in @example
+ or @verbatim environments), and do not use more than a single space
+ between words. `makeinfo' copies the input lines verbatim without
+ removing those spaces.
+
+ . Variables or numbers which consist of a single character (probably
+ followed by a punctuation mark) should be tied properly, either to
+ the previous or the next word. Example: