diff --git a/manage/ai/providers/custom/ollama.mdx b/manage/ai/providers/custom/ollama.mdx
index c45592d..27f4ed9 100644
--- a/manage/ai/providers/custom/ollama.mdx
+++ b/manage/ai/providers/custom/ollama.mdx
@@ -13,7 +13,7 @@ See [Capabilities](/manage/ai/providers/configuration#capabilities) for the full
 
 ## Configure
 
-1. Sidebar → **AI Gateway** → **Providers** → **Create**.
+1. Sidebar > **AI Gateway** > **Providers** > **Create**.
 2. Set **Provider Type** to **Custom** and give it a name.
 3. Select **OpenAI Chat Completions**.
 4. Set **Routing Mode** to **Site Targets** if Ollama runs on a site's network. Use **Upstream URL** (`http://<host>:11434`) only when the Pangolin node can reach Ollama directly.
diff --git a/manage/ai/providers/vertex-ai.mdx b/manage/ai/providers/vertex-ai.mdx
index 60e087e..e430d70 100644
--- a/manage/ai/providers/vertex-ai.mdx
+++ b/manage/ai/providers/vertex-ai.mdx
@@ -21,7 +21,7 @@ Vertex Generate Content covers Gemini-format calls on Vertex. Vertex Raw Predict
 
 ## Configure
 
-1. Sidebar → **AI Gateway** → **Providers** → **Create**.
+1. Sidebar > **AI Gateway** > **Providers** > **Create**.
 2. Set **Provider Type** to **Vertex AI**. Capabilities and auth type fill in from the defaults above.
 3. Set **Upstream URL** to your regional Vertex host, for example `https://us-central1-aiplatform.googleapis.com`. The host includes the location.
 4. Paste a Bearer credential the Vertex endpoint accepts (typically a Google OAuth access token).
diff --git a/manage/ai/session-logs.mdx b/manage/ai/session-logs.mdx
index 669be07..6b7fcbd 100644
--- a/manage/ai/session-logs.mdx
+++ b/manage/ai/session-logs.mdx
@@ -3,7 +3,7 @@ title: "AI Session Logs"
 description: "Prompt and response transcripts for AI Gateway requests in an organization"
 ---
 
-Session logs store the prompt and response for each AI Gateway call. Open **AI Gateway → Session Logs** to browse them. Use them to see what a client sent, what the upstream returned, and which user, key, provider, and resource handled the call.
+Session logs store the prompt and response for each AI Gateway call. Open **AI Gateway > Session Logs** to browse them. Use them to see what a client sent, what the upstream returned, and which user, key, provider, and resource handled the call.
 
 <Frame>
   <img src="/images/ai/session-logs.png" alt="AI Gateway session logs table in the Pangolin dashboard" centered />
@@ -54,3 +54,7 @@ Narrow the table by date range, then:
 ## Export
 
 Export the current filters as CSV from the table, the same way as other organization logs.
+
+## Streaming
+
+Session logs can be streamed (like all other logs) to upstream SIEM providers or other data sources. You can set this up following the [streaming](/manage/analytics/streaming) documentation.
\ No newline at end of file
diff --git a/manage/analytics/streaming.mdx b/manage/analytics/streaming.mdx
index b764de9..fe64a34 100644
--- a/manage/analytics/streaming.mdx
+++ b/manage/analytics/streaming.mdx
@@ -3,8 +3,6 @@ title: "Event Streaming"
 description: "Stream Pangolin log events to external collectors and SIEM tools"
 ---
 
-
-
 Log streaming forwards your organization's audit logs to external data collectors such as Datadog, Splunk, Microsoft Sentinel, Elastic, or any HTTP endpoint you operate. You add a **destination** (how events are delivered), choose which **log types** to include, and Pangolin pushes new events as they are recorded.
 
 <Note>
@@ -13,7 +11,7 @@ Event streaming is only available in [Pangolin Cloud](https://app.pangolin.net/a
 
 ## In the dashboard
 
-Open **Organization → Logs & Analytics → Streaming** to add destinations and monitor delivery status. Each destination has its own connection settings, optional body customization (where supported), and log-type selection.
+Open **Organization > Logs & Analytics > Streaming** to add destinations and monitor delivery status. Each destination has its own connection settings, optional body customization (where supported), and log-type selection.
 
 ## Log types
 
diff --git a/self-host/how-to-update.mdx b/self-host/how-to-update.mdx
index 621c0a2..9497933 100644
--- a/self-host/how-to-update.mdx
+++ b/self-host/how-to-update.mdx
@@ -11,7 +11,7 @@ Updating Pangolin is straightforward since it's a collection of Docker images. S
 </Warning>
 
 <Tip>
-**Recommended**: Update incrementally between major versions. For example, update from 1.0.0 → 1.1.0 → 1.2.0 instead of jumping directly from 1.0.0 → 1.2.0.
+**Recommended**: Update incrementally between major versions. For example, update from 1.0.0 > 1.1.0 > 1.2.0 instead of jumping directly from 1.0.0 > 1.2.0.
 </Tip>
 
 ## Update Process