Less drama as per @x42's suggestion

diff --git a/include/io-plugins.html b/include/io-plugins.html
index 9a9299089b51e0e6f5ae10bbdc34b00294c74464..7e9043ca8453108f945d575be02f83c92094c643 100644 (file)
--- a/include/io-plugins.html
+++ b/include/io-plugins.html
@@ -18,8 +18,8 @@
   The rationale for pre-processing with I/O plugins is that it's a more
   lightweight way to do it as compared to busses. Much of that is because busses
   have automatable parameters such as fader and panner positions, as well as
   The rationale for pre-processing with I/O plugins is that it's a more
   lightweight way to do it as compared to busses. Much of that is because busses
   have automatable parameters such as fader and panner positions, as well as

-  plugins' parameters. Evaluating automation (even when there's none) is
-  expensive in terms of CPU use. However I/O plugins are not automatable, so
+  plugins' parameters. Evaluating parameter automation (even when there's none)
+  adds additional load to the CPU. However I/O plugins are not automatable, so

   there's no evaluation happening. As far as Ardour is concerned, they are
   almost like JACK audio server clients running alongside Ardour.
 </p>
   there's no evaluation happening. As far as Ardour is concerned, they are
   almost like JACK audio server clients running alongside Ardour.
 </p>