X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F15_editing-and-arranging%2F03_which-regions-are-affected.html;h=23b5df67a0d45959ee228b78d71d04ad88ab7509;hb=b539461b10786cb5d65db8ace96da207dfa0661e;hp=5e6e413ad4e385cb1d4e26b87daf807c3dcc2818;hpb=7b16cfabc9a6d88a0a924745b14a382b0e6540f6;p=ardour-manual

diff --git a/_manual/15_editing-and-arranging/03_which-regions-are-affected.html b/_manual/15_editing-and-arranging/03_which-regions-are-affected.html
index 5e6e413..23b5df6 100644
--- a/_manual/15_editing-and-arranging/03_which-regions-are-affected.html
+++ b/_manual/15_editing-and-arranging/03_which-regions-are-affected.html
@@ -1,45 +1,48 @@
 ---
 layout: default
-title: What Regions Are Affected?
+title: Which Regions Are Affected?
+menu_title: Affected Regions
 ---                        
-
-
-  
   
 <p>
-  This section explains the rules used to decide what regions are affected
-  by editing operations. You don't really have to understand them - hopefully
-  things will Just Work - but it may be useful to understand the rules some
-  of the time.
+  This section explains the rules used to decide which regions are affected
+  by editing operations. You don't really have to understand them &mdash; hopefully
+  things will Just Work &mdash; but it may be useful eventually to understand the rules.
 </p>
 <p>
-  Ardour divides operations up into those that operate on a single point
-  in time (Split being the obvious example) and those that operate on two 
-  points (which can also be considered to be a range of sorts), Separate 
-  is a good example of this.
+  Editing operations in Ardour either operate on a single point in time 
+  (<kbd class="menu">Split</kbd> being the obvious example) or on two 
+  points (which can also be considered to be a range of sorts), <kbd
+  class="menu">Separate</kbd> is a good example of this.
 </p>
 <p> 
   Most operations will operate on the currently selected region(s), but if 
   no regions are selected, the region that the mouse is in will be used 
   instead. Single-point operations will generally pick a set of regions to 
-  use based on the following rules:</p>
-<ol>
-  <li> If the edit point is `mouse':
+  use based on the following rules:
+</p>
+<ul>
+  <li> If the edit point is `mouse', then
     <ul>
-     <li>if the mouse is over a selected region, or no region, use all selected regions.</li>
+     <li>if the mouse is over a selected region, or no region, use all selected
+     regions, or</li>
      <li>if the mouse is over an unselected region, use just that region.</li>
     </ul>
   </li>
   <li> For all other edit points
     <ul>
       <li>
-        use the selected regions <strong>and</strong> those that are both
-        under the edit position <strong>and</strong> on a selected track, 
+        use the selected regions <em>and</em> those that are both
+        under the edit position <em>and</em> on a selected track, 
         or on a track which is in the same active edit-enabled route group
         as a selected region.
       </li>
     </ul>
   </li>
-</ol>
-<p>The rationale here for the two different rules is that the mouse edit point is special in that its position indicates both a time and a track; the other edit points (Playhead,Marker) indicates only a time.</p>
+</ul>
+<p>
+  The rationale here for the two different rules is that the mouse edit point 
+  is special in that its position indicates both a time and a track; the other 
+  edit points (Playhead,Marker) indicate a time only.
+</p>