doc: boards: Align native_sim to zephyr-board

carlescufi · carlescufi · commit 0b22f46800bb · 2025-09-23T20:48:39.000+02:00
See upstream commit 6de770291092178058bf3652a5221d32b4e8e078.

Signed-off-by: Carles Cufi &lt;carles.cufi@nordicsemi.no&gt;
diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-2.7.0.rst b/doc/nrf/releases_and_maturity/releases/release-notes-2.7.0.rst
@@ -845,7 +845,7 @@ Networking samples
 ------------------
 
 * Updated the networking samples to support import of certificates in valid PEM formats.
-* Removed QEMU x86 emulation support and added support for the :ref:`native simulator <zephyr:native_sim>` board.
+* Removed QEMU x86 emulation support and added support for the :zephyr:board:`native simulator <native_sim>` board.
 
 * :ref:`mqtt_sample` sample:
 
diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1.rst b/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0-nRF54H20-1.rst
@@ -113,7 +113,7 @@ IDE, OS, and tool support
 Board support
 =============
 
-* Updated various tests and samples to use Zephyr's :ref:`native simulator <zephyr:native_sim>` instead of Zephyr's native POSIX for :ref:`running_unit_tests`.
+* Updated various tests and samples to use Zephyr's :zephyr:board:`native simulator <native_sim>` instead of Zephyr's native POSIX for :ref:`running_unit_tests`.
   This mirrors the deprecation of ``native_posix`` in Zephyr.
   Support for ``native_posix`` will be removed in Zephyr with the v4.2 release.
   In the |NCS|, it will be removed once Zephyr v4.2 is upmerged to sdk-nrf.
diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0.rst b/doc/nrf/releases_and_maturity/releases/release-notes-2.9.0.rst
@@ -141,7 +141,7 @@ IDE, OS, and tool support
 Board support
 =============
 
-* Updated various tests and samples to use Zephyr's :ref:`native simulator <zephyr:native_sim>` instead of Zephyr's native POSIX for :ref:`running_unit_tests`.
+* Updated various tests and samples to use Zephyr's :zephyr:board:`native simulator <native_sim>` instead of Zephyr's native POSIX for :ref:`running_unit_tests`.
   This mirrors the deprecation of ``native_posix`` in Zephyr.
   Support for ``native_posix`` will be removed in Zephyr with the v4.2 release.
   In the |NCS|, it will be removed once Zephyr v4.2 is upmerged to sdk-nrf.
diff --git a/doc/nrf/test_and_optimize/test_framework/running_unit_tests.rst b/doc/nrf/test_and_optimize/test_framework/running_unit_tests.rst
@@ -31,7 +31,7 @@ To generate the test project and run the unit tests, locate the directory with t
 
          <Zephyr_path>/scripts/twister -T .
 
-      This command will generate the test project and run it for :ref:`zephyr:native_sim` and ``qemu_cortex_m3`` boards.
+      This command will generate the test project and run it for :zephyr:board:`native_sim` and ``qemu_cortex_m3`` boards.
       If you want to specify a board target, use the ``-p`` parameter and specify the *board_target*.
       For example, to run the unit test on ``qemu_cortex_m3``, use the following command:
 
@@ -45,7 +45,7 @@ To generate the test project and run the unit tests, locate the directory with t
 
          <Zephyr_path>/scripts/twister -T .
 
-      This command will generate the test project and run it for :ref:`zephyr:native_sim` and ``qemu_cortex_m3`` boards.
+      This command will generate the test project and run it for :zephyr:board:`native_sim` and ``qemu_cortex_m3`` boards.
       If you want to specify a board target, use the ``-p`` parameter and specify the *board_target*.
       For example, to run the unit test on ``qemu_cortex_m3``, use the following command:
 
@@ -61,7 +61,7 @@ To generate the test project and run the unit tests, locate the directory with t
          west build -b *board_target* -t run
 
       The ``-t run`` parameter tells west to run the default test target.
