next batch of XHTML validation fixes. somebody really hates markup languages here...

[ardour-manual] / _manual / 14_signal-routing / 07_Patchbay.html

diff --git a/_manual/14_signal-routing/07_Patchbay.html b/_manual/14_signal-routing/07_Patchbay.html
index b59e45b5f2c42e9d202f403e0476c15a9a700340..e02370b903c7cc326a34912b72a9b8b0ead90248 100644 (file)
--- a/_manual/14_signal-routing/07_Patchbay.html
+++ b/_manual/14_signal-routing/07_Patchbay.html
@@ -9,7 +9,7 @@ title: Patchbay
 <blockquote><p>
 Notable exceptions are aux sends and connections to the monitor bus (if you are using one): these cannot be controlled from a patchbay, and are basically not under manual control at all.
 </p></blockquote>
-<p><img align="center" src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay" /></p>
+<p><img src="/ardour/manual/html/screenshots/connection-manager.png" alt="an example patchbay" /></p>
 <p>The patchbay presents two groups of ports; one set of sources (which produce data), and one of destinations (which consume data). Depending on the relative number of each, the sources will be placed on the left or the top of the dialogue, and the destinations on the right or the bottom. Thus, in general, signal flow is from top or left to right or bottom.</p>
 <p>Both sources and destinations are divided up into groups, with each group being given a tab. Click on the appropriate tab to show the ports in each group (‘Ardour Busses’, ‘Ardour Tracks’ and so on).</p>
 <p>The groups that are used are as follows:</p>