diff --git a/docs/en/api-guides/performance/speed.rst b/docs/en/api-guides/performance/speed.rst index c8e338e3c3..b168b003db 100644 --- a/docs/en/api-guides/performance/speed.rst +++ b/docs/en/api-guides/performance/speed.rst @@ -193,7 +193,7 @@ Common priorities are: All Bluedroid Tasks are pinned to the same core, which is Core 0 by default (:ref:`configurable `). - The Ethernet driver creates a task for the MAC to receive Ethernet frames. If using the default config ``ETH_MAC_DEFAULT_CONFIG`` then the priority is medium-high (15) and the task is not pinned to any core. These settings can be changed by passing a custom :cpp:class:`eth_mac_config_t` struct when initializing the Ethernet MAC. - If using the :doc:`MQTT ` component, it creates a task with default priority 5 (:ref:`configurable `, depends on :ref:`CONFIG_MQTT_USE_CUSTOM_CONFIG`) and not pinned to any core (:ref:`configurable `). - - To see what is the task priority for ``mDNS`` service, please check `Performance Optimization `__. + - To see what is the task priority for ``mDNS`` service, please check `Performance Optimization `__. Choosing application task priorities ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/docs/en/contribute/esp-idf-tests-with-pytest.rst b/docs/en/contribute/esp-idf-tests-with-pytest.rst index e011d0ce27..a5315874cd 100644 --- a/docs/en/contribute/esp-idf-tests-with-pytest.rst +++ b/docs/en/contribute/esp-idf-tests-with-pytest.rst @@ -164,15 +164,15 @@ Pytest Execution Process 1. ``pexpect_proc``: `pexpect `__ instance - 2. ``app``: `IdfApp `__ instance + 2. ``app``: `IdfApp `__ instance The information of the app, like sdkconfig, flash_files, partition_table, etc., would be parsed at this phase. - 3. ``serial``: `IdfSerial `__ instance + 3. ``serial``: `IdfSerial `__ instance The port of the host which connected to the target type parsed from the app would be auto-detected. The flash files would be auto flashed. - 4. ``dut``: `IdfDut `__ instance + 4. ``dut``: `IdfDut `__ instance 2. Run the real test function @@ -269,7 +269,7 @@ Expect From the Serial output When we're using ``dut.expect(...)``, the string would be compiled into regex at first, and then seeks through the serial output until the compiled regex is matched, or a timeout is exceeded. You may have to pay extra attention when the string contains regex keyword characters, like parentheses, or square brackets. -Actually using ``dut.expect_exact(...)`` here is better, since it would seek until the string is matched. For further reading about the different types of ``expect`` functions, please refer to the `pytest-embedded Expecting documentation `__. +Actually using ``dut.expect_exact(...)`` here is better, since it would seek until the string is matched. For further reading about the different types of ``expect`` functions, please refer to the `pytest-embedded Expecting documentation `__. Advanced Examples -----------------