diff --git a/configure.ac b/configure.ac
index 5de936a..630dc4a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -10,49 +10,50 @@ AM_INIT_AUTOMAKE([subdir-objects])
 dnl Note by ts A71207:
 dnl
 dnl BURN_MICRO_VERSION is _not_ the third component Z of libburn-X.Y.Z
-dnl but an eternal counter which leads to SONAME. This misunderstanding
-dnl caused a messed up sequence of SONAMEs.
+dnl but an eternal counter which leads to CURRENT. This misunderstanding
+dnl caused a messed up sequence of CURRENTs.
 dnl
-dnl SONAME and AGE describe the binary compatibility interval of a
-dnl dynamic library. See also http://www.gnu.org/software/libtool/manual.html
+dnl CURRENT and AGE describe the binary compatibility interval of a
+dnl dynamic library.
+dnl See also http://www.gnu.org/software/libtool/manual.html#Interfaces
 dnl
-dnl The name of the library will be libburn.so.$SONAME.$REV.$AGE
+dnl The name of the library will be libburn.so.$CURRENT-$AGE.$AGE.$REV
 dnl In the terminology of this file:
-dnl   SONAME= LT_CURRENT
-dnl   REV   = LT_REVISION
-dnle  AGE   = LT_AGE
+dnl   CURRENT = LT_CURRENT
+dnl   REV     = LT_REVISION
+dnle  AGE     = LT_AGE
 dnl
-dnl In the past the following SONAMEs of libburn have been released.
+dnl In the past the following CURRENTs of libburn have been released.
 dnl All with AGE=0.
 dnl  0.2.2 = 2 , 0.2.3 = 3 , 0.2.6 = 6
 dnl  0.3.0 = 0 , 0.3.2 = 2 , 0.3.4 = 4 . 0.3.6 = 6 , 0.3.8 = 4
-dnl  0.4.0 = 4
+dnl  0.4.0 = 0
 dnl 
 dnl Beginning with libburn-0.4.1 a rectified counting was introduced as
-dnl   SONAME=10, REV=1, AGE=6
+dnl   CURRENT=10, REV=1, AGE=6
 dnl This rectification declared the current version
 dnl to be binary compatible down to libburn-0.3.4.
 dnl Real backward compatibility is given down to libburn-0.3.2.
-dnl Beware of libburn-0.2.6 which had SONAME=6.
+dnl Beware of libburn-0.2.6 which had CURRENT=6.
 dnl
-dnl SONAME=10, REV=0, AGE=6 would be appropriate for libburn-0.4.0
+dnl CURRENT=10, REV=0, AGE=6 would be appropriate for libburn-0.4.0
 dnl but was not issued, regreattably.
 dnl
-dnl If libburn-0.4.0 gets patched, its SONAME will become 10, AGE 6, and
-dnl REV will be set to one higher than the highest REV of SONAME 10.
-dnl If libburn-0.4.1 is still on SONAME 10 then its REV gets set one higher
+dnl If libburn-0.4.0 gets patched, its CURRENT will become 10, AGE 6, and
+dnl REV will be set to one higher than the highest REV of CURRENT 10.
+dnl If libburn-0.4.1 is still on CURRENT 10 then its REV gets set one higher
 dnl than that.
 dnl As soon as 0.4.1 becomes upwardly incompatible, it shall become 11,0,7.
 dnl From then on it counts REV independently of libburn-0.4.0.
 dnl Whether 0.4.1 alters independent REV at all, is not decided yet.
-dnl It may well stay 0 until a release version joins SONAME 11.
+dnl It may well stay 0 until a release version joins CURRENT 11.
 dnl
 dnl Under the preconditions
-dnl   SONAME= $BURN_MICRO_VERSION - $BURN_INTERFACE_AGE
-dnl   REV=    $BURN_INTERFACE_AGE
-dnl   AGE=    $BURN_BINARY_AGE
+dnl   CURRENT= $BURN_MICRO_VERSION - $BURN_INTERFACE_AGE
+dnl   REV=     $BURN_INTERFACE_AGE
+dnl   AGE=     $BURN_BINARY_AGE
 dnl the following old instructions were reasonable. Their drawback
-dnl is that they cause large jumps in SONAME, when BURN_INTERFACE_AGE gets
+dnl is that they cause large jumps in CURRENT, when BURN_INTERFACE_AGE gets
 dnl reset to 0 from a high value. So this is outdated now:
 dnl ---------------------------------------------------------------------------
 dnl .Making releases: