Fix typos and miswording in the mbedtls_ssl_conf_max_frag_len documentation comment

This commit is contained in:
k-stachowiak 2019-02-05 16:49:33 +01:00
parent eb1bb3d2d0
commit 61aa74fb3d

View file

@ -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.