diff --git a/.gitbook/assets/bamboo.png b/.gitbook/assets/bamboo.png
new file mode 100644
index 00000000..2a497ccc
Binary files /dev/null and b/.gitbook/assets/bamboo.png differ
diff --git a/.gitbook/assets/google-cloud-build.png b/.gitbook/assets/google-cloud-build.png
new file mode 100644
index 00000000..1a3bd9dd
Binary files /dev/null and b/.gitbook/assets/google-cloud-build.png differ
diff --git a/flaky-tests/detection.md b/flaky-tests/detection.md
index 6e0f9fad..edfaf19b 100644
--- a/flaky-tests/detection.md
+++ b/flaky-tests/detection.md
@@ -107,14 +107,14 @@ Trunk classifies all tests into one of three categories based on the history of
 
 ### How Trunk detects broken tests
 
-Threshold monitors detect broken tests alongside flaky tests. When a test's failure rate exceeds the configured threshold and the failures are consistent rather than intermittent, Trunk classifies the test as **Broken** instead of **Flaky**.
+[Threshold monitors](dashboard.md#monitors) detect broken tests alongside flaky tests. When a test's failure rate exceeds the configured threshold and the failures are consistent rather than intermittent, Trunk classifies the test as **Broken** instead of **Flaky**.
 
 The key difference is the failure pattern:
 
 * **Flaky**: Failures are intermittent — the test sometimes passes and sometimes fails on the same code.
 * **Broken**: Failures are consistent — the test fails reliably above the threshold without intermittent passes.
 
-Broken detection events appear in the test case detail view alongside flaky detection events. In the events panel, broken events are displayed as a distinct series so you can track when tests transition between healthy, flaky, and broken states.
+Broken detection events appear in the test case detail view alongside flaky detection events. In the events panel, broken and flaky events are shown as separate series so you can track when tests transition between healthy, flaky, and broken states.
 
 {% hint style="info" %}
 A test can transition between states over time. For example, a test might start as healthy, become flaky as a race condition surfaces, and eventually be classified as broken if the underlying issue causes consistent failures.
diff --git a/flaky-tests/get-started/ci-providers/atlassian-bamboo.md b/flaky-tests/get-started/ci-providers/atlassian-bamboo.md
index 75276aea..eec48cd6 100644
--- a/flaky-tests/get-started/ci-providers/atlassian-bamboo.md
+++ b/flaky-tests/get-started/ci-providers/atlassian-bamboo.md
@@ -128,7 +128,7 @@ variables:
 ```
 {% endtab %}
 
-{% tab title="XCode" %}
+{% tab title="Xcode" %}
 ```yaml
 version: 2
 plan:
diff --git a/merge-queue/integration-for-slack.md b/merge-queue/integration-for-slack.md
index 217581fc..b313ce5a 100644
--- a/merge-queue/integration-for-slack.md
+++ b/merge-queue/integration-for-slack.md
@@ -80,7 +80,7 @@ To receive personal Slack notifications, you'll need to connect both your GitHub
 
 The Trunk Slack app's **Home** tab provides a personal merge queue dashboard directly in Slack. Open the Trunk app in Slack and click the **Home** tab to see an overview of your merge queue activity.
 
-### What you'll see
+### What You'll See
 
 The Home tab displays the following sections:
 
@@ -93,13 +93,13 @@ The Home tab displays the following sections:
 
 Each PR entry shows the PR title, number, a link to the Trunk dashboard, and a link to the GitHub PR. All data is scoped to your PRs via your linked GitHub account.
 
-### Linking your account
+### Linking Your Account
 
 1. Open the Trunk app in Slack and go to the **Home** tab
 2. Click **Link Account** to connect your Trunk account
 3. Click **Connect GitHub** to link your GitHub account (required for PR tracking and most notifications)
 
-### Managing notification preferences
+### Managing Notification Preferences
 
 You can toggle notification topics on or off directly from the Home tab — no need to visit the Trunk web UI. Changes take effect immediately. The available topics are the same as those listed in [Available Notification Topics](integration-for-slack.md#available-notification-topics).
 
diff --git a/merge-queue/reference/merge.md b/merge-queue/reference/merge.md
index c068c4e6..4448117b 100644
--- a/merge-queue/reference/merge.md
+++ b/merge-queue/reference/merge.md
@@ -180,7 +180,7 @@ Use these endpoints to create, configure, and manage merge queues. Each queue ta
 {% endopenapi-operation %}
 
 {% hint style="warning" %}
-The queue must be empty before it can be deleted. Cancel or merge all enqueued PRs first.
+The queue must be empty before it can be deleted. Cancel all enqueued PRs or wait for them to be merged first.
 {% endhint %}
 
 {% openapi-operation spec="trunk-api" path="/getQueue" method="post" %}
diff --git a/merge-queue/using-the-queue/monitor-queue-status.md b/merge-queue/using-the-queue/monitor-queue-status.md
index 75d0b506..407c0800 100644
--- a/merge-queue/using-the-queue/monitor-queue-status.md
+++ b/merge-queue/using-the-queue/monitor-queue-status.md
@@ -41,7 +41,9 @@ View status of the queue and recent activity in the **Queue** tab
 
 ### Graph view
 
-The graph view shows all PRs currently being tested by Trunk Merge Queue and their relationships. Each node represents a pull request, and each edge indicates that the PR is testing with the item above and depends on it. All edges point towards the target branch; as items merge, the affected queues restructure. If running in `Single` mode, this will be a single line showing the testing and merging process.
+The graph view shows all PRs currently being tested by Trunk Merge Queue and their relationships. Each node represents a pull request, and each edge indicates that the PR is testing with the item above and depends on it. All edges point towards the target branch; as items merge, the affected queues restructure.
+
+If running in `Single` mode, this will be a single line showing the testing and merging process.
 
 #### Reading the graph