diff --git a/docs/secure-partition-manager/secure-partition-manager.rst b/docs/secure-partition-manager/secure-partition-manager.rst
index b9a9e36..0425a94 100644
--- a/docs/secure-partition-manager/secure-partition-manager.rst
+++ b/docs/secure-partition-manager/secure-partition-manager.rst
@@ -1741,9 +1741,8 @@
 These DMA devices are dependent on PE endpoint to initiate and receive memory
 management transactions on their behalf. The acccess to the MMIO regions of
 any such device is assigned to the endpoint during boot.
-The :ref:`device node<device_region_node>` of the corresponding partition
-manifest must specify these additional properties for each peripheral device in
-the system:
+The `device node`_ of the corresponding partition manifest must specify these
+additional properties for each peripheral device in the system:
 
 -  smmu-id: This field helps to identify the SMMU instance that this device is
    upstream of.
@@ -1767,8 +1766,8 @@
 Hafnium, with help of SMMUv3 driver, enables the support for static DMA
 isolation. The DMA device is explicitly granted access to a specific
 memory region only if the partition requests it by declaring the following
-properties of the DMA device in the :ref:`memory region node<memory_region_node>`
-of the partition manifest:
+properties of the DMA device in the `memory region node`_ of the partition
+manifest:
 
 -  smmu-id
 -  stream-ids
@@ -1837,6 +1836,10 @@
 
 .. _SPMC FVP build configuration: https://github.com/TF-Hafnium/hafnium-project-reference/blob/main/BUILD.gn#L143
 
+.. _device node: https://trustedfirmware-a.readthedocs.io/en/latest/components/ffa-manifest-binding.html#device-regions
+
+.. _memory region node: https://trustedfirmware-a.readthedocs.io/en/latest/components/ffa-manifest-binding.html#memory-regions
+
 .. _[1]:
 
 [1] `Arm Firmware Framework for Arm A-profile <https://developer.arm.com/docs/den0077/latest>`__