second batch of xhtml validation fixes

diff --git a/_manual/19_synchronization/03_timecode-generators-and-slaves.html b/_manual/19_synchronization/03_timecode-generators-and-slaves.html
index b83935e91ad87f9eccedc0946ade6a82b5a39b02..5c3abaecca801861cd3fe3dd94e71634ca64a4f8 100644 (file)
--- a/_manual/19_synchronization/03_timecode-generators-and-slaves.html
+++ b/_manual/19_synchronization/03_timecode-generators-and-slaves.html
@@ -72,7 +72,7 @@ In <code>session &gt; properties</code> it is possible to define an offset betwe
 
 <p>
 Both LTC and MTC are limited to max of 30fps. Using frame-rates larger than that will disable the generator. In both cases also only 24, 25, 29.97df and 30fps are well defined by specifications (such as SMPTE-12M, EU and the MIDI standard).
-<p>
+</p>
 
 <h3>MTC Generator</h3>
 

diff --git a/_manual/20_default-keyboard-bindings/01_mnemonic-bindings-for-linux.html b/_manual/20_default-keyboard-bindings/01_mnemonic-bindings-for-linux.html
index 03f86f0b9c37c696071b17890edf4ad7882262de..98e074c0b457e6d0c7d54c24bc5040c49dab6f18 100644 (file)
--- a/_manual/20_default-keyboard-bindings/01_mnemonic-bindings-for-linux.html
+++ b/_manual/20_default-keyboard-bindings/01_mnemonic-bindings-for-linux.html
@@ -175,7 +175,7 @@ title: Mnemonic Bindings for Linux
 <dd>Control+3</dd>
 </dl>
 <h3>Aligning with the Edit Point</h3>
-<p>Align operations move regions so that their start/end/sync point is at the edit point. "Relative" operations<br>
+<p>Align operations move regions so that their start/end/sync point is at the edit point. "Relative" operations
 just align the first region and moves other selected regions to maintain relative positioning.</p>
 <dl class="bindings">
 <dt>align end(s)</dt>

diff --git a/_manual/20_default-keyboard-bindings/02_mnemonic-bindings-for-os-x.html b/_manual/20_default-keyboard-bindings/02_mnemonic-bindings-for-os-x.html
index ab4ba4bdd0457121c0c1121bb61f1f9cb530aab2..cb6f2b9c5031b2ba5fa8940cd909567eb85dd3df 100644 (file)
--- a/_manual/20_default-keyboard-bindings/02_mnemonic-bindings-for-os-x.html
+++ b/_manual/20_default-keyboard-bindings/02_mnemonic-bindings-for-os-x.html
@@ -172,7 +172,7 @@ title: Mnemonic Bindings for OS X
 <dd>Cmd+3</dd>
 </dl>
 <h3>Aligning with the Edit Point</h3>
-<p>Align operations move regions so that their start/end/sync point is at the edit point. "Relative" operations<br>
+<p>Align operations move regions so that their start/end/sync point is at the edit point. "Relative" operations
 just align the first region and moves other selected regions to maintain relative positioning.</p>
 <dl class="bindings">
 <dt>align end(s)</dt>

diff --git a/_manual/21_preferences-and-session-properties/01_preferences-dialog.html b/_manual/21_preferences-and-session-properties/01_preferences-dialog.html
index 6499bb7c22188be6915e6c1bb0d1fca1c6bc2132..51ab9eb0f82a0ae74e4a3873e597538d178e2b59 100644 (file)
--- a/_manual/21_preferences-and-session-properties/01_preferences-dialog.html
+++ b/_manual/21_preferences-and-session-properties/01_preferences-dialog.html
@@ -6,5 +6,6 @@ title: Preferences Dialog
 
   
   
-<p><img src="/files/a3/a3_ardour_preferences.png" alt="ardour preferences dialog"></p>
+<p><img src="/files/a3/a3_ardour_preferences.png" alt="ardour preferences
+dialog"/></p>
   

diff --git a/_manual/21_preferences-and-session-properties/02_seession-properties-dialog.html b/_manual/21_preferences-and-session-properties/02_seession-properties-dialog.html
index 154f18968a9347c81eeb3384e142cacda84bfb96..4ae5abab9fc2ab08893bc2655c02dccb65f27d71 100644 (file)
--- a/_manual/21_preferences-and-session-properties/02_seession-properties-dialog.html
+++ b/_manual/21_preferences-and-session-properties/02_seession-properties-dialog.html
@@ -6,5 +6,5 @@ title: Seession Properties Dialog
 
   
   <h2>Session Properties Dialog</h2>
-<p><img src="/files/a3/a3_session_properties.png" alt="session properties dialog"></p>
+<p><img src="/files/a3/a3_session_properties.png" alt="session properties dialog"  /></p>
   

diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html
index c1018301e2a26c656e63561dfe110952aedf43ca..169f6ad835b372579fccfd0f69464643f3c9e504 100644 (file)
--- a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html
+++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html
@@ -18,62 +18,40 @@ OSC support is not enabled by default, but can be turned on via <code>Edit &gt;
 
 <h2>Transport Control</h2>
 <dl class="wide-table">
-<dt>/ardour/transport_stop
-<dt>/ardour/transport_play
-<dt>/ardour/set_transport_speed [transport_speed]
-</dt>
-</dt>
-</dt>
-<dd>where [transport_speed] is a float rangin from -8 to 8.
-</dd>
-<dt>/ardour/ffwd
-<dt>/ardour/rewind
-<dt>/ardour/goto_start
-<dt>/ardour/goto_end
-<dt>/ardour/add_marker
-</dt>
-</dt>
-</dt>
-</dt>
-</dt>
+<dt>/ardour/transport_stop</dt>
+<dt>/ardour/transport_play</dt>
+<dt>/ardour/set_transport_speed [transport_speed]</dt>
+<dd>where [transport_speed] is a float rangin from -8 to 8.</dd>
+<dt>/ardour/ffwd</dt>
+<dt>/ardour/rewind</dt>
+<dt>/ardour/goto_start</dt>
+<dt>/ardour/goto_end</dt>
+<dt>/ardour/add_marker</dt>
 <dd>(adds marker to the current transport position)
 </dd>
