diff --git a/docs/1-essentials/01-routing.md b/docs/1-essentials/01-routing.md
index 9f52b3e79..968319af4 100644
--- a/docs/1-essentials/01-routing.md
+++ b/docs/1-essentials/01-routing.md
@@ -452,7 +452,7 @@ When users submit forms—like updating profile settings, or posting comments—
 On validation failure, Tempest either redirects back to the form (for web pages) or returns a 422 response (for stateless requests). Validation errors are available in two places:
 
 - As a JSON encoded string in the `{txt}X-Validation` header
-- Through the `b{Tempest\Http\Session\FormSession}` class
+- Through the {b`Tempest\Http\Session\FormSession`} class
 
 For web pages, Tempest also provides built-in view components to display errors when they occur.
 
diff --git a/docs/2-features/08-events.md b/docs/2-features/08-events.md
index d98e3911f..6eee2be41 100644
--- a/docs/2-features/08-events.md
+++ b/docs/2-features/08-events.md
@@ -161,7 +161,7 @@ final readonly class EventLoggerMiddleware implements EventBusMiddleware
 
 ## Stopping event propagation
 
-In rare cases you might want an event only to be handled by a single handler. You can use the `b{Tempest\EventBus\StopsPropagation}` attribute on both events and event handlers to achieve this:
+In rare cases you might want an event only to be handled by a single handler. You can use the {b`Tempest\EventBus\StopsPropagation`} attribute on both events and event handlers to achieve this:
 
 ```php
 use Tempest\EventBus\StopsPropagation;