X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmuting-and-soloing.html;h=fc93dddf44b9effdca8df1620e965063d802728d;hb=8784c09ee467dad5cc148876bfb2e780d40132c0;hp=c5f8afd04514979117327cd84eccde6cfc7039fa;hpb=858e4e6227e192c8d9efc4140fb91603d2d85657;p=ardour-manual

diff --git a/include/muting-and-soloing.html b/include/muting-and-soloing.html
index c5f8afd..fc93ddd 100644
--- a/include/muting-and-soloing.html
+++ b/include/muting-and-soloing.html
@@ -85,7 +85,7 @@
 </p>
 <p>
   In this scheme Solo has no effect other than to mute other non-soloed tracks;
-  with solo (rather then listen), the monitor out is fed from the master bus.
+  with solo (rather than listen), the monitor out is fed from the master bus.
 </p>
 
 <h2>Other solo options</h2>
@@ -100,8 +100,8 @@
   listened to on the master bus, this fader specifies the gain that will be
   applied to other tracks in order to mute them. Setting this level to
   -&infin;&nbsp;dB will mean that other tracks will not be heard at all; setting to
-  some higher value less than 0dB means that other non-soloed tracks will be h
-  eard, just reduced in volume compared to the soloed tracks. Using a value
+  some higher value less than 0dB means that other non-soloed tracks will be heard, just
+  reduced in volume compared to the soloed tracks. Using a value
   larger than -&infin;&nbsp;dB is sometimes called "Solo-In-Front" by other DAWs, because
   the listener has the sense that soloed material is "in front" of other
   material. In Ardour, this is not a distinct mode, but instead the mute cut