Web: typos and line length in community

diff --git a/Documentation/web/community.itexi b/Documentation/web/community.itexi
index 7cc26d9cd7d84d0ca8546786542518642706f45a..933e2e83961670fb2e10e52473cd388977f03bc3 100644 (file)
--- a/Documentation/web/community.itexi
+++ b/Documentation/web/community.itexi
@@ -876,7 +876,8 @@ manuals can be found at @url{http://lilypond.org}}
 @subheading What is Google Summer of Code?
 
 Quoting
-@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012, GSoC website},
+@uref{http://www.google-melange.com/gsoc/homepage/google/gsoc2012,
+GSoC website},
 @qq{Google Summer of Code is a global program that offers students
 stipends to write code for open source projects.  Google has worked
 with the open source community to identify and fund exciting projects
@@ -884,12 +885,12 @@ for the upcoming summer.}
 
 The LilyPond Team decided that this is an excellent opportunity to find
 new contributors, encourage students already participating in LilyPond
-development to become more involved, and - last but not least - write some
-great code for the benefit of all!
+development to become more involved, and - last but not least - write
+some great code for the benefit of all!
 
 We are participating in GSoC as a part of GNU Project.  See
-@uref{http://www.gnu.org/software/soc-projects/guidelines.html, GNU GSoC webpage}
-for information on how to participate.
+@uref{http://www.gnu.org/software/soc-projects/guidelines.html,
+GNU GSoC webpage} for information on how to participate.
 
 @divEnd
 
@@ -908,10 +909,11 @@ have basic music notation knowledge.
 
 Fix problems with synchronization of grace notes,
 together with all underlying architecture (see
-@uref{http://code.google.com/p/lilypond/issues/detail?id=34, issue 34 in our tracker}).
-Grace notes are confusing to LilyPond's timing because they're like
-going back in time.  This causes weird effects, especially when one staff
-has a grace note and the other doesn't.
+@uref{http://code.google.com/p/lilypond/issues/detail?id=34,
+issue 34 in our tracker}).  Grace notes are confusing to LilyPond's
+timing because they're like going back in time.  This causes weird
+effects, especially when one staff has a grace note and the other
+doesn't.
 
 @strong{Difficulty:} medium
 
@@ -942,7 +944,7 @@ add a connection from music event to XML tag
 Let all LilyPond engravers do their job
 
 @item
-add ability to link each output object
+Add ability to link each output object
 (basically each stencil / group of stencils) to the music cause
 (and thus to the XML tag in the XML tree)
 
@@ -953,8 +955,9 @@ for each output object to the XML tags
 @end itemize
 @divEnd
 
-The goal will be considered achieved when a (previously chosen) score could be
-imported from MusicXML and exported back with no unintentional loss of data.
+The goal will be considered achieved when a (previously chosen) score
+could be imported from MusicXML and exported back with no unintentional
+loss of data.
 
 @strong{Difficulty:} medium
 
@@ -962,7 +965,8 @@ imported from MusicXML and exported back with no unintentional loss of data.
 
 @strong{Mentor(s):} Reinhold Kainhofer, Mike Solomon
 
-familiarity with other scorewriters (for cross-testing) would be a nice bonus.
+Familiarity with other scorewriters (for cross-testing) would be a nice
+bonus.
 
 @subheading Improve slurs and ties
 
@@ -983,8 +987,8 @@ deciding on the intended output and writing the actual code.
 @subheading Adding special variant of font glyphs
 Adding on-staff-line, between-staff-line, shorter and narrower variants
 of some glyphs, for example accidentals, together with a generic
-infrasctucture to support them.  An example is ancient notation breve notehead
-coming in two variants, with smaller and bigger hole.
+infrastructure to support them.  An example is ancient notation breve
+notehead coming in two variants, with smaller and bigger hole.
 
 @strong{Difficulty:} easy
 
@@ -997,9 +1001,9 @@ coming in two variants, with smaller and bigger hole.
 @subheading Improve beaming
 
 Default positioning of regular, cross-staff, broken and kneed beams
-should be improved.  Beaming should depend on context and neighbor notes (see
-@uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf, section 2.2 here}).
-If possible, reduce beaming computation time.
+should be improved.  Beaming should depend on context and neighbor notes
+(see @uref{http://icking-music-archive.org/lists/sottisier/sottieng.pdf,
+section 2.2 here}).  If possible, reduce beaming computation time.
 
 @strong{Difficulty:} medium
 
@@ -1015,19 +1019,21 @@ If possible, reduce beaming computation time.
 @itemize
 
 @item
-non-monotonic string tunings, like Ukulele
+Non-monotonic string tunings, like Ukulele
 
 @item
-create tablature input mode (currently musical information is entered
+Create tablature input mode (currently musical information is entered
 in western-common-music-notation-terms, i.e. @qq{a quarter f sharp note}
-and then converted to tablature) for transcribing medieval lute tablature
+and then converted to tablature) for transcribing medieval lute
+tablature
 
 @item
-implement modern tablature features, such as bends, pull-off, hammer-on
+Implement modern tablature features, such as bends, pull-off, hammer-on
 
 @item
-if a fretboard shape is defined for a given chord, use this information when
-displaying the chord on the staff (and not just display a default chord shape)
+If a fretboard shape is defined for a given chord, use this information
+when displaying the chord on the staff (and not just display a default
+chord shape)
 
 @end itemize
 @divEnd
@@ -1044,10 +1050,10 @@ displaying the chord on the staff (and not just display a default chord shape)
 
 Clean up compiler warnings, static code analysis, and valgrind warnings.
 Automatic code analysis tools (warnings in @code{g++} and @code{clang})
-and analysis tools like valgrind memory leak detection and callgrind code
-profilers provide valuable information about possible flaws in C++ code.
-Cleaning these warnings would allow us to automatically reject any patch
-which introduced extra warnings.
+and analysis tools like valgrind memory leak detection and callgrind
+code profilers provide valuable information about possible flaws in C++
+code.  Cleaning these warnings would allow us to automatically reject
+any patch which introduced extra warnings.
 
 @strong{Difficulty:} medium