X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmonitor-setup-in-ardour.html;h=208a49889d569125ddf51e787c8a3d35b2aee2be;hb=e957674fe9b4239dfb346e569724a4b14a704259;hp=fc20e8a16923b2134b27c27cdee3260a63f63181;hpb=a885875b007fa0766edb62d5512e3099e946d055;p=ardour-manual

diff --git a/include/monitor-setup-in-ardour.html b/include/monitor-setup-in-ardour.html
index fc20e8a..208a498 100644
--- a/include/monitor-setup-in-ardour.html
+++ b/include/monitor-setup-in-ardour.html
@@ -2,8 +2,8 @@
 <p>Ardour has three main settings which affect how
   monitoring is performed. The first is
   <kbd class="menu">Edit &gt; Preferences &gt; Audio &gt;
-  Record monitoring handled by</kbd>.  There are two or three
-  options here, depending on the capabilities of your hardware.
+  Record monitoring handled by</kbd>. There are two or three
+  options here, depending on the capabilities of the hardware.
 </p>
 <p> The other two settings are more complex.  One is
   <kbd class="menu">Tape machine mode</kbd>, found in the
@@ -13,23 +13,22 @@
 </p>
 <p>
   Monitoring also depends on the state of the track's record-enable button,
-the session record-enable button, and on whether or not the transport is
-rolling.
+  the session record-enable button, and on whether or not the transport is
+  rolling.
 </p>
 
 <h3>Software or Hardware Monitoring Modes</h3>
 <p>
-If Ardour is set to <dfn>external monitoring</dfn>, the explanation of
-Ardour's monitoring behaviour is simple: it does not do any.
+  If Ardour is set to <dfn>external monitoring</dfn>, Ardour does not do any
+  monitoring.
 </p>
 
 <h2>Monitoring in Non-Tape-Machine Mode</h2>
 <p>
-  When <dfn>Tape-Machine mode is off</dfn>, and a track is armed,
-  Ardour <em>always</em> monitors the live input, except in one case:
-  the transport is rolling, the session is not recording, and
-  <dfn>auto-input</dfn>
-  is active. In this case only, you will hear playback from an armed track.
+  When <dfn>Tape-Machine mode is off</dfn>, and a track is armed, Ardour
+  <em>always</em> monitors the live input, except in one case: if the transport is
+  rolling, the session is not recording, and <dfn>auto-input</dfn> is active,
+  the playback from an armed track will be heard.
 </p>
 <p>
   Unarmed tracks will play back their contents from disc, unless the
@@ -40,11 +39,10 @@ Ardour's monitoring behaviour is simple: it does not do any.
 <h2>Monitoring in Tape-Machine Mode</h2>
 
 <p>
-  In <dfn>Tape-Machine mode</dfn>, things are slightly simpler: when a
-  track is armed, its behaviour is the same as in non-tape-machine mode.
+  In <dfn>Tape-Machine mode</dfn>, when a track is armed, its behaviour is
+  the same as in non-tape-machine mode.
 </p>
 <p>
   Unarmed tracks however will always just play back their contents from
   disk; the live input will never be monitored.
 </p>
-