From 1a95e913c7163dd770c9b2f83ea5f995bafa4aaa Mon Sep 17 00:00:00 2001
From: Xi Ruoyao <xry111@xry111.site>
Date: Sat, 28 May 2022 21:04:22 +0800
Subject: [PATCH] openssl: reword upgrading note for versioning scheme change

---
 chapter08/openssl.xml | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/chapter08/openssl.xml b/chapter08/openssl.xml
index cece1904f..044c715a4 100644
--- a/chapter08/openssl.xml
+++ b/chapter08/openssl.xml
@@ -81,12 +81,15 @@ make MANSUFFIX=ssl install</userinput></screen>
     <note>
       <para>
         You should update OpenSSL when a new version which fixes vulnerabilities
-        is announced. The releases run in series, with a letter for each release
-        after the initial release (e.g. 1.1.1, 1.1.1a, 1.1.1b, etc). Because LFS
-        installs only the shared libraries, there is no need to recompile packages
-        which link to <filename class="libraryfile">libcrypto.so</filename> or
+        is announced.  Since OpenSSL 3.0.0, the OpenSSL versioning scheme
+        follows the MAJOR.MINOR.PATCH format.  API/ABI compatibility
+        are guaranteed for the same MAJOR version number.  Because LFS
+        installs only the shared libraries, there is no need to recompile
+        packages which link to
+        <filename class="libraryfile">libcrypto.so</filename> or
         <filename class="libraryfile">libssl.so</filename>
-        <emphasis>when upgrading in the same series.</emphasis>
+        <emphasis>when upgrading to a version with MAJOR version number
+        unchanged</emphasis>.
       </para>
 
       <para>