diff --git a/components/mbedtls/Kconfig b/components/mbedtls/Kconfig
index 22cc25a92482..2f5328b8076a 100644
--- a/components/mbedtls/Kconfig
+++ b/components/mbedtls/Kconfig
@@ -85,8 +85,13 @@ menu "mbedTLS"
         range 512 16384
         depends on MBEDTLS_ASYMMETRIC_CONTENT_LEN
         help
-            This defines maximum incoming fragment length, overriding default
-            maximum content length (MBEDTLS_SSL_MAX_CONTENT_LEN).
+            This defines the maximum incoming fragment length, overriding the default
+            maximum content length (MBEDTLS_SSL_MAX_CONTENT_LEN). The default value is
+            set to 16 KB as recommended by mbedTLS for secure handling of incoming messages.
+
+            Note: Setting this value lower than 16 KB may cause memory leaks or 
+            unexpected behavior when receiving larger fragments, as there is no 
+            mechanism to notify clients of buffer size restrictions. 
 
     config MBEDTLS_SSL_OUT_CONTENT_LEN
         int "TLS maximum outgoing fragment length"
@@ -104,15 +109,16 @@ menu "mbedTLS"
         # Dynamic buffer feature is not supported with DTLS
         depends on !IDF_TARGET_LINUX && !MBEDTLS_SSL_PROTO_DTLS && !MBEDTLS_SSL_VARIABLE_BUFFER_LENGTH
         help
-            Using dynamic TX/RX buffer. After enabling this option, mbedTLS will
-            allocate TX buffer when need to send data and then free it if all data
-            is sent, allocate RX buffer when need to receive data and then free it
-            when all data is used or read by upper layer.
-
-            By default, when SSL is initialized, mbedTLS also allocate TX and
-            RX buffer with the default value of "MBEDTLS_SSL_OUT_CONTENT_LEN" or
-            "MBEDTLS_SSL_IN_CONTENT_LEN", so to save more heap, users can set
-            the options to be an appropriate value.
+            Enable the dynamic TX/RX buffer for mbedTLS. When enabled, mbedTLS will 
+            allocate the TX buffer only when data needs to be sent and free it once 
+            the data is transmitted. Similarly, it will allocate the RX buffer when 
+            receiving data and free it once the data has been fully processed.
+            
+            Caution: For incoming data, the RX buffer size should respect the 
+            minimum size of 16KB, as required by mbedTLS to prevent memory leaks and 
+            ensure proper handling of incoming messages. Reducing the RX buffer 
+            size may cause heap corruption or incomplete message processing if 
+            larger fragments are received.
 
     config MBEDTLS_DYNAMIC_FREE_CONFIG_DATA
         bool "Free private key and DHM data after its usage"
diff --git a/docs/en/api-reference/system/esp_https_ota.rst b/docs/en/api-reference/system/esp_https_ota.rst
index 623959968dde..ed701104f6f7 100644
--- a/docs/en/api-reference/system/esp_https_ota.rst
+++ b/docs/en/api-reference/system/esp_https_ota.rst
@@ -41,11 +41,11 @@ Please refer to :ref:`ESP-TLS: TLS Server Verification <esp_tls_server_verificat
 Partial Image Download over HTTPS
 ---------------------------------
 
-To use the partial image download feature, enable ``partial_http_download`` configuration in ``esp_https_ota_config_t``. When this configuration is enabled, firmware image will be downloaded in multiple HTTP requests of specified sizes. Maximum content length of each request can be specified by setting ``max_http_request_size`` to the required value.
+To use the partial image download feature, enable partial_http_download configuration in esp_https_ota_config_t. When this configuration is enabled, the firmware image will be downloaded in multiple HTTP requests of specified sizes. Maximum content length of each request can be specified by setting max_http_request_size to the required value.
 
-This option is useful while fetching image from a service like AWS S3, where mbedTLS Rx buffer size (:ref:`CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN`) can be set to a lower value which is not possible without enabling this configuration.
+This option is useful while fetching an image from a service like AWS S3, where the mbedTLS RX buffer size (:ref:CONFIG_MBEDTLS_SSL_IN_CONTENT_LEN) can be set to a lower value. However, note that reducing the buffer size below 16 KB may lead to memory leaks or unexpected behavior if the incoming fragment size exceeds the RX buffer capacity, as mbedTLS requires a minimum of 16KB for the RX buffer to ensure proper handling of incoming messages.
 
-Default value of mbedTLS Rx buffer size is set to 16 KB. By using ``partial_http_download`` with ``max_http_request_size`` of 4 KB, size of mbedTLS Rx buffer can be reduced to 4 KB. With this configuration, memory saving of around 12 KB is expected.
+By default, the mbedTLS RX buffer size is set to 16 KB. If the partial_http_download feature is used with a max_http_request_size of 4 KB, the RX buffer size can be reduced accordingly, but caution should be taken when using smaller buffer sizes.
 
 
 Signature Verification