fix: link fixes

Author: ronaldtse

_posts/2018-08-20-rnp-010-released.adoc

@@ -190,7 +190,7 @@ RNP supports a comprehensive set of public-key algorithms:
 * https://en.wikipedia.org/wiki/Digital_Signature_Algorithm[DSA] - The Digital Signature Algorithm, including support for key sizes beyond 1024 bits (DSA2)
 * https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm[ECDSA]/ECDH - Elliptic curve cryptography offering strong security with shorter key lengths
 * https://en.wikipedia.org/wiki/EdDSA[EdDSA] - Modern elliptic curve signatures providing high security and performance
-* https://en.wikipedia.org/wiki/SM2_(cryptography)[SM2] - The Chinese national standard for public-key cryptography, essential for Chinese market compliance
+* https://datatracker.ietf.org/doc/html/draft-openpgp-oscca-02[SM2] - The Chinese national standard for public-key cryptography, essential for Chinese market compliance
 
 
 == Summary

_posts/2021-04-05-rnp-release-0-15.adoc

@@ -51,7 +51,7 @@ A major enhancement to the build system enables offline builds:
 
 * New https://cmake.org[CMake] options for building without external downloads:
 ** https://github.com/google/googletest[Googletest] can be skipped during build
-** https://github.com/rnpgg/ruby-rnp[ruby-rnp] can be skipped during build
+** https://github.com/rnpgp/ruby-rnp[ruby-rnp] can be skipped during build
 * Better support for air-gapped environments
 * Improved build reproducibility
 

_posts/2022-09-06-rnp-release-0-16-1.adoc

@@ -18,9 +18,9 @@ flexibility, and platform support.
 == Introduction
 
 The release marks a major milestone in RNP's evolution with comprehensive
-support for https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[OpenSSL
-3.0], enabling seamless integration with the latest enterprise Linux
-distributions.
+support for
+https://openssl-library.org/news/openssl-3.0-notes/[OpenSSL 3.0], enabling
+seamless integration with the latest enterprise Linux distributions.
 
 Additionally, it introduces more nuanced security policies and several
 user-requested features that improve flexibility and ease of use.
@@ -44,7 +44,7 @@ Other highlights:
 
 === OpenSSL 3.0 compatibility
 
-https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[OpenSSL 3.0] has
+https://openssl-library.org/news/openssl-3.0-notes/[OpenSSL 3.0] has
 been recently released and RNP 0.16.1 is the only OpenPGP implementation that
 fully supports it.
 

_posts/2023-05-01-rnp-release-0-17-0.adoc

@@ -35,7 +35,7 @@ Key highlights:
 
 Other highlights:
 
-* SExp parsing code moved to a separate library
+* SExp parsing code moved to a separate library (https://github.com/rnpgp/sexpp[SEXPP])
 * New FFI capabilities for signature export and key verification
 * Enhanced CLI features for key management and encryption
 * Configurable compile-time options for legacy algorithm support
@@ -100,9 +100,12 @@ is crucial
 === GnuPG 2.3+ compatibility
 
 This release adds support for modern key storage formats used by GnuPG 2.3 and
-later versions. The new format, based on
-https://people.csail.mit.edu/rivest/Sexp.txt[S-expressions], provides a more
-structured and extensible way to store OpenPGP keys and their metadata.
+later versions, described in its https://github.com/gpg/gnupg/blob/master/agent/keyformat.txt[specification].
+
+The new format, based on S-Expressions (SExp)
+(https://web.archive.org/web/20071017100533/http://people.csail.mit.edu/rivest/Sexp.txt[original specification from 1997]),
+provides a more structured and extensible way to store OpenPGP keys and their
+metadata.
 
 RNP can now read and write keys in this format, ensuring smooth interoperability
 with recent GnuPG versions. This is particularly important for users and
@@ -155,14 +158,15 @@ Users can expect:
 
 == Developer improvements
 
-=== SExp library separation
+=== S-Expression library separation to SEXPP
+
+S-Expressions (SExp), was originally defined in a
+(https://web.archive.org/web/20071017100533/http://people.csail.mit.edu/rivest/Sexp.txt[specification from 1997]),
+that provides a structured format for storing cryptographic data. This format is
+oft-used in security applications, including GnuPG's modern key storage system.
 
-The https://github.com/rnpgp/sexp[SExp] parsing library, essential for handling
-GnuPG key storage, has been moved to a separate repository. S-expressions,
-originally defined in a https://people.csail.mit.edu/rivest/Sexp.txt[1997 spec
-by Ron Rivest], provide a structured format for storing cryptographic data. This
-format is widely used in security applications, including GnuPG's modern key
-storage system.
+The RNP team has created a reusable C++ Library for working with SEXP data called
+https://github.com/rnpgp/sexpp[SEXPP].
 
 By separating the SExp parsing code into its own library, RNP achieves better
 code organization and enables other projects to benefit from this
@@ -172,8 +176,9 @@ with GnuPG keys or other cryptographic data storage.
 
 The separation also simplifies RNP's core codebase while maintaining full
 compatibility with GnuPG 2.3+ key storage formats through this dedicated
-component. Users and developers can expect better maintainability and easier
-updates to the S-expression handling code.
+component. Users and developers can expect better maintainability, easier
+updates to the S-expression handling code, and improved performance during
+cryptographic operations.
 
 
 This modularization: