diff --git a/boards/cdns/xt-sim/doc/index.rst b/boards/cdns/xt-sim/doc/index.rst
index d8a4b9c5993..5f97e597250 100644
--- a/boards/cdns/xt-sim/doc/index.rst
+++ b/boards/cdns/xt-sim/doc/index.rst
@@ -38,7 +38,7 @@ System requirements
 Prerequisites
 =============
 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).
 
 Only Xtensa tools version ``RF-2016.4-linux`` or later are officially
diff --git a/doc/develop/west/build-flash-debug.rst b/doc/develop/west/build-flash-debug.rst
index 5cc4dd70305..a7c19857dd3 100644
--- a/doc/develop/west/build-flash-debug.rst
+++ b/doc/develop/west/build-flash-debug.rst
@@ -771,7 +771,7 @@ Runner-Specific Overrides
 =========================
 
 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
 
diff --git a/doc/develop/west/west-apis.rst b/doc/develop/west/west-apis.rst
index 306cef813e8..e7eb623ac5d 100644
--- a/doc/develop/west/west-apis.rst
+++ b/doc/develop/west/west-apis.rst
@@ -148,7 +148,7 @@ WestCommand
    .. method:: check_call(args, **kwargs)
 
       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
       The *cwd* keyword argument was replaced with a catch-all ``**kwargs``.
diff --git a/tests/bsim/bluetooth/mesh/README.rst b/tests/bsim/bluetooth/mesh/README.rst
index 1ae78887b71..02f16740bb5 100644
--- a/tests/bsim/bluetooth/mesh/README.rst
+++ b/tests/bsim/bluetooth/mesh/README.rst
@@ -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
 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
 test application's main function. The harness contains a set of callback
 functions that allows starting the test behavior.