Fixed automation language for modes and states to match UI

[ardour-manual] / include / automation-nomenclature.html

diff --git a/include/automation-nomenclature.html b/include/automation-nomenclature.html
index 264423a3f1e5a1881c5c17f5d8735bd2a0696d05..dc634ee7e21bba1c34266e3613a1492224c0c75e 100644 (file)
--- a/include/automation-nomenclature.html
+++ b/include/automation-nomenclature.html
@@ -1,7 +1,8 @@
 
 <figure class=right>
-<img src="/images/automation-fader1.png">
-<figcaption class=center>An example of a fader automation lane (below) with its associated track (above).</figcaption>
+       <img src="/images/automation-fader1.png" alt="An example of a fader automation lane (below) with its associated track (above).">
+       <figcaption class=center>An example of a fader automation lane (below) with its associated track (above).
+       </figcaption>
 </figure>
 
 <p>
@@ -12,6 +13,7 @@
   trim, etc. <dfn>Automation curves</dfn> consist of lines connected by
   <dfn>control points</dfn>, that live within the confines of a lane; these
   tell Ardour how to change a given parameter over time. <dfn>Automation
-  modes</dfn> govern how a given automation lane will behave during playback.
+       modes</dfn> specify whether the control points are connected by lines or
+       stair steps. <dfn>Automation states</dfn> govern how a given automation lane
+       will behave during playback. 
 </p>
-