From 49d3ae12eac1ef012898280ca0fbcbc1d44d249a Mon Sep 17 00:00:00 2001 From: Rylie Pavlik Date: Tue, 9 Dec 2025 13:40:42 -0600 Subject: [PATCH] doc: Fix doxygen issues Part-of: --- doc/async-functions-and-futures.md | 2 +- doc/swapchains-ipc.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) 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} 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} -- 2.51.2