diff --git a/doc/board/em_starterkit.rst b/doc/board/em_starterkit.rst
index feb34f08615..daaf03086bc 100644
--- a/doc/board/em_starterkit.rst
+++ b/doc/board/em_starterkit.rst
@@ -156,7 +156,7 @@ On your development environment, you will need to:
 * Open a serial port emulator (i.e. on Linux minicom, putty, screen, etc)
 
 * Specify the tty driver name, for example, on Linux this may be
- :file:`/dev/ttyUSB1`
+  :file:`/dev/ttyUSB1`
 
 * Set the communication settings to:
 
diff --git a/doc/reference/kbuild/kbuild_project.rst b/doc/reference/kbuild/kbuild_project.rst
index de649064ae0..f9b957fce68 100644
--- a/doc/reference/kbuild/kbuild_project.rst
+++ b/doc/reference/kbuild/kbuild_project.rst
@@ -38,7 +38,7 @@ A common application project is composed of the following files:
   different directory.
 
    * **Makefile**: Adds the developer's source code into the build system's
-   recursion model.
+     recursion model.
 
 The application's source code can be organized in subdirectories.
 Each directory must follow the Kbuild Makefile conventions; see
@@ -130,9 +130,9 @@ QEMU is the supported emulation system of the kernel. QEMU must be invoked
 with the -s and -S options.
 
 * :option:`-S` Do not start CPU at startup; rather, you must type 'c' in the
-monitor.
+  monitor.
 * :option:`-s` Shorthand for :literal:`-gdb tcp::1234`: open a GDB server on
-TCP port 1234.
+  TCP port 1234.
 
 The build system can build the elf binary and call the QEMU process with
 the :makevar:`qemu` target. The QEMU debug options can be set using the
@@ -202,4 +202,4 @@ elf binary file, in this instance, the :file:`zephyr.elf` file.
 
    Both commands execute the :abbr:`gdb (GNU Debugger)`.
    The command name might change depending on the toolchain you are using
-   and your cross-development tools.
\ No newline at end of file
+   and your cross-development tools.
diff --git a/doc/subsystems/power_management.rst b/doc/subsystems/power_management.rst
index 2b533d7b1b4..966cacd18b9 100644
--- a/doc/subsystems/power_management.rst
+++ b/doc/subsystems/power_management.rst
@@ -542,7 +542,7 @@ operations:
    #. The PMA returns the :code:`SYS_PM_LOW_POWER_STATE` code.
 
 * If the time allotted is not enough for the :code:`SYS_PM_LOW_POWER_STATE`
-policy, the PMA returns the :code:`SYS_PM_DEVICE_SUSPEND_ONLY` code.
+  policy, the PMA returns the :code:`SYS_PM_DEVICE_SUSPEND_ONLY` code.
 
 When a device fails to suspend, the PMA executes the following operations: