From 3bc90d82e363019d7026a9ffbbd46f2fa459dc9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Sun, 30 Jan 2022 23:44:34 +0100 Subject: [PATCH] doc: improve wording surrounding TLS 1.3 ciphers Spelling out numbers makes this part easier to read. Also remove the unnecessary word 'last'. --- doc/api/tls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/tls.md b/doc/api/tls.md index 24c7ea742808b9..f2142b63059efa 100644 --- a/doc/api/tls.md +++ b/doc/api/tls.md @@ -357,7 +357,7 @@ the default configuration. If these clients _must_ be supported, the [TLS recommendations][] may offer a compatible cipher suite. For more details on the format, see the OpenSSL [cipher list format][] documentation. -There are only 5 TLSv1.3 cipher suites: +There are only five TLSv1.3 cipher suites: * `'TLS_AES_256_GCM_SHA384'` * `'TLS_CHACHA20_POLY1305_SHA256'` @@ -365,7 +365,7 @@ There are only 5 TLSv1.3 cipher suites: * `'TLS_AES_128_CCM_SHA256'` * `'TLS_AES_128_CCM_8_SHA256'` -The first 3 are enabled by default. The last 2 `CCM`-based suites are supported +The first three are enabled by default. The two `CCM`-based suites are supported by TLSv1.3 because they may be more performant on constrained systems, but they are not enabled by default since they offer less security.