second batch of xhtml validation fixes

[ardour-manual-diverged] / _manual / 22_using-control-surfaces / 04_midi-learn.html

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