Doc: CG 3.3 separate commits and patches subsections

[lilypond.git] / Documentation / contributor / administration.itexi

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index ec8e751a032ca32bc66d3d6a8cbe1be376342b76..510a799d9170a18b0b09693cf6c354e677ff32f4 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -167,7 +167,7 @@ The Patch Meister's responsibilities are:
 To keep track of all patches submitted for testing and review.  This
 includes scanning the bug and dev email lists looking for any patches
 submitted by @q{random} contributors and advising them on how to submit
 To keep track of all patches submitted for testing and review.  This
 includes scanning the bug and dev email lists looking for any patches
 submitted by @q{random} contributors and advising them on how to submit

-a patch for testing and review.  See @ref{Commits and patches}.
+a patch for testing and review.  See @ref{Patches}.

 
 @item
 To makes sure that any patch submitted has a corresponding Issue Tracker
 
 @item
 To makes sure that any patch submitted has a corresponding Issue Tracker


@@ -803,7 +803,7 @@ Should we change the "structure" / "framework" for bounties?
 (prep: 2 hours.  discuss: 10 hours)
 
 @item @strong{code readability}:
 (prep: 2 hours.  discuss: 10 hours)
 
 @item @strong{code readability}:

-"Our aim when producing source code for Lilypond in whatever
+"Our aim when producing source code for LilyPond in whatever

 language is that it should be totally comprehensible to a
 relatively inexperienced developer at the second reading."
 
 language is that it should be totally comprehensible to a
 relatively inexperienced developer at the second reading."