CG: minor renamings for Issues and Regtests.

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index 7ee9ef6009f97ea17212ad631b21cf1ee243ec5d..41e9ab6e29833111faccc276e2100ee9631552a6 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -49,9 +49,7 @@ you sort your folders alphabetically.
 @enumerate
 
 @item
-Skim through every section of this chapter, @ref{Issues}.  Read in
-detail any sections called @qq{Bug Squad...}, or any page linked
-from @ref{Bug Squad checklists}.
+Read every section of this chapter, @ref{Issues}.
 
 @item
 If you do not have one already, create a gmail account and send

diff --git a/Documentation/contributor/programming-work.itexi b/Documentation/contributor/programming-work.itexi
index 1e0c37fbd28e6f22bca9531b871b80580de21977..6f3bbb824a6b4e505b57d51d1dea693069b55d21 100644 (file)
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -1310,7 +1310,7 @@ get help from a Linux or OSX developer to do the make tests.
 In order to avoid breaking LilyPond, it is important to verify that
 the regression tests succeed, and that no unwanted changes are
 introduced into the output.  This process is described in
-@ref{Identifying code regressions}.
+@ref{Regtest comparison}.
 
 @subheading Typical developer's edit/compile/test cycle
 

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index 11bcf5a87d642d7240df8ff0a3e1c67c289ba589..e2216f1a0bbc9c0052f30d80726882c9a4d91006 100644 (file)
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -6,7 +6,7 @@
 * Introduction to regression tests::
 * Precompiled regression tests::
 * Compiling regression tests::
-* Identifying code regressions::
+* Regtest comparison::
 * Finding the cause of a regression::
 * Memory and coverage tests::
 * MusicXML tests::
@@ -174,8 +174,8 @@ than building the source code, as described in
 @ref{Requirements for building documentation}.
 
 
-@node Identifying code regressions
-@section Identifying code regressions
+@node Regtest comparison
+@section Regtest comparison
 
 Before modified code is committed to master, a regression test
 comparison must be completed to ensure that the changes have
@@ -266,9 +266,6 @@ automatic regression comparison again.
 @node Finding the cause of a regression
 @section Finding the cause of a regression
 
-@warning{This is not a @qq{simple} task; it requires a fair amount
-of technical knowledge.}
-
 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,