Initial work on fixing up Plugins section.

[ardour-manual] / include / working-with-ardour-built-plugin-editors.html

diff --git a/include/working-with-ardour-built-plugin-editors.html b/include/working-with-ardour-built-plugin-editors.html
index 57ad9ba33274249685e61cdbc62b63ee954852ec..41e3fb63f4901371372b9c883a93cff445e6c4ca 100644 (file)
--- a/include/working-with-ardour-built-plugin-editors.html
+++ b/include/working-with-ardour-built-plugin-editors.html
@@ -4,23 +4,26 @@
   <a href="/working-with-plugins/processor-box/">processor box</a>. 
   A new window will appear showing the editor/GUI for the plugin.
 </p>  
+
+<p class=fixme>Add a pic showing the generic GUI</p>
+
 <p>
   If a plugin does not have its own GUI, Ardour will construct a
   <dfn>generic plugin editor</dfn> from a small set of common control 
   elements. Ardour will do this even for plugins that have their 
-  own, if you disable <kbd class="menu">Edit &gt; Preferences &gt; 
-  GUI &gt; Use Plugins' own interface instead of Ardour's</kbd>
+  own, if <kbd class="menu">Edit &gt; Preferences &gt; 
+  GUI &gt; Use Plugins' own interface instead of Ardour's</kbd> is disabled.
 </p>
+
 <p>
-  You can temporarily switch to the generic UI by context-clicking on 
-  a processor and selecting <kbd
-  class="menu">Edit with generic controls</kbd>. This will be necessary to
-  access the <a href="/automation/">plugin automation controls</a>.
+  The generic UI can be temporarily switched to by context-clicking on 
+  a processor and selecting <kbd class="menu">Edit with generic controls</kbd>.
+  This is necessary in order to access the <a href="/automation/">plugin
+  automation controls</a>.
 </p>
+
 <p>
-  In the generic UI, you can re-set any controller to its default by
-  <kbd class="mod3 mouse">Left</kbd>-clicking on it.
+  In the generic UI, any controller can be reset to its default state by
+  <kbd class=mod3n></kbd><kbd class=mouse>Left</kbd>-clicking on it.
 </p>
 
-  
-