-      For example, to run the unit test on :ref:`zephyr:native_sim` board, use the following command:
+      For example, to run the unit test on :zephyr:board:`native_sim` board, use the following command:
 
       .. code-block:: console
 
diff --git a/doc/nrf/test_and_optimize/test_framework/testing_unity_cmock.rst b/doc/nrf/test_and_optimize/test_framework/testing_unity_cmock.rst
@@ -13,7 +13,7 @@ The |NCS| provides support for writing tests using Unity and CMock.
 Support for CMock is integrated into Unity.
 
 CMake automatically generates the required test runner file and the mock files.
-The test can be executed on the :ref:`zephyr:native_sim` board.
+The test can be executed on the :zephyr:board:`native_sim` board.
 For more information, see :ref:`running_unit_tests`.
 
 Setting up a unit test
diff --git a/samples/cellular/nrf_cloud_multi_service/README.rst b/samples/cellular/nrf_cloud_multi_service/README.rst
@@ -1068,7 +1068,7 @@ These overlays show all the Kconfig settings changes needed to properly disable
 Building with native simulator
 ==============================
 
-You can run this sample on the :ref:`zephyr:native_sim` target.
+You can run this sample on the :zephyr:board:`native simulator <native_sim>` target.
 This enables you to try out connectivity without the need for embedded hardware.
 A Linux host or docker container is required to run the ``native_sim`` target.
 Some setup is needed to connect the application to the network.
diff --git a/samples/net/aws_iot/README.rst b/samples/net/aws_iot/README.rst
@@ -24,7 +24,7 @@ The sample supports the following development kits:
 
 .. table-from-sample-yaml::
 
-Additionally, the sample supports emulation using the :ref:`native simulator <zephyr:native_sim>`.
+Additionally, the sample supports emulation using the :zephyr:board:`native simulator <native_sim>`.
 
 .. include:: /includes/tfm.txt
 
@@ -217,7 +217,7 @@ To observe incoming messages in the AWS IoT console, follow the steps documented
 Emulation
 =========
 
-The sample can run on the :ref:`native simulator <zephyr:native_sim>`, which simplifies development and testing and removes the need for hardware.
+The sample can run on the :zephyr:board:`native simulator <native_sim>`, which simplifies development and testing and removes the need for hardware.
 Before you build and run on the ``native_sim`` board, you need to perform the steps documented in :ref:`networking_with_native_sim`.
 
 When these steps are completed, you can build and run the sample by using the following commands:
diff --git a/samples/net/mqtt/doc/description.rst b/samples/net/mqtt/doc/description.rst
@@ -20,7 +20,7 @@ The sample supports the following development kits:
 
 .. table-from-sample-yaml::
 
-Additionally, the sample supports emulation using the :ref:`native simulator <zephyr:native_sim>`.
+Additionally, the sample supports emulation using the :zephyr:board:`native simulator <native_sim>`.
 
 Overview
 *********
@@ -271,7 +271,7 @@ If this occurs, the sample's transport module has built-in reconnection logic th
 Emulation
 =========
 
-The sample can be run in :ref:`native simulator <zephyr:native_sim>` that simplifies development and testing and removes the need for hardware.
+The sample can be run in :zephyr:board:`native simulator <native_sim>` that simplifies development and testing and removes the need for hardware.
 Before you can build and the run native simulator, you need to perform the steps included in this link: :ref:`networking_with_native_sim`.
 
 When the aforementioned steps are completed, you can build and run the sample by using the following commands:
diff --git a/samples/net/udp/README.rst b/samples/net/udp/README.rst
@@ -21,7 +21,7 @@ The sample supports the following development kits:
 
 .. table-from-sample-yaml::
 
-Additionally, the sample supports emulation using the :ref:`native simulator <zephyr:native_sim>`.
+Additionally, the sample supports emulation using the :zephyr:board:`native simulator <native_sim>`.
 
 Overview
 ********
