From c7f325437990e8a7737bc2cec0f57cdce409f300 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20P=C3=A9gouri=C3=A9-Gonnard?= Date: Thu, 10 Feb 2022 13:00:33 +0100 Subject: [PATCH] Clarify a sentence MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Manuel Pégourié-Gonnard --- docs/architecture/psa-migration/psa-limitations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/psa-migration/psa-limitations.md b/docs/architecture/psa-migration/psa-limitations.md index 915922d02f..45c78063fd 100644 --- a/docs/architecture/psa-migration/psa-limitations.md +++ b/docs/architecture/psa-migration/psa-limitations.md @@ -53,8 +53,8 @@ extension. In TLS 1.3 the situation will be simpler: named groups are the only option, so the current PSA Crypto API is a good match for that. (Not -coincidentally, the groups used by RFC 7919 and TLS 1.3 are part those defined -in the specification.) +coincidentally, all the groups used by RFC 7919 and TLS 1.3 are included +in the PSA specification.) There are several options here: