Merge branch 'docs/unify-menu-path-separator' into 'master'

docs: unify menu path separator from -> to >

See merge request application/esp-at!1942

Author: xcguang

docs/en/AT_Binary_Lists/esp_at_binaries.rst

@@ -11,7 +11,7 @@ It is recommended to use the latest version of firmware. Currently, Espressif re
 
     - The released AT firmware only supports chip versions with a crystal oscillator frequency of 26 MHz. If your module uses a crystal oscillator frequency of 40 MHz, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-      - ``Component config`` -> ``Hardware Settings`` -> ``Main XTAL Config`` -> ``Main XTAL frequency`` -> ``40 MHz``
+      - ``Component config`` > ``Hardware Settings`` > ``Main XTAL Config`` > ``Main XTAL frequency`` > ``40 MHz``
 
   .. only:: esp32 or esp32c2
 

docs/en/AT_Command_Examples/index.rst

@@ -9,7 +9,7 @@ AT Command Examples
 
    AT Response Message Format Control Examples <at_msg_resp_fmt_ctrl_examples>
    TCP-IP AT Examples <TCP-IP_AT_Examples>
-   :esp32 or esp32c2 or esp32c3 or esp32c5 or esp32c6 or esp32c61: Bluetooth® Low Engergy AT Examples <bluetooth_le_at_examples>
+   :esp32 or esp32c2 or esp32c3 or esp32c5 or esp32c6 or esp32c61: Bluetooth® Low Energy AT Examples <bluetooth_le_at_examples>
    MQTT AT Examples <MQTT_AT_Examples>
    MQTT AT Examples for Cloud <mqtt-at-examples-for-cloud>
    :esp32: Ethernet AT Examples <Ethernet_AT_Examples>

docs/en/AT_Command_Set/BLE_AT_Commands.rst

@@ -81,9 +81,9 @@ Introduction
   .. important::
     The default AT firmware supports all the AT commands mentioned on this page. If you need to modify the commands supported by {IDF_TARGET_NAME} by default, please compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections (Each item below is independent. Choose it according to your needs):
 
-    - Disable BluFi commands: ``Component config`` -> ``AT`` -> ``AT blufi command support``
-    - Disable Bluetooth LE commands: ``Component config`` -> ``AT`` -> ``AT ble command support``
-    - Disable Bluetooth LE HID commands: ``Component config`` -> ``AT`` -> ``AT ble hid command support``
+    - Disable BluFi commands: ``Component config`` > ``AT`` > ``AT blufi command support``
+    - Disable Bluetooth LE commands: ``Component config`` > ``AT`` > ``AT ble command support``
+    - Disable Bluetooth LE HID commands: ``Component config`` > ``AT`` > ``AT ble hid command support``
 
 .. only:: esp32c2
 

docs/en/AT_Command_Set/BT_AT_Commands.rst

@@ -39,9 +39,9 @@ Introduction
 .. important::
   The default AT firmware does not support the AT commands listed on this page. If you need {IDF_TARGET_NAME} to support Classic Bluetooth commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections (Each item below is independent. Choose it according to your needs):
 
-  - Enable Generic Bluetooth commands: ``Component config`` -> ``AT`` -> ``AT bt command support``
-  - Enable SPP commands: ``Component config`` -> ``AT`` -> ``AT bt command support`` -> ``AT bt spp command support``
-  - Enable A2DP commands:``Component config`` -> ``AT`` -> ``AT bt command support`` -> ``AT bt a2dp command support``
+  - Enable Generic Bluetooth commands: ``Component config`` > ``AT`` > ``AT bt command support``
+  - Enable SPP commands: ``Component config`` > ``AT`` > ``AT bt command support`` > ``AT bt spp command support``
+  - Enable A2DP commands:``Component config`` > ``AT`` > ``AT bt command support`` > ``AT bt a2dp command support``
 
 .. _cmd-BTINIT:
 

docs/en/AT_Command_Set/Driver_AT_Commands.rst

@@ -27,7 +27,7 @@ Introduction
 .. important::
   The default AT firmware does not support the AT commands listed on this page. If you need {IDF_TARGET_NAME} to support driver commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-  - Enable ``Component config`` -> ``AT`` -> ``AT driver command support``
+  - Enable ``Component config`` > ``AT`` > ``AT driver command support``
 
 .. _cmd-DRVADC:
 

docs/en/AT_Command_Set/FS_AT_Commands.rst

@@ -19,7 +19,7 @@ Introduction
 .. important::
   The default AT firmware does not support the AT commands listed on this page. If you need {IDF_TARGET_NAME} to support FileSystem commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-  - Enable ``Component config`` -> ``AT`` -> ``AT FS command support``
+  - Enable ``Component config`` > ``AT`` > ``AT FS command support``
 
 .. _cmd-FS:
 

docs/en/AT_Command_Set/HTTP_AT_Commands.rst

@@ -24,7 +24,7 @@ Introduction
 .. important::
   The default AT firmware supports all the AT commands mentioned on this page. If you don't need {IDF_TARGET_NAME} to support HTTP commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-  - Disable ``Component config`` -> ``AT`` -> ``AT http command support``
