From db850c63b2db10fc437c2095a9d7d9a4acd99147 Mon Sep 17 00:00:00 2001
From: k-stachowiak <krzysiek.stachowiak@gmail.com>
Date: Wed, 6 Feb 2019 12:51:45 +0100
Subject: [PATCH] Reword ssl_conf_max_frag_len documentation

---
 include/mbedtls/ssl.h | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/include/mbedtls/ssl.h b/include/mbedtls/ssl.h
index 07ecba7d4..ba3592a05 100644
--- a/include/mbedtls/ssl.h
+++ b/include/mbedtls/ssl.h
@@ -2764,8 +2764,9 @@ void mbedtls_ssl_conf_cert_req_ca_list( mbedtls_ssl_config *conf,
  *
  * \note           By default the \c mfl_code field of the \c mbedtls_ssl_config
  *                 structure is equal to `0 == MBEDTLS_SSL_MAX_FRAG_LEN_NONE`.
- *                 This means the maximum fragment length extension *will not*
- *                 be used unless set to another value via this function.
+ *                 Therefore, the maximum fragment length extension *will not*
+ *                 be used, unless the maximum fragment length has been set to a
+ *                 different value via this function.
  *
  * \note           With TLS, this currently only affects ApplicationData (sent
  *                 with \c mbedtls_ssl_read()), not handshake messages.