diff --git a/doc/vulkan-mapping.dox b/doc/vulkan-mapping.dox
index de1d9cf5f..c0b438b6e 100644
--- a/doc/vulkan-mapping.dox
+++ b/doc/vulkan-mapping.dox
@@ -25,7 +25,7 @@
 
 namespace Magnum { namespace Vk {
 
-/** @page vulkan-mapping APi mapping
+/** @page vulkan-mapping API mapping
 @brief List of Vulkan handles, functions, enums and structures corresponding to particular Magnum APIs.
 @m_since_latest
 
diff --git a/src/Magnum/Vk/Instance.h b/src/Magnum/Vk/Instance.h
index 97d46b2fe..2622a7081 100644
--- a/src/Magnum/Vk/Instance.h
+++ b/src/Magnum/Vk/Instance.h
@@ -172,7 +172,7 @@ Compared to the above, the same custom code would then look like this:
 Similarly you can use @ref Device::populateGlobalFunctionPointers() to populate
 device-level global function pointers.
 
-@section Vk-Instance-disabled-move Disabled move and delayed instances creation
+@section Vk-Instance-disabled-move Disabled move and delayed instance creation
 
 Similarly to @ref Device, for safety reasons as all instance-dependent objects
 internally have to keep a pointer to the originating @ref Instance to access