diff --git a/examples/coap/src/seccontext.rs b/examples/coap/src/seccontext.rs
index 72b4e526f..2ec068184 100644
--- a/examples/coap/src/seccontext.rs
+++ b/examples/coap/src/seccontext.rs
@@ -151,7 +151,7 @@ enum SecContextStage {
     // roll-over is a topic, that'd be a no-go. An alternative is to both store the message and the
     // ResponderWaitM3 state -- but that'll make our SecContextPool slots larger; best evaluate
     // that once the states are ready and we see which ones are the big ones. Possible outcomes are
-    // to just do it, to store the message in the handler's RequestData, or to have one or a few
+    // to just do it, to store the message in the handler's `RequestData`, or to have one or a few
     // slots in parallel to this in the SecContextPool.
     EdhocResponderProcessedM1 {
         responder: lakers::EdhocResponderProcessedM1<'static, LakersCrypto>,