docs: Sync the CN transation and EN source

docs/en/api-reference/peripherals/ecdsa.rst

@@ -134,7 +134,6 @@ The ECDSA peripheral in Mbed TLS stack is integrated by overriding the ECDSA sig
 
 For a particular TLS context, additional APIs have been supplied to populate certain fields (e.g., private key ctx) to differentiate routing to hardware. ESP-TLS layer integrates these APIs internally and hence no additional work is required at the application layer. However, for custom use-cases please refer to API details below.
 
-
 API Reference
 -------------
 

docs/en/api-reference/peripherals/i3c_master.rst

@@ -1,3 +1,4 @@
+====================
 I3C master interface
 ====================
 
@@ -501,10 +502,12 @@ Thread Safety
 The following functions of the I3C driver are thread-safe and can be called from different RTOS tasks without additional lock protection:
 
 Factory functions:
+
 - :cpp:func:`i3c_new_master_bus`
 - :cpp:func:`i3c_del_master_bus`
 
 I3C master operation functions (thread safety guaranteed through bus operation signals):
+
 - :cpp:func:`i3c_master_bus_add_i3c_static_device`
 - :cpp:func:`i3c_master_bus_rm_i3c_device`
 - :cpp:func:`i3c_master_i3c_device_transmit`

docs/en/api-reference/system/esp_timer.rst

@@ -216,7 +216,7 @@ The general procedure to create, start, stop, and delete a timer is as follows:
 3. Stop the timer
 
     - To stop the running timer, call the function :cpp:func:`esp_timer_stop`. But it does not guarantee that after this call, the callback will not be running one or more times. To check if the callback is not running after stopping the timer, you can use :cpp:func:`esp_timer_is_active`. Another approach is to use a blocking stop API.
-    - Blocking the timer stop operation until any in-flight callback completes can be done using :cpp:func:`esp_timer_stop_blocking`.
+    - To block the timer stop operation until any in-flight callback completes, use :cpp:func:`esp_timer_stop_blocking`.
 
 4. Delete the timer