diff --git a/apps/docs/content/troubleshooting/download-logical-backups.mdx b/apps/docs/content/troubleshooting/download-logical-backups.mdx
index 326478529e1..a2de237d67a 100644
--- a/apps/docs/content/troubleshooting/download-logical-backups.mdx
+++ b/apps/docs/content/troubleshooting/download-logical-backups.mdx
@@ -6,8 +6,8 @@ github_url = "https://github.com/orgs/supabase/discussions/33045"
 database_id = "91ae4c49-bf22-4b8c-b96b-cd11f1c38158"
 ---
 
-When Point-in-Time Recovery (PITR) or physical backups are enabled, Supabase no longer generates the downloadable logical backup file (backup.gz). This is expected, as the backup pipeline switches entirely to physical backups. You can still download backups via the Supabase CLI command `pgdump`.
+When Point-in-Time Recovery (PITR) or physical backups are enabled, Supabase no longer generates the downloadable logical backup file (backup.gz). This is expected, as the backup pipeline switches entirely to physical backups. You can still download backups via the [Supabase CLI `db dump` command](/docs/reference/cli/supabase-db-dump) or using [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html).
 
-For step-by-step instructions, check out our guide: [Backup & Restore](/docs/guides/platform/migrating-within-supabase/backup-restore).
+For step-by-step instructions using the Supabase CLI, check out the [Backup database using the CLI](/docs/guides/platform/migrating-within-supabase/backup-restore#backup-database-using-the-cli) guide.
 
 You can also learn more about how backups work in Supabase here: [Database Backups](/docs/guides/platform/backups).