diff options
author | David Bryant <davidbryant@gvtc.com> | 2022-12-06 14:45:38 -0600 |
---|---|---|
committer | David Bryant <davidbryant@gvtc.com> | 2022-12-06 14:45:38 -0600 |
commit | 5042efcc2f694301ebaae0646a8aacb5eeb1b131 (patch) | |
tree | 189c021c60945e6c9a317dd21265961933ef2255 /chapter08/openssl.xml | |
parent | 67dfc3b3717972e37eaa78b042504ce07c389a3a (diff) |
Fix a grammatical error (subject / verb number). Improve English idiom.
Diffstat (limited to 'chapter08/openssl.xml')
-rw-r--r-- | chapter08/openssl.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter08/openssl.xml b/chapter08/openssl.xml index 901bf985c..bd436d868 100644 --- a/chapter08/openssl.xml +++ b/chapter08/openssl.xml @@ -89,13 +89,13 @@ make MANSUFFIX=ssl install</userinput></screen> You should update OpenSSL when a new version which fixes vulnerabilities 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 + is 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 to a version with MAJOR version number - unchanged</emphasis>. + <emphasis>when upgrading to a version with the same MAJOR version + number</emphasis>. </para> <para> |