Updating pages : passive form, new menu locations, etc.

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

diff --git a/include/signal-routing.html b/include/signal-routing.html
index 4176d02614a146b6cec2f638994a90df61d6a60d..f8e61d65cbe96d5a9b61886da77e93fd8daf0754 100644 (file)
--- a/include/signal-routing.html
+++ b/include/signal-routing.html
@@ -4,14 +4,16 @@
   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
-  href="/working-with-plugins/processor-box/">processor to processor</a>) is
-  handled internally.<br>
-  By default, Ardour will create the following connections for you:
+  href="@@processor-box">processor to processor</a>) is
+  handled internally.
+</p>
+<p>
+  By default, Ardour will automatically create the following connections:
 </p>
 <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 chosen in the
     <a href="@@newopen-session-dialog"><kbd
     class="menu">Session &gt; New Session</kbd> dialog</a>.
   </li>
@@ -31,13 +33,11 @@
 </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
-  to do so&mdash;it is generally not necessary and often leads to problems.
+  sessions without any adjustment by the user. Changing these connections
+  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
-  way you may need or want them.
+  is required. Ardour offers many possibilties for connecting things to fit any
+  particular workflow.
 </p>
-