From f1a8900bbe9a3bb4bd61bbd20167bd40be2ddeb3 Mon Sep 17 00:00:00 2001
From: PLyn <plyn8750@gmail.com>
Date: Fri, 18 Jul 2025 20:05:24 -0500
Subject: [PATCH] fix lints

---
 .../content/guides/platform/migrating-within-supabase.mdx     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/apps/docs/content/guides/platform/migrating-within-supabase.mdx b/apps/docs/content/guides/platform/migrating-within-supabase.mdx
index 8ec89cd668b..cdcf8f98f57 100644
--- a/apps/docs/content/guides/platform/migrating-within-supabase.mdx
+++ b/apps/docs/content/guides/platform/migrating-within-supabase.mdx
@@ -12,7 +12,7 @@ to another project feature](/docs/guides/platform/clone-project).
 
 - **Project migration only migrates the Postgres database** and anything else will need to be re-configured.
 
-### Pre-Migration Checklist
+### Pre-Migration checklist
 
     <Accordion
 
@@ -154,7 +154,7 @@ If you already have the database backup, skip to the Restore project step.
 
 ### Migrate Storage
 
-The new project has the old project's Storage buckets, but the Storage objects need to be migrated manually. If you have your storage objects locally (eg 90 day paused projects), migrate the storage objects to the new project using this [google colab script](https://colab.research.google.com/github/PLyn/supabase-storage-migrate/blob/main/Supabase_Storage_migration.ipynb).
+The new project has the old project's Storage buckets, but the Storage objects need to be migrated manually. If you have your storage objects locally (e.g. 90 day paused projects), migrate the storage objects to the new project using this [Google Colab script](https://colab.research.google.com/github/PLyn/supabase-storage-migrate/blob/main/Supabase_Storage_migration.ipynb).
 
 If the old project is still active, use this script to move storage objects from one project to another: