docs(ble): Revisied BLE Low Power Giude

(cherry picked from commit 19fc731)

Co-authored-by: Wei Yuhan <weiyuhan@espressif.com>

Author: weiyuhannnn

docs/en/api-guides/low-power-mode/low-power-mode-ble.rst

@@ -101,20 +101,7 @@ Selecting 136 kHz RC Oscillator
 
     - \ (X) Internal 136kHz RC oscillator
 
-    Generally, the 136 kHz RC oscillator cannot meet the accuracy requirement of BLE. It is only suitable for scenarios with low clock accuracy requirements, such as legacy advertising (ADV) or scanning.
-
-    However, for testing purposes, if the peer device also uses 136 kHz RC as the clock source, BLE can function under a 136 kHz RC clock through the following configuration:
-
-    **Configuration Path:**
-
-    ``Component config → Bluetooth → Controller Options``
-
-    **Configuration Options:**
-
-    - \ [*] Enable to set constant peer SCA
-    - \ (3000) Constant peer sleep clock accuracy value
-
-    **Note:** Using the 136 kHz RC oscillator may cause rare issues like connection drops or failures to establish a connection.
+    Generally, the 136 kHz RC oscillator cannot meet the accuracy requirement of BLE. It is only suitable for scenarios with low clock accuracy requirements, such as legacy advertising (ADV) or scanning. It does not support connections in central or peripheral roles.
 
 .. only:: esp32
 
@@ -140,9 +127,7 @@ Selecting 136 kHz RC Oscillator
 
     - \ (X) Internal 136 kHz RC oscillator
 
-    Generally, the 136 kHz RC oscillator cannot meet the accuracy requirement of BLE. It is only suitable for scenarios with low clock accuracy requirements, such as legacy advertising (ADV) or scanning.
-
-    If low curent consumption is required but have no access to the External 32kHz Crystal, then this clock source is recommended. However, selecting this clock source will have the sleep clock accuracy larger than 500 PPM, which is supported if the peer device is also an ESP chip. If the peer device is not an ESP chip, here's some BLE event not supported:
+    If low current consumption is required but have no access to the External 32kHz Crystal, then this clock source is recommended. However, selecting this clock source will have the sleep clock accuracy larger than 500 PPM, which is supported if the peer device is also an ESP chip. If the peer device is not an ESP chip, here's some BLE event not supported:
 
     1. Central role of Connection
     2. Advertiser of Periodic Advertising
@@ -196,11 +181,7 @@ As explained in the clock source selection section above, when ACL connections f
 
 As introduced in the clock source selection section above, if the main XTAL is used as the clock source, it will remain powered on during light-sleep, resulting in higher current consumption than other clock sources.
 
-Also, BLE operates in Auto Light-sleep mode, meaning the system decides whether to enter sleep after entering IDLE. During advertising or scanning, current will be significantly higher than during light-sleep.
-
-Thus, the average current in low power mode is somewhere between light-sleep current and peak current (usually TX current).
-
-The average current can be application specific, and depends on the BLE configuration and the period of time in light-sleep mode. Some application may have larger average currrent because it has BLE taking a larger ratio of time transmitting and receiving.
+The average current can be application specific, and depends on the BLE configuration and the period of time in light-sleep mode. Some application may have larger average current because it has BLE taking a larger ratio of time transmitting and receiving.
 
 **3. Unable to Enter light-sleep Mode**
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

docs/zh_CN/api-guides/low-power-mode/low-power-mode-ble.rst

@@ -101,20 +101,7 @@
 
     - \ (X) Internal 136kHz RC oscillator
 
-    一般来说，136 kHz RC 振荡器难以满足 BLE 的精度要求，仅适用于对时钟精度要求不高的场景，如传统广播 (ADV) 或扫描 (SCAN)。
-
-    但测试时，如果对端设备也用 136 kHz RC 作为时钟源，可通过如下配置实现 BLE 在 136 kHz RC 下运行：
-
-    **配置路径：**
-
-    ``Component config → Bluetooth → Controller Options``
-
-    **配置选项：**
-
-    - \ [*] Enable to set constant peer SCA
-    - \ (3000) Constant peer sleep clock accuracy value
-
-    **注意：** 使用 136 kHz RC 振荡器可能偶发连接断开或连接失败。
+    一般来说，136 kHz RC 振荡器难以满足 BLE 的精度要求，仅适用于对时钟精度要求不高的场景，如传统广播 (ADV) 或扫描 (SCAN)。它不支持以中心角色或外设角色建立连接。
 
 .. only:: esp32
 
@@ -140,12 +127,10 @@
 
     - \ (X) Internal 136 kHz RC oscillator
 
-    一般来说，136 kHz RC 振荡器难以满足 BLE 的精度要求，仅适用于对时钟精度要求不高的场景，如传统广播 (ADV) 或扫描 (SCAN)。
+    对于需要低功耗且没有 32kHz 外部晶振的场景下，可以选择 136 kHz R C振荡器。然而这个时钟无法满足 BLE 的 500PPM 的休眠时钟精度需求。不过如果对端设备使用的是 ESP 芯片，仍能支持 BLE 行为。但是如果对端设备并非使用 ESP 芯片，则使用下面 BLE 行为将无法支持：
 
-    对于需要低功耗且没有32kHz外部晶振的场景下，可以选择136 kHz RC振荡器。然而这个时钟无法满足BLE的500PPM的休眠时钟精度需求。不过如果对端设备使用的是ESP芯片，仍能支持BLE行为。但是如果对端设备并非使用ESP芯片，则使用下面BLE行为将无法支持：
-
-      1. 作为连接的Central方
-      2. 作为Periodic Advertising的广播方
+      1. 作为连接的 Central 方
+      2. 作为 Periodic Advertising 的广播方
 
     如果对端设备也用 136 kHz RC 作为时钟源，需要如下配置:
 
@@ -196,11 +181,7 @@
 
 如时钟源选择部分所述，若主晶振为时钟源，light-sleep 模式下主晶振持续供电，电流消耗高于其他时钟源。
 
-此外，BLE 运行在 Auto Light-sleep 模式下，系统在进入 IDLE 后自动决定是否休眠。广播或扫描时电流远高于 light-sleep。
-
-因此，低功耗模式下的平均电流介于 light-sleep 电流与峰值电流（通常为 TX 电流）之间。
-
-一个应用程序的平均电流一般取决于在light-sleep模式下的时间，以及蓝牙的配置。如果一个应用中蓝牙收发包的时间更长，这个应用的平均电流也会更高
+平均电流可能会因具体应用而异，并取决于 BLE 的配置以及处于 light-sleep 模式的时间周期。某些应用的平均电流可能会更大，这是因为 BLE 在其中花费了更高比例的时间进行发射和接收。
 
 **3. 无法进入 light-sleep 模式**
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^