X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fsignal-routing.html;h=d8b23e8c6e800359f27e3cf2cac22bf332e6c41d;hb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;hp=30a8b69f9e3deb9baed8afd35683de92b3b74c69;hpb=e6123839d20de4f903ed74820cc087fc8401f625;p=ardour-manual

diff --git a/include/signal-routing.html b/include/signal-routing.html
index 30a8b69..d8b23e8 100644
--- a/include/signal-routing.html
+++ b/include/signal-routing.html
@@ -5,7 +5,7 @@
   inserts, which means they can be tapped into by other JACK clients.
   Only the signal flow inside a track or bus (i.e. from <a
   href="/working-with-plugins/processor-box/">processor to processor</a>) is
-  handled internally.<br />
+  handled internally.<br>
   By default, Ardour will create the following connections for you:
 </p>
 <ul>
@@ -33,7 +33,7 @@
   This configuration is sufficient to do basic tracking and playback of many 
   sessions without any adjustment by the user. If you are using Ardour and 
   start to change these connections, be certain that you have a good reason 
-  to do so &mdash; it is generally not necessary and often leads to problems.
+  to do so&mdash;it is generally not necessary and often leads to problems.
 </p>
 <p>
   However, for many workflows during mixing, more complicated signal routing 
@@ -41,5 +41,3 @@
   way you may need or want them.
 </p>
 
-{% children %}
-