From f26c90fca89ca366497a78d281f293e3f4f46433 Mon Sep 17 00:00:00 2001
From: Sreelakshmi Haridas Maruthur <sreelakshmi.haridas@gmail.com>
Date: Tue, 10 Sep 2024 11:53:17 -0600
Subject: [PATCH] Update api/opencl_platform_layer.asciidoc

Co-authored-by: Ben Ashbaugh <ben.ashbaugh@intel.com>
---
 api/opencl_platform_layer.asciidoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/api/opencl_platform_layer.asciidoc b/api/opencl_platform_layer.asciidoc
index b762e24d..81f08b58 100644
--- a/api/opencl_platform_layer.asciidoc
+++ b/api/opencl_platform_layer.asciidoc
@@ -1606,8 +1606,8 @@ include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES.asci
         {CL_DEVICE_ATOMIC_ORDER_RELAXED} \| +
         {CL_DEVICE_ATOMIC_SCOPE_WORK_GROUP}
 
-        A device that does not support CL_DEVICE_SVM_ATOMICS (and hence does not support CL_MEM_SVM_ATOMICS) may still support CL_DEVICE_ATOMIC_SCOPE_ALL_DEVICES. On these devices, an atomic operation with
-        memory_scope_all_svm_devices will behave the same as if the scope were memory_scope_device - refer to <<memory-consistency-model, memory consistency model>>
+        A device that does not support {CL_DEVICE_SVM_ATOMICS} (and hence does not support {CL_MEM_SVM_ATOMICS}) may still support {CL_DEVICE_ATOMIC_SCOPE_ALL_DEVICES}. On these devices, an atomic operation with
+        *memory_scope_all_svm_devices* will behave the same as if the scope were *memory_scope_device* - refer to the <<memory-consistency-model, memory consistency model>>.
 
 | {CL_DEVICE_ATOMIC_FENCE_CAPABILITIES_anchor}