X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Funderstanding-playlists.html;h=4bec177d27b2b81a5af06082c1b8f2ac7206f607;hb=7ab6bbbc7b588b46a4ee9c80709fbb09756f1a18;hp=a056716e3faf37b8dfa6579f8ac0f5e9ba8f0fbd;hpb=764a7768616c7dd4c57c63d3afc7673d9900c662;p=ardour-manual

diff --git a/include/understanding-playlists.html b/include/understanding-playlists.html
index a056716..4bec177 100644
--- a/include/understanding-playlists.html
+++ b/include/understanding-playlists.html
@@ -35,7 +35,7 @@
   time, and tracks can even share playlists.
 </p>
 <p>
-  Some other <abbr title="Digital Audio Workstation">DAW</abbr>s, us the term
+  Some other <abbr title="Digital Audio Workstation">DAW</abbr>s use the term
   <dfn>"virtual track"</dfn> to define a track that isn't actually playing or
   doing anything, but can be mapped/assigned to a real track. This concept is
   functionally identical to Ardour's playlists. We just like to be little more
@@ -48,7 +48,7 @@
   One thing to bear in mind is that playlists are cheap. They
   do not cost anything in terms of CPU consumption, and they have very
   minimal efforts on memory use. So generating new playlists whenever needed
-  is recommendable. They are not equivalent to tracks,
+  is recommended. They are not equivalent to tracks,
   which require extra CPU time and significant memory space, or audio
   files, which use disk space, or plugins that require extra CPU time.
   If a playlist is not in use, it occupies a small amount of memory, and