X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Flayering-display.html;h=9b0198ea5d8040b16887a8686d30fbf3a26799bc;hb=d1339ef8a461372e6abf8bbfd918cbbc0c65c903;hp=14be09ccdf4f75cf9360f0b7ec93c91a7872564f;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual

diff --git a/include/layering-display.html b/include/layering-display.html
index 14be09c..9b0198e 100644
--- a/include/layering-display.html
+++ b/include/layering-display.html
@@ -7,17 +7,17 @@ alt="Track layering menu" />
   <dfn>overlaid</dfn> in the editor window, to save vertical space.
 </p>
 <p>
-  However, this display mode can be confusing for tracks with many overdubs, 
-  because its not obvious in which order the overdubs are layered. Although 
+  However, this display mode can be confusing for tracks with many overdubs,
+  because its not obvious in which order the overdubs are layered. Although
   there are other methods of moving particular regions to the top of an
   overlapping set, and although Ardour also has playlists to let you manage
-  <a href="/working-with-playlists/playlist_usecases/">takes</a> a bit more 
-  efficiently than just continually layering, 
-  there are times when being able to clearly see all regions in a track without 
-  any overlaps is reassuring and useful. 
+  <a href="@@playlist-usecases">takes</a> a bit more
+  efficiently than just continually layering,
+  there are times when being able to clearly see all regions in a track without
+  any overlaps is reassuring and useful.
 </p>
 <p>
-  Here is an image of a track with a rather drastic overdub situation, 
+  Here is an image of a track with a rather drastic overdub situation,
   viewed in normal <dfn>overlaid mode</dfn>:
 </p>
 <img src="/images/a3_overlaps_layered.png" alt="overlapping regions in overlaid mode" />
@@ -29,13 +29,13 @@ alt="Track layering menu" />
 </p>
 <img src="/images/a3_layers_stacked.png" alt="overlapping regions in stacked mode" />
 <p>
-  You can still move regions around as usual, and in fact you can 
-  even drag them so that they overlay each again, but when you 
-  release the mouse button, things will flip back to them all being 
-  stacked cleanly. The number of <dfn>lanes</dfn> for the track is determined by 
-  the maximum number of regions existing in any one spot throughout 
-  the track, so if you have really stacked up 10 overdubs in one spot, 
-  you'll end up with 10 lanes. Obviously, using a large track height 
+  You can still move regions around as usual, and in fact you can
+  even drag them so that they overlay each again, but when you
+  release the mouse button, things will flip back to them all being
+  stacked cleanly. The number of <dfn>lanes</dfn> for the track is determined by
+  the maximum number of regions existing in any one spot throughout
+  the track, so if you have really stacked up 10 overdubs in one spot,
+  you'll end up with 10 lanes. Obviously, using a large track height
   works much better for this than a small one.
 </p>