Use $disabled{"dynamic-engine"} internally

We were kinda sorta using a mix of $disabled{"static-engine" and
$disabled{"dynamic-engine"} in Configure.  Let's avoid confusion,
choose one of them and stick to it.

Reviewed-by: Rich Salz <rsalz@openssl.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/CHANGES b/CHANGES
index d60d6555a9..66e653e58d 100644
--- a/CHANGES
+++ b/CHANGES
@@ -9,7 +9,7 @@
      only requirement for building dynamic engines is the presence of
      the DSO module, so configuring "disable-dso" will automatically
      disable dynamic engines.  Dynamic engines are enabled by default,
-     and can be disabled with "enable-static-engine".
+     and can be disabled with "disable-dynamic-engine".
      This only applies to the engines in engines/, those in
      crypto/engine/ will always be built into libcrypto (i.e. "static").