https://codereview.appspot.com/7518047/diff/4004/Documentation/learning/common-notation.itely File Documentation/learning/common-notation.itely (right):
https://codereview.appspot.com/7518047/diff/4004/Documentation/learning/common-notation.itely#newcode1330 Documentation/learning/common-notation.itely:1330: using @code{\relative}, pitches are interpreted in absolute mode. "Without @code{\relative} ..." https://codereview.appspot.com/7518047/diff/4004/Documentation/learning/common-notation.itely#newcode1398 Documentation/learning/common-notation.itely:1398: If you are storing music in a variable (see @ref{Organizing pieces This entire section would be better repositioned in Organizing pieces with variables. Remember that the LM is intended to be read sequentially by people coming to LilyPond for the first time. At this stage in the manual they have not even tried writing a piece of music, and have not met variables. But happy to see a ref to that section. https://codereview.appspot.com/7518047/diff/4004/Documentation/notation/pitches.itely File Documentation/notation/pitches.itely (right): https://codereview.appspot.com/7518047/diff/4004/Documentation/notation/pitches.itely#newcode155 Documentation/notation/pitches.itely:155: Writing @code{\relative gis''' @{ gis @dots{} @}} makes it easy to Please separate items with a blank line https://codereview.appspot.com/7518047/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
