Update documentation for ML-KEM

Change-Id: Ia812327af10235de099f5ed2e5dfc6586a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/94167
Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Lily Chen <chlily@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>

include/openssl/evp.h

diff --git a/include/openssl/evp.h b/include/openssl/evp.h
index b156dfa..08d24c3 100644
--- a/include/openssl/evp.h
+++ b/include/openssl/evp.h
@@ -396,6 +396,10 @@
 //   APIs, but instead the |EVP_PKEY_from_private_seed| and
 //   |EVP_PKEY_get_private_seed| APIs.
 //
+// - ML-KEM, using the formats in FIPS 203. The private key representation
+//   supported by BoringSSL is the 64-byte "seed" resulting from the
+//   concatenation of d||z, as each is defined in FIPS 203.
+//
 // These formats are suitable if serializing a key in a context where the
 // algorithm is already known and there is no need to encode it.
 

include/openssl/mlkem.h

diff --git a/include/openssl/mlkem.h b/include/openssl/mlkem.h
index 56edc16..65b4e90 100644
--- a/include/openssl/mlkem.h
+++ b/include/openssl/mlkem.h
@@ -25,7 +25,7 @@
 // ML-KEM-768.
 //
 // This implements the Module-Lattice-Based Key-Encapsulation Mechanism from
-// https://csrc.nist.gov/pubs/fips/204/final
+// https://csrc.nist.gov/pubs/fips/203/final
 
 
 // MLKEM768_public_key contains an ML-KEM-768 public key. The contents of this