From 61aa74fb3d37382475e90ba584bacab13d66038e Mon Sep 17 00:00:00 2001
From: k-stachowiak <krzysiek.stachowiak@gmail.com>
Date: Tue, 5 Feb 2019 16:49:33 +0100
Subject: [PATCH] Fix typos and miswording in the mbedtls_ssl_conf_max_frag_len
 documentation comment

---
 include/mbedtls/ssl.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/mbedtls/ssl.h b/include/mbedtls/ssl.h
index 86ada47dde..07ecba7d45 100644
--- a/include/mbedtls/ssl.h
+++ b/include/mbedtls/ssl.h
@@ -2762,10 +2762,10 @@ void mbedtls_ssl_conf_cert_req_ca_list( mbedtls_ssl_config *conf,
  *                 (Client: set maximum fragment length to emit *and*
  *                 negotiate with the server during handshake)
  *
- * \note           By default the \c mfl_code field ofthe \c mbedtls_ssl_config
- *                 structure is equal `0 == MBEDTLS_SSL_MAX_FRAG_LEN_NONE`.
- *                 This means the max fragment length extension *will not* be
- *                 used unless set to other value via this function.
+ * \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.
  *
  * \note           With TLS, this currently only affects ApplicationData (sent
  *                 with \c mbedtls_ssl_read()), not handshake messages.