docs: Update CN translation

docs/en/api-reference/protocols/esp_tls.rst

@@ -194,15 +194,15 @@ To use a custom TLS stack in your project, follow these steps:
            // ... create TLS connections as usual using esp_tls_conn_new(), etc. ...
        }
 
-Important Notes
----------------
+.. important::
+
+    * The custom stack must be registered **before** creating any TLS connections. Calling :cpp:func:`esp_tls_register_stack` after TLS connections have been created will not affect existing connections.
+    * The :cpp:type:`esp_tls_stack_ops_t` structure must point to a static/global structure (not on the stack) as it's stored by reference.
+    * Your implementation should store stack-specific context data in the ``priv_ctx`` and ``priv_ssl`` fields of the :cpp:type:`esp_tls_t` structure.
+    * All required function pointers must be non-NULL. Optional functions can be NULL if not supported.
+    * The registration function can only be called once. Subsequent calls will return ``ESP_ERR_INVALID_STATE``.
+    * For detailed function signatures and requirements, see :component_file:`esp-tls/esp_tls_custom_stack.h`.
 
-* The custom stack must be registered before creating any TLS connections. Calling :cpp:func:`esp_tls_register_stack` after TLS connections have been created will not affect existing connections.
-* The :cpp:type:`esp_tls_stack_ops_t` structure must point to a static/global structure (not on the stack) as it's stored by reference.
-* Your implementation should store stack-specific context data in the ``priv_ctx`` and ``priv_ssl`` fields of the :cpp:type:`esp_tls_t` structure.
-* All required function pointers must be non-NULL. Optional functions can be NULL if not supported.
-* The registration function can only be called once. Subsequent calls will return ``ESP_ERR_INVALID_STATE``.
-* For detailed function signatures and requirements, see :component_file:`esp-tls/esp_tls_custom_stack.h`.
 
 ATECC608A (Secure Element) with ESP-TLS
 --------------------------------------------------

docs/en/migration-guides/release-6.x/6.0/protocols.rst

@@ -64,7 +64,7 @@ Removed wolfSSL Support
 The built-in wolfSSL TLS stack support has been removed from ESP-TLS. Users who were using wolfSSL should migrate to either:
 
 1. **mbedTLS (Recommended)**: The default TLS stack, fully integrated and maintained within ESP-IDF.
-2. **Custom TLS Stack**: Register your own TLS implementation using the new custom stack API (see below).
+2. **Custom TLS Stack**: Register your own TLS implementation using the new custom stack API (see Option B below).
 
 **Removed Kconfig Options**
 
@@ -78,13 +78,13 @@ The following Kconfig options have been removed:
 
 If your project was using wolfSSL via ESP-TLS:
 
-1. **Option A - Switch to mbedTLS**:
+1. **Option A - Switch to mbedTLS**
 
    - Remove ``CONFIG_ESP_TLS_USING_WOLFSSL=y`` from your sdkconfig
    - The default ``CONFIG_ESP_TLS_USING_MBEDTLS`` will be used automatically
    - No code changes required for standard TLS operations
 
-2. **Option B - Use Custom Stack API**:
+2. **Option B - Use Custom Stack API**
 
    If you need to continue using wolfSSL or another TLS library, you can register it as a custom stack: