Doc: fix period and colon placement in a couple of instances.

diff --git a/Documentation/contributor/programming-work.itexi b/Documentation/contributor/programming-work.itexi
index ddf57c9a5e7d389f4dbc7350c6623c85f7d47abe..aa8da23a8ec0bc0fccfe39bbfbc30819a458c627 100644 (file)
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -1894,15 +1894,15 @@ A Music + Music_output_def object leads to a Global_context object (see
 ly_run_translator ())
 
 During interpreting, Global_context + Music leads to a bunch of
-Contexts. (see Global_translator::run_iterator_on_me () )
+Contexts (see Global_translator::run_iterator_on_me ()).
 
 After interpreting, Global_context contains a Score_context (which
 contains staves, lyrics etc.) as a child. Score_context::get_output ()
 spews a Music_output object (either a Paper_score object for notation
 or Performance object for MIDI).
 
-The Music_output object is the entry point for the backend. (see
-ly_render_output () )
+The Music_output object is the entry point for the backend (see
+ly_render_output ()).
 
 The main steps of the backend itself are in
 

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index 10bf481b362020139b447833825b020483885e80..b1a79e477fd0ce5fcbf4960055a613c2260f3797 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -231,7 +231,7 @@ Before release:
 
 * write preface section for manual.
 
-* submit pots for translation : send url of tarball to
+* submit pots for translation: send url of tarball to
 translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
 
 * Check reg test

diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi
index e36661d259b39cd141b71658d20925671d534e17..7f023f00588e2ce5abab2745893b9bdb1e26b56b 100644 (file)
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -1144,8 +1144,8 @@ Contributor's Guide}.
 
 @item To retrieve the Lilypond source code from @code{git},
 copy-and-paste each command from the CG @qq{Main source code}
-section into the terminal. (paste into the terminal with keystroke
-@code{CTRL+SHIFT+V})
+section into the terminal (paste into the terminal with keystroke
+@code{CTRL+SHIFT+V}).
 
 @item Prepare to build Lilypond by running the configuration script.
 Type