Correct busses spelling

[ardour-manual] / include / working-with-plugins.html

diff --git a/include/working-with-plugins.html b/include/working-with-plugins.html
index ca0d6643b79ec11adcf103083a6db19487318a78..cfdfed5ec34d2f8a30722bb4acdc85c0c9717081 100644 (file)
--- a/include/working-with-plugins.html
+++ b/include/working-with-plugins.html
@@ -1,33 +1,20 @@
 
-
-
-<p><dfn>Plugins</dfn> are bits of software that get loaded by Ardour in order to:</p>
+<p>
+  <dfn>Plugins</dfn> are bits of software that get loaded by Ardour in order to:</p>
 <ul>
-  <li>Create various audio or MIDI effects
-  </li>
-  <li>Generate audio by functioning as "software instruments"
-  </li>
+  <li>Create various audio or MIDI effects</li>
+  <li>Generate audio by functioning as "software instruments"</li>
 </ul>
 
-<p>Ardour does not come with any built-in signal processors of its own
-  (other than volume faders) but does ship with a small group of
-  plugins starting at Ardour 5.0. The shipped plugins are listed as authored by "Ardour Team"
-  and named with "a-" as the start of the name (Like a-EQ) or Authored by
-  "Ardour LUA Task Force" in which case they are example (but still useful)
-  LUA scripts. The included plugins are LV2 or LUA scripts and use
-  Ardour's generic GUI. They work on all supported platforms so that
-  projects started on one platform will sound the same on another platform
-  if they use just these plugins or other plugins that
-  are cross platform.
-  They are written by 3rd parties, though we do provide <a href="/working-with-plugins/getting-plugins/">some
-  information on how to get them</a>.
+<p>
+  They are usually written by 3rd parties, though <a href="@@plugins-bundled-with-ardour">a few come as part of a standard Ardour install</a>. The sources for plugins are many and varied; see <a href="@@getting-more-plugins">here</a> for some information on how to get them.
 </p>
 
-<h4>
-Ardour supports a variety of different plugin standards:
-</h4>
-<dl class="narrower-table">
+<p>
+  Ardour supports a variety of different plugin standards:
+</p>
 
+<dl class="narrower-table">
   <dt><abbr title="Linux Audio Developers' Simple Plugin API">LADSPA</abbr></dt>
   <dd>An early, simple, lightweight plugin <abbr title="Application
   Programming Interface">API</abbr>, audio effects only,
@@ -51,17 +38,17 @@ Ardour supports a variety of different plugin standards:
 
   <dt>Windows VST Plugins on Linux</dt>
   <dd>VST plugins for Windows, but being used on Linux. <em>Not
-  supported by normal builds of Ardour. <a href="/working-with-plugins/windows-vst-support/">Read
+  supported by normal builds of Ardour. <a href="@@using-windows-vst-plugins-on-linux">Read
   more&hellip;</a></em>
   </dd>
 </dl>
 
 <h2>Adding/Removing/Copying Plugins</h2>
 
-<p>Within Ardour, plugins are just another type
-of <dfn>Processor</dfn> and so the techniques for
-adding/removing/copying/moving processors apply to plugins as
-well. These techniques are covered on
-the <a href="/working-with-plugins/processor-box/">Processor
-Box</a> page.</p>
+<p>
+  Within Ardour, plugins are just another type of <dfn>Processor</dfn> and so
+  the techniques for adding/removing/copying/moving processors apply to plugins
+  as well. These techniques are covered on the
+  <a href="@@processor-box">Processor Box</a> page.
+</p>