diff --git a/doc/async-functions-and-futures.md b/doc/async-functions-and-futures.md
index 7577a887d..44bb45354 100644
--- a/doc/async-functions-and-futures.md
+++ b/doc/async-functions-and-futures.md
@@ -1,4 +1,4 @@
-# OpenXR async functions (XrFutureEXT)
+# OpenXR async functions (XrFutureEXT)  {#async}
 
 <!--
 Copyright 2025, Collabora, Ltd. and the Monado contributors
diff --git a/doc/swapchains-ipc.md b/doc/swapchains-ipc.md
index f61460f5b..8a6890eb8 100644
--- a/doc/swapchains-ipc.md
+++ b/doc/swapchains-ipc.md
@@ -6,7 +6,7 @@ SPDX-License-Identifier: BSL-1.0
 -->
 
 The control flow in Monado for allocating the images/buffers used for a given
-@ref XrSwapchain can vary widely based on a number of factors.
+`XrSwapchain` can vary widely based on a number of factors.
 
 ## Simple in-process
 
@@ -23,7 +23,7 @@ implementations, uses Vulkan to allocate exportable images.
 
 ## Simple out-of-process
 
-The usual model on desktop is that the images for a given @ref XrSwapchain are
+The usual model on desktop is that the images for a given `XrSwapchain` are
 allocated in the service, as shown below.
 
 @mermaid{swapchain_allocation_ipc}