diff --git a/doc/services/portability/posix/overview/index.rst b/doc/services/portability/posix/overview/index.rst
index 4ef1f9a596d..a57465d8e49 100644
--- a/doc/services/portability/posix/overview/index.rst
+++ b/doc/services/portability/posix/overview/index.rst
@@ -38,11 +38,12 @@ Benefits of POSIX support in Zephyr include:
 POSIX Subprofiles
 =================
 
-While Zephyr supports running multiple `threads <threads_v2>` (possibly in an `SMP <smp_arch>`
-configuration), as well as `Virtual Memory and MMUs <memory_management_api>`, Zephyr code and data
-normally share a common address space. The Zephyr kernel executable code and the application
-executable code are typically compiled into the same binary artifact. From that perspective, Zephyr
-apps can be seen as running in the context of a single process.
+While Zephyr supports running multiple :ref:`thread <threads_v2>` (possibly in an
+:ref:`SMP <smp_arch>` configuration), as well as
+:ref:`Virtual Memory and MMUs <memory_management_api>`, Zephyr code and data normally share a
+common address space. The Zephyr kernel executable code and the application executable code are
+typically compiled into the same binary artifact. From that perspective, Zephyr apps can be seen
+as running in the context of a single process.
 
 While multi-purpose operating systems (OS) offer full POSIX conformance, Real-Time Operating
 Systems (RTOS) such as Zephyr typically serve a fixed-purpose, have limited hardware resources,