From 118921d28b929918365d484ae796c7584c45f8a3 Mon Sep 17 00:00:00 2001 From: Nikos Mavrogiannopoulos Date: Sun, 22 Apr 2018 16:02:08 +0200 Subject: gnutls.h.in: corrected typo [ci skip] Signed-off-by: Nikos Mavrogiannopoulos --- lib/includes/gnutls/gnutls.h.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/includes/gnutls/gnutls.h.in b/lib/includes/gnutls/gnutls.h.in index cf7c61866c..139355b0cb 100644 --- a/lib/includes/gnutls/gnutls.h.in +++ b/lib/includes/gnutls/gnutls.h.in @@ -361,12 +361,12 @@ typedef enum { * @GNUTLS_ENABLE_FALSE_START: Enable the TLS false start on client side if the negotiated ciphersuites allow it. This will enable sending data prior to the handshake being complete, and may introduce a risk of crypto failure when combined with certain key exchanged; for that GnuTLS may not enable that option in ciphersuites that are known to be not safe for false start. Since 3.5.0. * @GNUTLS_FORCE_CLIENT_CERT: When in client side and only a single cert is specified, send that certificate irrespective of the issuers expected by the server. Since 3.5.0. * @GNUTLS_NO_TICKETS: Flag to indicate that the session should not use resumption with session tickets. - * @GNUTLS_KEY_SHARE_TOP3: Generate key shared for the top-3 different groups which are enabled. + * @GNUTLS_KEY_SHARE_TOP3: Generate key shares for the top-3 different groups which are enabled. * That is, as each group is associated with a key type (EC, finite field, x25519), generate * three keys using %GNUTLS_PK_DH, %GNUTLS_PK_EC, %GNUTLS_PK_ECDH_X25519 if all of them are enabled. - * @GNUTLS_KEY_SHARE_TOP2: Generate key shared for the top-2 different groups which are enabled. + * @GNUTLS_KEY_SHARE_TOP2: Generate key shares for the top-2 different groups which are enabled. * For example (ECDH + x25519). This is the default. - * @GNUTLS_KEY_SHARE_TOP: Generate key shared for the first group which is enabled. + * @GNUTLS_KEY_SHARE_TOP: Generate key share for the first group which is enabled. * For example x25519. This option is the most performant for client (less CPU spent * generating keys), but if the server doesn't support the advertized option it may * result to more roundtrips needed to discover the server's choice. -- cgit v1.2.1