Doc: CG: pre-GOP work on Issues.

[lilypond.git] / Documentation / included / helpus.itexi

diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi
index 986327f7b710edb619175d465e908a801d7e01b6..0bccb6780e30275349c385d04d16583214ec712d 100644 (file)
--- a/Documentation/included/helpus.itexi
+++ b/Documentation/included/helpus.itexi
@@ -24,15 +24,16 @@ of spending time on those simple tasks.
 Mailing list support: answer questions from fellow users.
 
 @item
-Bug reporting: help users create proper @rweb{Bug reports}, and
-aid the Bug Squad in handling @rcontrib{Issues}.
+Bug reporting: help users create proper @rweb{Bug reports}, and/or
+join the Bug Squad to organize @rcontrib{Issues}.
 
 @item
 Documentation: small changes can be proposed by following the
 guidelines for @rcontrib{Documentation suggestions}.
 
 @item
-LilyPond Snippet Repository (LSR): create and fix snippets.  See
+LilyPond Snippet Repository (LSR): create and fix snippets
+following the guidelines in
 @rcontrib{Adding and editing snippets}.
 
 @item
@@ -95,7 +96,11 @@ Frogs, and read @rcontrib{Programming work}.
 
 @subsubheading Frogs
 
-Website and mailist: @uref{http://frogs.lilynet.net}
+Website and mailing list:
+
+@example
+@uref{http://frogs.lilynet.net}
+@end example
 
 The Frogs are ordinary LilyPond users who have chosen to get
 involved in their favorite software's development.  Fixing bugs,
@@ -109,7 +114,11 @@ it, then the word is: @emph{Join the Frogs!}
 
 @subsubheading Grand LilyPond Input Syntax Standardization
 
-Website: @uref{http://lilypond.org/~graham/gliss}
+Website:
+
+@example
+@uref{http://lilypond.org/~graham/gliss}
+@end example
 
 GLISS will stabilize the (non-tweak) input syntax for the upcoming
 LilyPond 3.0.  After updating to 3.0, the input syntax for
@@ -122,7 +131,11 @@ input specification.
 
 @subsubheading Grand Organizing Project
 
-Website: @uref{http://lilypond.org/~graham/gop}
+Website:
+
+@example
+@uref{http://lilypond.org/~graham/gop}
+@end example
 
 GOP will be our big recruiting drive for new contributors.  We
 desperately need to spread the development duties (including