Skip to content

Commit d4f117e

Browse files
committed
Hyphenation fixes
1 parent ffc8be5 commit d4f117e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/ext-pqc/api/mlkem.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ The |API| supports Module Lattice-based key ecapsulation (ML-KEM) as defined in
131131
Module Lattice-based key-encapsulation algorithm
132132
------------------------------------------------
133133

134-
The ML-KEM key encapsulation mechanism is defined in :cite-title:`FIPS203`.
134+
ML-KEM is defined in :cite-title:`FIPS203`.
135135
ML-KEM has three parameter sets which provide differing security strengths.
136136

137137
The generation of an ML-KEM key depends on the full parameter specification.
@@ -143,7 +143,7 @@ See `[FIPS203]` §8 for details on the parameter sets.
143143
:definition: ((psa_algorithm_t)0x0c000200)
144144

145145
.. summary::
146-
Module Lattice-based key encapsulation mechanism (ML-KEM).
146+
Module Lattice-based key-encapsulation mechanism (ML-KEM).
147147

148148
This is the ML-KEM key-encapsulation algorithm, defined by `[FIPS203]`.
149149
ML-KEM requires an ML-KEM key, which determines the ML-KEM parameter set for the operation.
@@ -160,7 +160,7 @@ See `[FIPS203]` §8 for details on the parameter sets.
160160
ML-KEM-1024, 1568
161161

162162
The 32-byte shared output key that is produced by ML-KEM is pseudorandom.
163-
Although it can be used directly as an encryption key, it is recommended to use the output key as an input to a key derivation operation to produce additional cryptographic keys.
163+
Although it can be used directly as an encryption key, it is recommended to use the output key as an input to a key-derivation operation to produce additional cryptographic keys.
164164

165165
.. subsection:: Compatible key types
166166

0 commit comments

Comments
 (0)