-<dt>/ardour/next_marker
-<dt>/ardour/prev_marker
-<dt>/ardour/locate [sample_pos] [with_roll]
-</dt>
-</dt>
-</dt>
+<dt>/ardour/next_marker</dt>
+<dt>/ardour/prev_marker</dt>
+<dt>/ardour/locate [sample_pos] [with_roll]</dt>
 <dd>where [sample_pos] is the target position and [with_roll] is a bool/integer (whether you want transport to be kept rolling or not).
 </dd>
-<dt>/ardour/loop_toggle<br>
-</dt>
+<dt>/ardour/loop_toggle</dt>
 </dl>
 
 <h2>Editing-related</h2>
 <dl class="wide-table">
-<dt> /ardour/undo
-<dt> /ardour/redo
-<dt> /ardour/save_state
-</dt>
-</dt>
-</dt>
-<dd>(this is regular Session _&gt; Save operatio)<br>
-</dd>
+<dt> /ardour/undo</dt>
+<dt> /ardour/redo</dt>
+<dt> /ardour/save_state</dt>
+<dd>(this is regular Session _&gt; Save operatio)</dd>
 </dl>
 
 <h2>Recording control</h2>
 <dl class="wide-table">
-<dt> /ardour/toggle_punch_in
-<dt> /ardour/toggle_punch_out
-<dt> /ardour/rec_enable_toggle
-<dt> /ardour/toggle_all_rec_enables
-</dt>
-</dt>
-</dt>
-</dt>
-<dd>(toggles all tracks recording state). !currently toggles on but not off for 2.0 branch.<br>
-</dd>
+<dt> /ardour/toggle_punch_in</dt>
+<dt> /ardour/toggle_punch_out</dt>
+<dt> /ardour/rec_enable_toggle</dt>
+<dt> /ardour/toggle_all_rec_enables</dt>
+<dd>(toggles all tracks recording state). !currently toggles on but not off for 2.0 branch.</dd>
 </dl>
 
 <h2>Track specific operations</h2>

diff --git a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
index 8bb97e88e27a56fb464638107c7ef1e424316921..d58b2f1451208cf838ba7dcb1455d88ace375f4e 100644 (file)
--- a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
+++ b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
@@ -23,7 +23,7 @@ menu_title: Mackie/Logic Control Devices
 </ul>
 <h2>Enabling Mackie Control in Ardour</h2>
 <p>Navigate to <code>Edit &gt; Preferences &gt; User Interaction</code>. Double-click on "Mackie Control" to see the setup dialog:</p>
-<p><img src="" alt="Mackie Control Setup Dialog"></p>
+<p><img src="" alt="Mackie Control Setup Dialog" /></p>
 <p>From the selector at the top, choose the type of device you are using. (<a href="/missing">What do do if your device is not listed</a>). </p>
 <p>Once your setup is complete, click "OK" to close the dialog. Now click on the enable checkbox for "Mackie Control". </p>
 <h2>Connecting control surface and Ardour MIDI ports</h2>

diff --git a/_manual/22_using-control-surfaces/03_midi-binding-maps.html b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
index f7f42d1ab2dbf3f9940208b4b7129b092a2bf849..13846f1f13a233572889ad7b95172d5d0a0418ff 100644 (file)
--- a/_manual/22_using-control-surfaces/03_midi-binding-maps.html
+++ b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
@@ -196,7 +196,7 @@ Rather than binding to a specific track/bus control, it may be useful to have a
 <dt>
 <code>prev-bank</code>
 </dt>
-<dd>Move track/bus mapping to the previous bank (see Banks below)<br>
+<dd>Move track/bus mapping to the previous bank (see Banks below)
 </dd>
 </dl>
 <h2>Binding to Ardour "actions"</h2>

diff --git a/_manual/22_using-control-surfaces/04_midi-learn.html b/_manual/22_using-control-surfaces/04_midi-learn.html
index 1d7b9aaa34b22414cf9ffc2a30cd5daaafd7b1c1..bab46be6d50c7ca76534e3fe95d77d89fdf14085 100644 (file)
--- a/_manual/22_using-control-surfaces/04_midi-learn.html
+++ b/_manual/22_using-control-surfaces/04_midi-learn.html
@@ -3,7 +3,7 @@ layout: default
 title: MIDI Learn
 ---                        
 
-<h3>Philosophy<h3>
+<h2>Philosophy</h2>
 <p>
 There are no "best" ways to map an arbitrary MIDI controller for
 controlling Ardour. There may be very legitimate reasons for different
@@ -23,7 +23,7 @@ Patchbay. On Linux, a wide variety of tools are available including
 QJackctl, aconnect, Patchage, and more. 
 </p>
 
-<h3>Basics<h3>
+<h2>Basics</h2>
 
 <ol>
   <li>    Enable Generic MIDI control: Options -> Control Surfaces -> Generic MIDI</li>
@@ -34,7 +34,7 @@ QJackctl, aconnect, Patchage, and more.
   <li>The binding is complete. Moving the hardware should control the Ardour fader etc. </li>
 </ol>
 
-<h3>Avoiding work in the future<h3>
+<h2>Avoiding work in the future</h2>
 
 <p>
 If you want the bindings you set up to be used automatically in every