diff --git a/pages/docs/concepts/observability.mdx b/pages/docs/concepts/observability.mdx
index 9d2d4bd..59ce32c 100644
--- a/pages/docs/concepts/observability.mdx
+++ b/pages/docs/concepts/observability.mdx
@@ -16,8 +16,6 @@ In practice, this can include:
 
 Rig focuses primarily on **structured traces and logs** via the [`tracing`](https://docs.rs/tracing) ecosystem.
 
----
-
 ## What observability gives you in Rig
 
 Rig emits structured telemetry that allows you to:
@@ -34,8 +32,6 @@ Rig follows the [**OpenTelemetry GenAI Semantic Conventions**](https://opentelem
 - [Arize Phoenix](https://phoenix.arize.com/)
 - Other OpenTelemetry-compatible backends
 
----
-
 ## The easiest way to get started (recommended)
 
 If you just want to _see what Rig is doing_, the fastest path is **Langfuse**.
@@ -81,8 +77,6 @@ fn init_tracing() {
 
 Once this is set up, model calls, agent invocations, multi-turn agent loops and tool executions will automatically appear in the Langfuse UI.
 
----
-
 ## Agent span naming and customisation
 
 By default, agent spans use a generic name such as `invoke_agent`.
@@ -96,8 +90,6 @@ However, Rig attaches attributes like:
 
 You can use these attributes to rename spans **in your observability backend**.
 
----
-
 ## Setting up an OpenTelemetry Collector (advanced)
 
 You only need an OpenTelemetry Collector if:
@@ -135,8 +127,6 @@ This configuration:
 - Renames agent spans using their agent name
 - Exports traces to Langfuse
 
----
-
 ## I don’t want spans, just logs
 
 That’s completely fine.
@@ -198,8 +188,6 @@ tracing_subscriber::registry()
     .init();
 ```
 
----
-
 ## Troubleshooting
 
 - **Spans appear out of order**