diff --git a/src/assets/staging_patches_change_track_dropdown.png b/src/assets/staging_patches_change_track_dropdown.png
index 0f52f215..9a67e65f 100644
Binary files a/src/assets/staging_patches_change_track_dropdown.png and b/src/assets/staging_patches_change_track_dropdown.png differ
diff --git a/src/assets/staging_patches_patch_context_menu.png b/src/assets/staging_patches_patch_context_menu.png
index 64cf74bb..7ef2ea06 100644
Binary files a/src/assets/staging_patches_patch_context_menu.png and b/src/assets/staging_patches_patch_context_menu.png differ
diff --git a/src/content/docs/code-push/guides/staging-patches.mdx b/src/content/docs/code-push/guides/staging-patches.mdx
index b6bcf5bc..779bec4a 100644
--- a/src/content/docs/code-push/guides/staging-patches.mdx
+++ b/src/content/docs/code-push/guides/staging-patches.mdx
@@ -9,6 +9,12 @@ import { CodeTabs, LinkCard } from 'starlight-theme-nova/components';
import { Image } from 'astro:assets';
import goLive from '~/assets/staging_patches_change_track_dropdown.png';
import switchTrack from '~/assets/staging_patches_patch_context_menu.png';
+import ArcadeEmbed from '~/components/ArcadeEmbed.astro';
+
+
This guide will walk you through how to validate a patch in Shorebird's staging
environment before promoting the patch to production.
diff --git a/src/content/docs/code-push/tracks.mdx b/src/content/docs/code-push/tracks.mdx
index c8f7f005..1e96e991 100644
--- a/src/content/docs/code-push/tracks.mdx
+++ b/src/content/docs/code-push/tracks.mdx
@@ -8,6 +8,7 @@ sidebar:
---
import { CodeTabs, LinkCard } from 'starlight-theme-nova/components';
+import ArcadeEmbed from '~/components/ArcadeEmbed.astro';
**Tracks** are named deployment channels that control which devices receive a
patch. Every Shorebird app has a built-in `stable` track, which is the default
@@ -51,6 +52,11 @@ for your team.
## Publishing a patch to a track
+
+
Pass the `--track` flag to any `shorebird patch` command. If you omit the flag,
the patch is published to `stable` by default.