doc: sphinx-lint: fix bad usage of "default role"

Fixes bad usage of single backticks in lieu of double backticks for
rendering inline literals, or simple '*' for italics.

When appropriate, a better construct than double backticks has been
selected (ex. :file:, :kconfig:option:, :c:func:, ...), or proper :ref:
have been used if the original intention was to have a link.

Signed-off-by: Benjamin Cabé <[email protected]>

Author: kartben

boards/adafruit/feather_nrf52840/doc/index.rst

@@ -181,8 +181,8 @@ but does not support debugging the device.
 #. If using UF2, connect the board to your host computer using USB.
 
 #. Tap the reset button twice quickly to enter bootloader mode.
-   A mass storage device named `FTHR840BOOT` for (Express) or
-   `FTHRSNSBOOT` (Sense) should appear on the host. Ensure this is
+   A mass storage device named ``FTHR840BOOT`` for (Express) or
+   ``FTHRSNSBOOT`` (Sense) should appear on the host. Ensure this is
    mounted.
 
 #. Flash the image.

boards/adafruit/kb2040/doc/index.rst

@@ -117,7 +117,7 @@ Using UF2
 
 Since it doesn't expose the SWD pins, you must flash the Adafruit KB2040 with
 a UF2 file. By default, building an app for this board will generate a
-`build/zephyr/zephyr.uf2` file. If the KB2040 is powered on with the `BOOTSEL`
+:file:`build/zephyr/zephyr.uf2` file. If the KB2040 is powered on with the ``BOOTSEL``
 button pressed, it will appear on the host as a mass storage device. The
 UF2 file should be drag-and-dropped to the device, which will flash the KB2040.
 

boards/adafruit/qt_py_rp2040/doc/index.rst

@@ -116,7 +116,7 @@ Using UF2
 
 Since it doesn't expose the SWD pins, you must flash the Adafruit QT Py RP2040 with
 a UF2 file. By default, building an app for this board will generate a
-`build/zephyr/zephyr.uf2` file. If the QT Py RP2040 is powered on with the `BOOTSEL`
+:file:`build/zephyr/zephyr.uf2` file. If the QT Py RP2040 is powered on with the ``BOOTSEL``
 button pressed, it will appear on the host as a mass storage device. The
 UF2 file should be drag-and-dropped to the device, which will flash the QT Py RP2040.
 

boards/ambiq/apollo3_evb/doc/index.rst

@@ -69,7 +69,7 @@ Build the Zephyr kernel and application, then flash it to the device:
    :goals: flash
 
 .. note::
-   `west flash` requires `SEGGER J-Link software`_ and `pylink`_ Python module
+   ``west flash`` requires `SEGGER J-Link software`_ and `pylink`_ Python module
    to be installed on you host computer.
 
 Open a serial terminal (minicom, putty, etc.) with the following settings:

boards/ambiq/apollo3p_evb/doc/index.rst

@@ -69,7 +69,7 @@ Build the Zephyr kernel and application, then flash it to the device:
    :goals: flash
 
 .. note::
-   `west flash` requires `SEGGER J-Link software`_ and `pylink`_ Python module
+   ``west flash`` requires `SEGGER J-Link software`_ and `pylink`_ Python module
    to be installed on you host computer.
 
 Open a serial terminal (minicom, putty, etc.) with the following settings:

boards/ambiq/apollo4p_blue_kxr_evb/doc/index.rst

@@ -77,7 +77,7 @@ Build the Zephyr kernel and application, then flash it to the device:
    :goals: flash
 
 .. note::
-   `west flash` requires `SEGGER J-Link software`_ and `pylink`_ Python module
+   ``west flash`` requires `SEGGER J-Link software`_ and `pylink`_ Python module
    to be installed on you host computer.
 
 Open a serial terminal (minicom, putty, etc.) with the following settings:

boards/ambiq/apollo4p_evb/doc/index.rst

@@ -72,7 +72,7 @@ Build the Zephyr kernel and application, then flash it to the device:
    :goals: flash
 
 .. note::
-   `west flash` requires `SEGGER J-Link software`_ and `pylink`_ Python module
+   ``west flash`` requires `SEGGER J-Link software`_ and `pylink`_ Python module
    to be installed on you host computer.
 
 Open a serial terminal (minicom, putty, etc.) with the following settings:

boards/arduino/nano_33_ble/doc/index.rst

@@ -160,7 +160,7 @@ That license ties to Arduino Nano 33 BLE hardware serial number,
 it also works with the ZephyrRTOS.
 
 Follow the instruction of the tutorial for Arduino
-`Lauterbach TRACE32 GDB Front-End Debugger for Nano 33 BLE`
+`Lauterbach TRACE32 GDB Front-End Debugger for Nano 33 BLE`_
 to install the TRACE32.
 
 After installing the TRACE32, You should set the environmental variable ``T32_DIR``.

boards/arm/fvp_base_revc_2xaemv8a/doc/index.rst

@@ -99,7 +99,7 @@ Checkout and Build the TF-A:
    cd trusted-firmware-a/
    make PLAT=fvp PRELOADED_BL33_BASE="0x88000000" all fip
 
-then export the ``ARMFVP_BL1_FILE` and ``ARMFVP_FIP_FILE`` environment variables:
+then export the :envvar:`ARMFVP_BL1_FILE` and :envvar:`ARMFVP_FIP_FILE` environment variables:
 
 .. code-block:: console
 

boards/circuitdojo/feather/doc/index.rst

@@ -100,7 +100,7 @@ or Nordic based examples.
    Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
 
 Some of the examples do not use secure mode, so they do not require the
-``ns`` suffix. A great example of this is the `hello_world` below.
+``ns`` suffix. A great example of this is the ``hello_world`` below.
 
 Flashing
 ========