remove more outdated docs

Author: JesusMcCloud

README.md

@@ -43,8 +43,6 @@ action!
 * Generic ASN.1 abstractions to operate on and create arbitrary ASN.1 Data
 * JOSE-related data structures (JSON Web Keys, JWT, etc…)
 * COSE-related data structures (COSE Keys, CWT, etc…)
-* Serializability of all ASN.1 classes for debugging **and only for debugging!!!** *Seriously, do not try to deserialize
-  ASN.1 classes through kotlinx.serialization! Use `decodeFromDer()` and its companions!*
 * 100% pure Kotlin BitSet
 * Exposes Multibase Encoder/Decoder as an API dependency including [Matthew Nelson's smashing Base16, Base32, and Base64 encoders](https://github.com/05nelsonm/encoding)
 * **ASN.1 Parser and Encoder including a DSL to generate ASN.1 structures**
@@ -113,14 +111,14 @@ certificates, CSRs, as well as COSE and JOSE data. Hence, we needed a fully-feat
 X.509 to COSE and JOSE datatypes. We required comprehensive ASN.1 introspection and builder capabilities across platforms.
 Most notably, Apple has been notoriously lacking anything even remotely usable
 and [SwiftASN1](https://github.com/apple/swift-asn1) was out of the question for a couple of reasons.
-Most notably, it did not exist, when we started work on Signum. Hence, there was **neither ASN.1 parser, nor encoder on Apple platforms**
-that was actually usable. In effect: there way no KMP ASN.1 codec in sight, much less a type-safe, user-friendly one.
+Most notably, it did not exist when we started work on Signum. Hence, there was **neither ASN.1 parser, nor encoder on Apple platforms**
+that was actually usable. In effect: there was no KMP ASN.1 codec in sight, much less a type-safe, user-friendly one.
 As it stands now, our ASN.1 engine can handle almost anything you throw at it, in some areas even exceeding Bouncy Castle!
 cryptography-kotlin only added basic ASN.1 capabilities over a year after Signum's development started.
 <br>
 We are also unaware of any other library offering comprehensive JOSE and COSE data structures based on kotlinx-serialization.
 Hence, we implemented those ourselves, with first-class interop to our generic cryptographic data structures.
-We also support platform-native interop meaning that you can easily convert a Json Web Key to a JCA key or even a `SecKeyRef`.
+We also support platform-native interop meaning that you can easily convert a Json Web Key to a JCA key or even a `SecKeyRef` on iOS.
 
 Having actual implementations of cryptographic operations available was only second on our list of priorities. From the
 get-go, it was clear that we wanted the tightest possible platform integration on Android and iOS, including hardware-backed

docs/docs/index.md

@@ -32,8 +32,6 @@ types and platform-native functionality related to crypto and PKI applications:
 * Generic ASN.1 abstractions to operate on and create arbitrary ASN.1 Data
 * JOSE-related data structures (JSON Web Keys, JWT, etc…)
 * COSE-related data structures (COSE Keys, CWT, etc…)
-* Serializability of all ASN.1 classes for debugging **and only for debugging!!!** *Seriously, do not try to deserialize
-  ASN.1 classes through kotlinx.serialization! Use `decodeFromDer()` and its companions!*
 * 100% pure Kotlin BitSet
 * Exposes Multibase Encoder/Decoder as an API dependency
   including [Matthew Nelson's smashing Base16, Base32, and Base64 encoders](https://github.com/05nelsonm/encoding)
@@ -104,14 +102,14 @@ and comprehensive ASN.1, JOSE, and COSE support.
     X.509 to COSE and JOSE datatypes. We required comprehensive ASN.1 introspection and builder capabilities across platforms.
     Most notably, Apple has been notoriously lacking anything even remotely usable
     and [SwiftASN1](https://github.com/apple/swift-asn1) was out of the question for a couple of reasons.
-    Most notably, it did not exist, when we started work on Signum. Hence, there was **neither ASN.1 parser, nor encoder on Apple platforms**
-    that was actually usable. In effect: there way no KMP ASN.1 codec in sight, much less a type-safe, user-friendly one.
+    Most notably, it did not exist when we started work on Signum. Hence, there was **neither ASN.1 parser, nor encoder on Apple platforms**
+    that was actually usable. In effect: there was no KMP ASN.1 codec in sight, much less a type-safe, user-friendly one.
     As it stands now, our ASN.1 engine can handle almost anything you throw at it, in some areas even exceeding Bouncy Castle!
     cryptography-kotlin only added basic ASN.1 capabilities over a year after Signum's development started.
     <br>
     We are also unaware of any other library offering comprehensive JOSE and COSE data structures based on kotlinx-serialization.
     Hence, we implemented those ourselves, with first-class interop to our generic cryptographic data structures.
-    We also support platform-native interop meaning that you can easily convert a Json Web Key to a JCA key or even a `SecKeyRef`.
+    We also support platform-native interop meaning that you can easily convert a Json Web Key to a JCA key or even a `SecKeyRef` on iOS.
 
     Having actual implementations of cryptographic operations available was only second on our list of priorities. From the
     get-go, it was clear that we wanted the tightest possible platform integration on Android and iOS, including hardware-backed

docs/docs/indispensable.md

@@ -187,8 +187,6 @@ The following section provides more details on the various patterns used for ASN
 As mentioned before, classes like `CryptoPublicKey`, `X509Certificate`, and `ObjectIdentifier` all implement `Asn1Encodable`
 while their companions implement `Asn1Decodable`.
 These interfaces essentially provide a mapping between custom types and low-level TLV structures that can directly be encoded, conforming to DER.
-This also means, a direct serialization of such custom types is valuable for debugging, but not for encoding.
-**Hence, decoding a kotlinx.serialization output of those classes is unsupported.**
 
 In addition, `CryptoPublicKey`, `CryptoPrivateKey`, `X509Certificate`, `Pkcs10CertificationRequest` also implement `PemEncodable`,
 while their respective companions implement `PemDecodable`.