X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Fpitches.itely;h=647d0a1a36584b9ee40c0fe4b48faffc7cee90e3;hb=3a7c967205c02b195a75074492d5fdd7b2ed4310;hp=322d5e41b495c16c3b4782f7e008b5fb89e28e4e;hpb=88cfc9ee61dece9cffff98ab7f10318633698c39;p=lilypond.git

diff --git a/Documentation/notation/pitches.itely b/Documentation/notation/pitches.itely
index 322d5e41b4..647d0a1a36 100644
--- a/Documentation/notation/pitches.itely
+++ b/Documentation/notation/pitches.itely
@@ -182,7 +182,7 @@ Writing @code{\relative gis''' @{ gis @dots{} @}} makes it easy to
 determine the absolute pitch of the first note inside.
 
 @item no explicit starting pitch
-The form @code{\relative @{ gis''' @dots{} @}}) serves
+The form @code{\relative @{ gis''' @dots{} @}} serves
 as a compact version of the previous option: the first note
 inside is written in absolute pitch itself.  (This happens to be
 equivalent to choosing @code{f} as the reference pitch.)
@@ -666,8 +666,8 @@ The octave of notes may also be checked with the
 checks that the interval between the previous note and the
 @code{@var{controlpitch}} is within a fourth (i.e., the normal
 calculation of relative mode).  If this check fails, a warning is
-printed, but the previous note is not changed.  Future notes are
-relative to the @code{@var{controlpitch}}.
+printed.  While the previous note itself is not changed, future
+notes are relative to the corrected value.
 
 @lilypond[verbatim,quote]
 \relative {