X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fcontributor%2Fregressions.itexi;h=7f4c9276169c22f9f52462b9fa95ee595df245c1;hb=fda5ce3457daa5326985d032b9b8bf191cf6e129;hp=45ccbaf7601351007387766861e2a53d49051e5d;hpb=904b46b9fa8fc5c189087058cdf977383a4580d7;p=lilypond.git

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index 45ccbaf760..7f4c927616 100644
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -273,8 +273,8 @@ unless git master changed. In other words, if you work with several branches
 and want to do regtests comparison for all of them, you can
 @code{make test-baseline} with git master, checkout some branch,
 @code{make} and @code{make check} it, then switch to another branch,
-@code{make} and @code{make check} it without doing @code{make test-baseline}
-again.}
+@code{make test-clean}, @code{make} and @code{make check} it without doing
+@code{make test-baseline} again.}
 
 
 @node Finding the cause of a regression
@@ -430,7 +430,9 @@ code has been exercised by the tests.
 
 For tracking memory usage as part of this test, you will need
 GUILE CVS; especially the following patch:
+@smallexample
 @uref{http://www.lilypond.org/vc/old/gub.darcs/patches/guile-1.9-gcstats.patch}.
+@end smallexample
 
 @subheading Code coverage