Reword and reorder to clarify oneVoice in Simultaneous

diff --git a/Documentation/user/simultaneous.itely b/Documentation/user/simultaneous.itely
index 211aa3156db8858b57e07ea2b330c513d88ac2d4..988a5159fa0888b66fd3eb2d7e171be9c7e75ae0 100644 (file)
--- a/Documentation/user/simultaneous.itely
+++ b/Documentation/user/simultaneous.itely
@@ -143,7 +143,6 @@ multiple staves.
 @node Single-staff polyphony
 @unnumberedsubsubsec Single-staff polyphony
 
-@c Already reordered as Carl suggested --FV
 The basic structure of code needed to achieve multiple, independent
 voices in a single staff is illustrated in the following example:
 
@@ -161,17 +160,20 @@ Here, voices are instantiated explicitly and are given a name. The
 that first and third voices get stems up, second and fourth voices get
 stems down, third and fourth voice note heads are horizontally
 shifted, and rests in the respective voices are automatically moved to
-avoid collisions.
+avoid collisions.  Using the @code{\oneVoice} command, all the voice
+settings are put back to the neutral directions typical of a
+single-voice passage.
 
-Using the @code{\oneVoice} command, we can make a voice to be into the
-same @code{Voice} context before and after a temporary polyphonic
-passage.  For example:
+We can make a voice to be into the same @code{Voice} context before
+and after a temporary polyphonic passage.  For example, the following
+construct keeps a voice alive throughout the polyphonic section.  Said
+voice is the first one inside of the two-voice section, and the extra
+voice is the second one.
 
 @example
 << @{ \voiceOne ... @} \new Voice @{ \voiceTwo ... @} >> \oneVoice
 @end example
 
-This construct keeps a voice alive throughout the polyphonic section.
 Using the name given when created, this allows lyrics to be assigned
 to one consistent voice.
 
@@ -198,9 +200,13 @@ to one consistent voice.
 >>
 @end lilypond
 
-The @code{<<@{...@} \\ @{...@}>>} construction can be used as a
-simplified method, where the two (or more) voices are separated by
-double backslashes.  Our first example could be typeset as follows:
+Here, the \voiceOne and \voiceTwo commands help to make clear what
+settings does each voice receive.
+
+The @code{<<@{...@} \\ @{...@}>>} construction, where the two (or
+more) voices are separated by double backslashes, can be used as a
+simplified method to print multiple voices in a single staff.  Our
+first example could be typeset as follows:
 
 @lilypond[quote,relative=3,verbatim]
 <<