diff --git a/doc/api.dox b/doc/api.dox
index 220567e9c..dc624b465 100644
--- a/doc/api.dox
+++ b/doc/api.dox
@@ -15,7 +15,7 @@ invokes that same method on the remote side. Marshalling and de-marshalling is
 handled transparently by the \ref page_module_protocol_native.
 The below graph illustrates this approach:
 
-@dot
+\dot
 digraph API {
   compound=true;
   node [shape="box"];
@@ -46,7 +46,7 @@ digraph API {
   obj_node -> impl_node;
 
 }
-@enddot
+\enddot
 
 It is common for clients to use both the Core API and the Implementation API
 and both APIs are provided by the same library.
diff --git a/doc/pipewire-daemon.dox b/doc/pipewire-daemon.dox
index 2c7d686bf..2ca2c243b 100644
--- a/doc/pipewire-daemon.dox
+++ b/doc/pipewire-daemon.dox
@@ -10,7 +10,7 @@ PipeWire socket (default: `$XDG_RUNTIME_DIR/pipewire-0`). This approach
 provides provides address-space separation between the privileged daemon and
 non-privileged clients.
 
-@dot
+\dot
 digraph pw {
   compound=true;
   node [shape="box"];
@@ -46,7 +46,7 @@ digraph pw {
   sm -> socket;
   alsa -> kernel;
 }
-@enddot
+\enddot
 
 As shown above, the protocol is handled by the \ref
 page_module_protocol_native. From PipeWire's point-of-view this module is just