Doc: CG: improve Issues.

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 7c36c1e6698adb3a3e2cbee5e4f56760d9fede91..b8e59bc3a31beb8acba5fb7f52d4659b3982f455 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -149,6 +149,14 @@ like Ancient notation, which nobody wants to touch.
 
 @end itemize
 
+The difference between Priority-Medium and Priority-Low is not
+well-defined, both in this policy and in practice.  The only
+answer we can give at the moment is @qq{look at existing items in
+of the same type, and try to guess whether the priority is closer
+to the Medium items or Low items}.  We're aware of the ambiguity,
+and won't complain if somebody picks a @q{wrong} value for
+Medium/Low.
+
 
 @subheading Opsys
 
@@ -274,11 +282,11 @@ else about LilyPond development.
 
 Git has special functionality to help tracking down the exact
 commit which causes a problem.  See the git manual page for
-@code{git bisect}.
-
-This is a job that non-programmers can do; once a problematic
-commit is identified, the programmers' job is much easier.  In
-fact, for most regression bugs, the majority of the time is spent
-simply finding the problematic commit.
+@code{git bisect}.  This is a job that non-programmers can do,
+although it requires familiarity with git, ability to compile
+LilyPond, and generally a fair amount of technical knowledge.
 
+Once a problematic commit is identified, the programmers' job is
+much easier.  In fact, for most regression bugs, the majority of
+the time is spent simply finding the problematic commit.