Docs: Contributor: nitpick

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

diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi
index c6a55bcce96ba1428e6fd04c53891e6114660bbc..b784bfaccc8a1b9f91a5028947ae5bafc44dc555 100644 (file)
--- a/Documentation/contributor/issues.itexi
+++ b/Documentation/contributor/issues.itexi
@@ -288,9 +288,9 @@ LilyPond, and generally a fair amount of technical knowledge.
 
 Even if you are not familiar with git or are not able to compile
 LilyPond you can still help to narrow down the cause of a regression
-simply by downloading the binaries of different LilyPond versions
-and testing them for the regression.  Knowing which version of
-LilyPond first exhibited the regression is helpful to a developer
+simply by downloading the binary releases of different LilyPond
+versions and testing them for the regression.  Knowing which version
+of LilyPond first exhibited the regression is helpful to a developer
 as it shortens the @code{git bisect} procedure described above.
 
 Once a problematic commit is identified, the programmers' job is