X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F15_editing-and-arranging%2F12_edit-midi%2F12_copy-midi-region.html;h=60d2d329fec96648ccf5017ca51a7eb52285a942;hb=b539461b10786cb5d65db8ace96da207dfa0661e;hp=3a48eba626d4401e5e33da60a9a7172ad84e00c1;hpb=7b16cfabc9a6d88a0a924745b14a382b0e6540f6;p=ardour-manual

diff --git a/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html b/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html
index 3a48eba..60d2d32 100644
--- a/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html
+++ b/_manual/15_editing-and-arranging/12_edit-midi/12_copy-midi-region.html
@@ -5,44 +5,46 @@ menu_title: Copy MIDI Region
 ---
 
 <p>
-When copying a MIDI region, Ardour has to decide whether to make the
-copy refer to the same data as the original or not. If it does refer
-to the same data, then editing either the copy or the original will
-affect the both of them. If it refers to an independent copy of the
-data then each one can be edited without affecting the other.
+  When <dfn>copying a MIDI region</dfn>, Ardour has to decide whether to make the
+  copy refer to the same data as the original or not. If it does refer
+  to the same data, then editing either the copy or the original will
+  affect the both of them. If it refers to an independent copy of the
+  data then each one can be edited without affecting the other.
 </p>
 
-<h3>Changing dependent/independent copying for the entire session</h3>
+<h2>Changing dependent/independent copying for the entire session</h2>
 
 <p>
-<code>Sesson > Properties > Misc > MIDI region copies are
-  independent</code> can be used to control the default behaviour when
+  <kbd class="menu">Sesson &gt; Properties &gt; Misc &gt; MIDI region copies are
+  independent</kbd> can be used to control the default behaviour when
   making a copy of a MIDI region. 
 </p>
 <p>
-When enabled, every new copy of a MIDI
-region results in a copy being made of the MIDI data used by the
-region, and the new copy of the region will refer to that data. 
+  When enabled, every new copy of a MIDI
+  region results in a copy being made of the MIDI data used by the
+  region, and the new copy of the region will refer to that data. 
 </p>
 <p>
-When disabled, every new copy of a MIDI region will refer to the same
-MIDI data, and thus editing any copy will change the contents of all
-of them.
+  When disabled, every new copy of a MIDI region will refer to the same
+  MIDI data, and thus editing any copy will change the contents of all
+  of them.
 </p>
-<p>Changing the status of this option has no effect on the existing
+<p>
+  Changing the status of this option has no effect on the existing
   dependent/independent status of existing region copies.
 </p>
 
-<h3>Making an existing copy of a MIDI region independent</h3>
+<h2>Making an existing copy of a MIDI region independent</h2>
 <p>
-Context-click on the MIDI region you want to be
-independent. From the context menu, select <code>MIDI > Unlink From
-  Other Copies</code>. The copy is now using an independent version of
-the data, and edits to the copy will affect only the copy. Other
-copies will continue to share data.
+  Context-click on the MIDI region you want to be
+  independent. From the context menu, select <kbd class="menu">MIDI &gt; Unlink From
+  Other Copies</kbd>. The copy is now using an independent version of
+  the data, and edits to the copy will affect only the copy. Other
+  copies will continue to share data.
 </p>
 
-<p>Note that the copied data only covers the extent of the region when
+<p class="note">
+  Note that the copied data only covers the extent of the region when
   the copy is made. If the region was already trimmed and then a copy
   is made, an independent copy will have no access to data that is
   earlier or later than the bounds of the region it was copied