Rearrangement and cleanup of Part I.

[ardour-manual] / include / signal-routing.html

diff --git a/include/signal-routing.html b/include/signal-routing.html
index 0f4b7162e22ff35861613b63f09bdb9cc77fd3a0..4176d02614a146b6cec2f638994a90df61d6a60d 100644 (file)
--- a/include/signal-routing.html
+++ b/include/signal-routing.html
@@ -1,6 +1,6 @@
 
 <p>
-  Ardour does most of its internal <dfn>signal routing</dfn> via JACK: 
+  Ardour does most of its internal <dfn>signal routing</dfn> via JACK:
   all track and bus inputs and outputs are JACK ports, as are sends and
   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
@@ -11,7 +11,7 @@
 <ul>
   <li>
     <dfn>Track inputs</dfn> are optionally auto-connected to hardware inputs, in round robin
-    order, depending on the setting you chose in the 
+    order, depending on the setting you chose in the
     <a href="@@newopen-session-dialog"><kbd
     class="menu">Session &gt; New Session</kbd> dialog</a>.
   </li>
@@ -30,14 +30,14 @@
   </li>
 </ul>
 <p>
-  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 
+  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.
 </p>
 <p>
-  However, for many workflows during mixing, more complicated signal routing 
-  is required. Ardour offers many possibilties for connecting things in the 
+  However, for many workflows during mixing, more complicated signal routing
+  is required. Ardour offers many possibilties for connecting things in the
   way you may need or want them.
 </p>