Update generated docs

Author: Keyfactor

README.md

@@ -296,47 +296,6 @@ The following examples are intended as **copy/adapt templates**.
   ]
 }
 ```
----
-
-## Signing algorithm selection (ACM PCA)
-
-The gateway supports an optional CAConnection setting `SigningAlgorithm` that controls the **certificate signature algorithm**
-passed to AWS ACM PCA `IssueCertificate`.
-
-- If **not set**, the plugin will **auto-select** a compatible default based on the CA `KeyAlgorithm` returned by
-  `DescribeCertificateAuthority`.
-- If **set**, the plugin validates the value and **rejects incompatible combinations** before calling AWS.
-
-### Valid `SigningAlgorithm` values (AWS PCA)
-
-- RSA family: `SHA256WITHRSA`, `SHA384WITHRSA`, `SHA512WITHRSA`
-- ECDSA family: `SHA256WITHECDSA`, `SHA384WITHECDSA`, `SHA512WITHECDSA`
-- SM2: `SM3WITHSM2`
-- ML-DSA (post-quantum): `ML_DSA_44`, `ML_DSA_65`, `ML_DSA_87`
-
-### Allowed CA key algorithm and signing algorithm combinations
-
-The CA key algorithm is the PCA CA **KeyAlgorithm** (not the subject key in the CSR). The signing algorithm must match the CA key family.
-
-| CA KeyAlgorithm | Allowed SigningAlgorithm values |
-|---|---|
-| `RSA_2048`, `RSA_3072`, `RSA_4096` | `SHA256WITHRSA`, `SHA384WITHRSA`, `SHA512WITHRSA` |
-| `EC_prime256v1`, `EC_secp384r1`, `EC_secp521r1` | `SHA256WITHECDSA`, `SHA384WITHECDSA`, `SHA512WITHECDSA` |
-| `SM2` | `SM3WITHSM2` |
-| `ML_DSA_44` | `ML_DSA_44` |
-| `ML_DSA_65` | `ML_DSA_65` |
-| `ML_DSA_87` | `ML_DSA_87` |
-
-### Auto-selection defaults
-
-When `SigningAlgorithm` is omitted, the plugin selects:
-
-- RSA CAs -> `SHA256WITHRSA`
-- EC P-256 -> `SHA256WITHECDSA`
-- EC P-384 -> `SHA384WITHECDSA`
-- EC P-521 -> `SHA512WITHECDSA`
-- SM2 -> `SM3WITHSM2`
-- ML-DSA -> exact-match (`ML_DSA_44/65/87`)
 
 ---