+2 -2

doc/conventions.md

reviewed

··· 114 114 115 115 For example, consider @ref client_gl_swapchain 116 116 117 117 - - Its first element is named @ref client_gl_swapchain::base and is of type @ref 118 118 - xrt_swapchain_gl - meaning that it implements @ref xrt_swapchain_gl 117 117 + - Its first element is named @ref client_gl_swapchain::base and is of type 118 118 + @ref xrt_swapchain_gl - meaning that it implements @ref xrt_swapchain_gl 119 119 - @ref xrt_swapchain_gl in turn starts with @ref xrt_swapchain_gl::base which is 120 120 @ref xrt_swapchain - meaning that @ref xrt_swapchain_gl **extends** @ref 121 121 xrt_swapchain. (Both @ref xrt_swapchain_gl and @ref xrt_swapchain are abstract

+2 -2

doc/writing-a-new-driver.md

reviewed

··· 67 67 68 68 Depending on whether your device can be created from a detected USB HID device, 69 69 you will also need to implement either @ref xrt_auto_prober or a function 70 70 - matching @ref xrt_prober_found_function_t which is the function pointer type of 70 70 + matching @ref xrt_prober_found_func_t which is the function pointer type of 71 71 @ref xrt_prober_entry::found. See below for more details. 72 72 73 73 ## Probing ··· 79 79 80 80 If you can detect based on VID/PID, you will instead implement If you can use 81 81 built-in HID, you might consider looking at @ref hdk_found, which is a nice 82 82 - example of how to implement @ref xrt_prober_found_function_t to perform 82 82 + example of how to implement @ref xrt_prober_found_func_t to perform 83 83 detection of an HMD based on the USB HID for its IMU. 84 84 85 85 Either way, your device's detection details will need to be added to a list used