However, if you compile the documentation, a script called
check_texi_refs can help you with checking and fixing these
cross-references; for information on usage, cd into a source tree
-where documentation has been built, cd into Documentation and look
-for check-xrefs and fix-xrefs targets in 'make help' output. Note
-that you have to find yourself the source files to fix
+where documentation has been built, cd into Documentation and run:
+
+@example
+make check-xrefs
+make fix-xrefs
+@end example
+
+Note that you have to find yourself the source files to fix
cross-references in the generated documentation such as the
Internals Reference; e.g. you can grep scm/ and lily/.
If the snippet is tagged with @qq{docs}, check to see if it
matches our guidelines for @ref{LilyPond formatting}.
+Also, snippets tagged with @qq{docs} should not be explaining
+(replicating) existing material in the docs. They should not
+refer to the docs; the docs should refer to them.
+
@item
If the snippet uses scheme, check that everything looks good and
there are no security risks.
* Run convert-ly on all files, bump parser minimum version.
+* update links to distros providing lilypond packages? link in
+Documentation/web/download.itexi . This has nothing to do with
+the release, but I'm dumping this here so I'll find it when I
+reorganize this list later. -gp
+
* Make FTP directories on lilypond.org
* website: