X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmonitor-signal-flow.html;h=f65c0dc546df15c87e34097a935fd739106007a5;hb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;hp=336adbf0e1d331cc85368937cbf25cfdd7f71fb0;hpb=e6123839d20de4f903ed74820cc087fc8401f625;p=ardour-manual

diff --git a/include/monitor-signal-flow.html b/include/monitor-signal-flow.html
index 336adbf..f65c0dc 100644
--- a/include/monitor-signal-flow.html
+++ b/include/monitor-signal-flow.html
@@ -25,12 +25,10 @@ src="/images/external-monitoring.png" />
 <h3>Software Monitoring</h3> 
 <img class="right" src="/images/ardour-monitoring.png" />
 <p>With the <dfn>software monitoring</dfn> approach, all monitoring is
-  performed by Ardour &mdash; it makes track inputs available at track
+  performed by Ardour&mdash;it makes track inputs available at track
   outputs, governed by various controls. This approach will almost always have
   more routing flexibility than JACK-based monitoring. The disadvantage is
   that there will be some latency between the input and the output, which
   depends for the most part on the JACK buffer size that is being used. 
 </p> 
 
-{% children %}
-