OSC added some ids to take reader directly to relevant info

[ardour-manual] / include / using-windows-vst-plugins-on-linux.html

diff --git a/include/using-windows-vst-plugins-on-linux.html b/include/using-windows-vst-plugins-on-linux.html
index 25ae2f48b5e3599c481f5c389eb97459b68f1118..628617e5adc12a76bcb5ab45209dd1c268070539 100644 (file)
--- a/include/using-windows-vst-plugins-on-linux.html
+++ b/include/using-windows-vst-plugins-on-linux.html
@@ -4,8 +4,7 @@
   Davis and a few other developers, it is possible to use Windows
   <dfn><abbr title="Virtual Studio Technology">VST</abbr>
   plugins</dfn> (that is, plugins in VST format built and distributed
-  for the Windows platforms) on Ardour running on Linux. (Note: there
-  is no VST support of any kind on OS X).
+  for the Windows platforms) on Ardour running on Linux.
 </p>
 
 <p>However, doing so has three <em>substantial</em> downsides:</p>
@@ -32,7 +31,7 @@
   Step back and think about what "using Windows VSTs" really means:
   taking bits of software written with only one idea in mind&mdash;running
   on the Windows platform&mdash;and then trying to use them on an entirely
-  different platform. It is a bit of a miracle (largely thanks to the
+  different platform. It is a bit of a miracle (thanks largely to the
   incredible work done by the Wine project) that it works at all. But is
   this the basis of a stable, reliable DAW for a non-Windows platform?
   Getting Ardour on Linux to pretend that its really a Windows