+  - Disable ``Component config`` > ``AT`` > ``AT http command support``
 
 .. _cmd-HTTPCLIENT:
 

docs/en/AT_Command_Set/MQTT_AT_Commands.rst

@@ -30,7 +30,7 @@ Introduction
 .. important::
   - The default AT firmware supports all the AT commands mentioned on this page. If you don't need {IDF_TARGET_NAME} to support MQTT commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-    - Disable ``Component config`` -> ``AT`` -> ``AT MQTT command support``
+    - Disable ``Component config`` > ``AT`` > ``AT MQTT command support``
 
   - For MQTT connection to local Broker examples, see :doc:`MQTT AT Examples <../AT_Command_Examples/MQTT_AT_Examples>`.
   - For MQTT connection to AWS IoT examples, see :doc:`MQTT Cloud Connection AT Examples <../AT_Command_Examples/mqtt-at-examples-for-cloud>`.

docs/en/AT_Command_Set/Signaling_Test_AT_Commands.rst

@@ -16,7 +16,7 @@ Introduction
 .. important::
   The default AT firmware supports all the AT commands mentioned on this page. If you don't need {IDF_TARGET_NAME} to support signaling test commands, you can compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections:
 
-  - Disable ``Component config`` -> ``AT`` -> ``AT signaling test command support``
+  - Disable ``Component config`` > ``AT`` > ``AT signaling test command support``
 
 .. _cmd-FACTPLCP:
 

docs/en/AT_Command_Set/TCP-IP_AT_Commands.rst

@@ -55,10 +55,10 @@ Introduction
 .. important::
   The default AT firmware supports all the AT commands mentioned on this page. If you need to modify the commands supported by {IDF_TARGET_NAME} by default, please compile the ESP-AT project by following the steps in :doc:`Compile ESP-AT Project Locally <../Compile_and_Develop/How_to_clone_project_and_compile_it>` documentation. In the project configuration during the fifth step, make the following selections (Each item below is independent. Choose it according to your needs):
 
-  - Disable OTA commands (:ref:`AT+CIUPDATE <cmd-UPDATE>` and :ref:`AT+CIPFWVER <cmd-FWVER>`): ``Component config`` -> ``AT`` -> ``AT OTA command support``
-  - Disable PING commands (:ref:`AT+PING <cmd-CIPPING>`): ``Component config`` -> ``AT`` -> ``AT ping command support``
-  - Disable mDNS commands (:ref:`AT+MDNS <cmd-MDNS>`): ``Component config`` -> ``AT`` -> ``AT MDNS command support``
-  - Disable TCP/IP commands (Not recommended. Once disabled, all TCP/IP functions will be unavailable and you will need to implement these AT commands yourself): ``Component config`` -> ``AT`` -> ``AT net command support``
+  - Disable OTA commands (:ref:`AT+CIUPDATE <cmd-UPDATE>` and :ref:`AT+CIPFWVER <cmd-FWVER>`): ``Component config`` > ``AT`` > ``AT OTA command support``
+  - Disable PING commands (:ref:`AT+PING <cmd-CIPPING>`): ``Component config`` > ``AT`` > ``AT ping command support``
+  - Disable mDNS commands (:ref:`AT+MDNS <cmd-MDNS>`): ``Component config`` > ``AT`` > ``AT MDNS command support``
+  - Disable TCP/IP commands (Not recommended. Once disabled, all TCP/IP functions will be unavailable and you will need to implement these AT commands yourself): ``Component config`` > ``AT`` > ``AT net command support``
 
 .. _cmd-IPV6:
 
@@ -389,7 +389,7 @@ Notes
   -  Obtain an IPv6 address through the :ref:`AT+CWJAP <cmd-JAP>` command
   - (Optional) Check whether {IDF_TARGET_NAME} has obtained an IPv6 address using the :ref:`AT+CIPSTA? <cmd-IPSTA>` command
 
-- If you want to receive a UDP packet longer than 1460 bytes, please compile the firmware on your own by following :doc:`Compile ESP-AT Project <../Compile_and_Develop/How_to_clone_project_and_compile_it>` and choosing the following configurations in the Step 5. Configure: ``Component config`` -> ``LWIP`` -> ``Enable reassembly incoming fragmented IP4 packets``.
+- If you want to receive a UDP packet longer than 1460 bytes, please compile the firmware on your own by following :doc:`Compile ESP-AT Project <../Compile_and_Develop/How_to_clone_project_and_compile_it>` and choosing the following configurations in the Step 5. Configure: ``Component config`` > ``LWIP`` > ``Enable reassembly incoming fragmented IP4 packets``.
 - To view the reason for UDP transmission establishment failure, please first run :ref:`AT+SYSLOG=1 <cmd-SYSLOG>` to enable logging, then retry this command. Upon failure, AT will return a more detailed error code ``+ERRNO:<error_code>`` to help locate the problem.
 
 Example