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

[ardour-manual] / _manual / 15_editing-and-arranging / 12_edit-midi / 10_step-entry.html

diff --git a/_manual/15_editing-and-arranging/12_edit-midi/10_step-entry.html b/_manual/15_editing-and-arranging/12_edit-midi/10_step-entry.html
index 15254156d7186124717982c01f6fdf5167e49863..2246572cae5f2509db2be0f3d92941b974f283d6 100644 (file)
--- a/_manual/15_editing-and-arranging/12_edit-midi/10_step-entry.html
+++ b/_manual/15_editing-and-arranging/12_edit-midi/10_step-entry.html
@@ -8,7 +8,7 @@ title: Step Entry
   
 <p>Sometimes you'll want to edit MIDI data directly from a connected MIDI device like a music keyboard or pad controller. Sometimes you'll want to use the mouse. Sometimes you'll want the fine-grain control, precision and speed of entry that comes from using a custom note entry dialog. </p>
 <p>The step entry dialog is accessed via a right click context menu on the rec-enable button (its there because step entry is related to <em>recording</em> MIDI data. You cannot simultaneously step edit and record MIDI via the track's MIDI port.</p>
-<p><img src="/files/a3/a3_step_entry.png"></p>
+<p><img src="/files/a3/a3_step_entry.png" /></p>
 <p>The dialog (quite closely modelled on Logic's) contains:</p>
 <ul>
 <li>Chord entry switch (successive notes are stacked in a chord until it is released
@@ -49,5 +49,3 @@ title: Step Entry
 </li>
 </ul>
 <p>More or less all actions in the step entry dialog can be driven directly from the keyboard, so you do not need to keep moving back and forth from keyboard to mouse to do complex data insertion.</p>
-<p>The step entry dialog is accessed via a right click context menu on the rec-enable button (its there because step entry is related to <em>recording</em> MIDI data. You cannot simultaneously step edit and record MIDI via the track's MIDI port.</p>
-