Fixes and improvements from review by Robin

diff --git a/include/plugin-manager.html b/include/plugin-manager.html
index e56a62a34324c2e0ea076d24f47f122e9012055e..14c2fe13dea0a917cda7e1033f6f13d20059720d 100644 (file)
--- a/include/plugin-manager.html
+++ b/include/plugin-manager.html
@@ -2,8 +2,7 @@
 <p>
   The <dfn>Plugin Manager</dfn> provides a convenient interface to various
   operations on plugins and is the primary troubleshooting tools when something
-  goes wrong with plugins. It works on both physical plugin files and
-  the plugins index.
+  goes wrong with plugins. It works on both plugin files and the plugins index.
 </p>
 
 <figure class=center>
@@ -14,7 +13,7 @@
 <h2>What is a plugins index?</h2>
 
 <p>
-  For each type of a plugin (e.g. VST3 or LV2) there are pre-configured paths
+  For each type of a plugin (e.g. VST3 or AU) there are pre-configured paths
   where these plugins are located. Every time Ardour runs, it re-scans plugins
   in these paths and recreates an index — a kind of inventory of available
   plugins. Whenever you open the <a href="@@plugin-selector">Plugin Selector</a>
@@ -31,6 +30,12 @@
   plugins.
 </p>
 
+<p>
+  Ardour also treats LV2 plugins slightly differently and scans them on startup
+  unconditionally. You can disable the scanning of VST2, VST3, and AU plugins
+  entirely in the <kbd class="menu">Preferences</kbd> dialog.
+</p>
+
 <h2>Plugins info</h2>
 
 The main part of the Plugin Manager window is the table where all plugins known