an example of minimal example

Documentation/web/community.itexi

 @c -*- coding: utf-8; mode: texinfo; -*-
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  For details, see the Contributors'
     Guide, node Updating translation committishes..
 @end ignore
 
 @include included/authors.itexi
@@ skipping 266 matching lines @@
 @subheading Why create them?
 
 @divClass{keep-bullets}
 @itemize
 
 @item
 The simpler the example is, the quicker potential helpers can
 understand it and help you.
 
 @item
-A simple example demonstrates that you have put effort towards
+A tiny example demonstrates that you have put effort towards
 solving the problem yourself.  When people send huge portions of
-input, it looks like they don't care how if we help them or not.
-
-@item
-Creating a tiny example forces you to understand what is
+input, it looks like they don't care if we help them or not.
+
+@item
+Creating a tiny example helps you to understand what is
 happening.  Many false problem reports can be avoided by
 attempting to create a tiny example; if you cannot replicate a
 @qq{bug} in a tiny example, then the problem was probably an
 insufficient understanding of LilyPond, not an actual bug!
 
 @end itemize
 @divEnd
 
 @divEnd
 
 
 @divClass{column-right-bottom}
-@subheading How do I create them?
-
-@divClass{keep-bullets}
-@itemize
-
-@item
-Include the \version number.
+@subheading How to create them?
+
+@divClass{keep-bullets}
+@itemize
+
+@item
+Include the @code{\version} number.
 
 @item
 Make it small!  Examples about spacing or page layout might
 require many bars of music, but most issues can be reproduced
 using less than a single measure.
 
 @item
 When trying to create an example, try commenting out @w{(@code{%}
-or @code{%@{ @dots{} %@}})} sections of your file.  If you can
-comment something while still demonstrating the main idea, then
-remove the commented-material!
-
-@item
-Avoid using complicated notes, keys, or time signatures, unless
+or @code{%@{ @dots{} %@}})} sections of your file.  If you
+can comment something while still demonstrating the main idea,
+then remove the commented-material.
+
+@item
+Avoid using complicated notes, keys or time signatures, unless
 the bug is about the behavior of those items.
 
 @item
 Do not use @code{\override} or @code{\set} commands unless the bug
-is about those particular commands.
-
-@item
-If possible, attach an image showing what do you want to achieve
-(how the correct output should look like).
+is about those specific commands.
+
+@item
+Optionally, attach an image showing the desired graphical output.
 
 @end itemize
 @divEnd
 
 @divEnd
 
 @divClass{column-center-bottom}
 @subheading How tiny should they be?
 
 Is the code below a minimal example?
@@ skipping 534 matching lines @@
 
 @contactUsAbout{academic papers}
 
 
 @node Old news
 @unnumberedsec Old news
 
 @include web/news-front.itexi
 
 @include web/news.itexi