doc: sphinx-lint: fix unbalanced-inline-literals-delimiters

used sphinx-lint to catch unbalanced inline literal markup.

Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit is contained in:
Benjamin Cabé 2024-09-10 18:45:21 +02:00 committed by Anas Nashif
commit fc9e7962c2
4 changed files with 4 additions and 4 deletions

View file

@ -38,7 +38,7 @@ System requirements
Prerequisites Prerequisites
============= =============
A Linux host system is required for Xtensa development work. A Linux host system is required for Xtensa development work.
We recommend using a __``Debian 9.x (Stretch)``__ or recent __``Ubuntu``__ We recommend using a Debian 9.x (Stretch) or recent Ubuntu
releases (with multilib support). releases (with multilib support).
Only Xtensa tools version ``RF-2016.4-linux`` or later are officially Only Xtensa tools version ``RF-2016.4-linux`` or later are officially

View file

@ -771,7 +771,7 @@ Runner-Specific Overrides
========================= =========================
To view all of the available options supported by the runners, as well To view all of the available options supported by the runners, as well
as their usage information, use ``--context`` (or``-H``):: as their usage information, use ``--context`` (or ``-H``)::
west simulate --runner=renode --context west simulate --runner=renode --context

View file

@ -148,7 +148,7 @@ WestCommand
.. method:: check_call(args, **kwargs) .. method:: check_call(args, **kwargs)
Runs ``subprocess.check_call(args, **kwargs)`` after Runs ``subprocess.check_call(args, **kwargs)`` after
logging the call at Verbosity.DBG_MORE`` level. logging the call at ``Verbosity.DBG_MORE`` level.
.. versionchanged:: 1.2.0 .. versionchanged:: 1.2.0
The *cwd* keyword argument was replaced with a catch-all ``**kwargs``. The *cwd* keyword argument was replaced with a catch-all ``**kwargs``.

View file

@ -97,7 +97,7 @@ Test scripts should be organized by submodules under the test_scripts
directory, and each test case needs a separate test script with a single test directory, and each test case needs a separate test script with a single test
run. run.
Each test harness is defined by a ``struct bst_test_instance` structure, that Each test harness is defined by a ``struct bst_test_instance`` structure, that
is presented to the test runner through an ``install`` function called from the is presented to the test runner through an ``install`` function called from the
test application's main function. The harness contains a set of callback test application's main function. The harness contains a set of callback
functions that allows starting the test behavior. functions that allows starting the test behavior.