chore: Pr review

Author: developerjamiu

docs/migration.mdx

@@ -25,7 +25,7 @@ If you need any further support, please contact us at contact@globe.dev and incl
 
 ---
 
-<h2 id="before-you-begin" style="scroll-margin-top: 6rem">Before You Begin</h2>
+<h2 id="before-you-begin" style="scroll-margin-top: 12rem">Before You Begin</h2>
 
 Take a moment to inventory what you are using on Globe. This will help you plan your migration.
 
@@ -51,7 +51,7 @@ Take a moment to inventory what you are using on Globe. This will help you plan
 
 ---
 
-<h2 id="part-1-migrating-dart-backend-deployments" style="scroll-margin-top: 6rem">Part 1: Migrating Dart Backend Deployments</h2>
+<h2 id="part-1-migrating-dart-backend-deployments" style="scroll-margin-top: 12rem">Part 1: Migrating Dart Backend Deployments</h2>
 
 Globe ran your Dart backend code in serverless containers. To move to another platform, you will need to containerize your application with Docker. The good news: Dart has official Docker support, and the process is straightforward regardless of which framework you use.
 
@@ -251,7 +251,7 @@ For a VPS deployment, the general process is:
 
 ---
 
-<h2 id="part-2-migrating-flutter-web-deployments" style="scroll-margin-top: 6rem">Part 2: Migrating Flutter Web Deployments</h2>
+<h2 id="part-2-migrating-flutter-web-deployments" style="scroll-margin-top: 12rem">Part 2: Migrating Flutter Web Deployments</h2>
 
 Flutter Web applications are static assets after building. This means you have many hosting options, and most of them are free or very affordable.
 
@@ -323,7 +323,7 @@ Alternatively, build locally and use the Vercel CLI: `vercel deploy build/web`
 
 ---
 
-<h2 id="part-3-migrating-jaspr-projects" style="scroll-margin-top: 6rem">Part 3: Migrating Jaspr Projects</h2>
+<h2 id="part-3-migrating-jaspr-projects" style="scroll-margin-top: 12rem">Part 3: Migrating Jaspr Projects</h2>
 
 Jaspr projects come in three modes, and each requires a different migration approach.
 
@@ -368,7 +368,7 @@ Note: Verify the exact build output paths for your Jaspr version. The compiled s
 
 ---
 
-<h2 id="part-4-migrating-custom-domains" style="scroll-margin-top: 6rem">Part 4: Migrating Custom Domains</h2>
+<h2 id="part-4-migrating-custom-domains" style="scroll-margin-top: 12rem">Part 4: Migrating Custom Domains</h2>
 
 If you connected a custom domain to your Globe project, here is how to point it to your new provider. Globe managed custom domains through Cloudflare DNS, so you previously added a CNAME record pointing to `domains.globeapp.dev`.
 
@@ -408,7 +408,7 @@ To minimize downtime, we recommend this sequence:
 
 ---
 
-<h2 id="part-5-migrating-globe-db-data" style="scroll-margin-top: 6rem">Part 5: Migrating Globe DB Data</h2>
+<h2 id="part-5-migrating-globe-db-data" style="scroll-margin-top: 12rem">Part 5: Migrating Globe DB Data</h2>
 
 Globe DB is powered by Turso, a distributed SQLite-compatible database built on libSQL. Your data is stored in Turso's infrastructure, and there are clear paths to export it.
 
@@ -442,7 +442,7 @@ sqlite3 my_local.db < my_data_dump.sql
 
 ---
 
-<h2 id="part-6-migrating-globe-kv-data" style="scroll-margin-top: 6rem">Part 6: Migrating Globe KV Data</h2>
+<h2 id="part-6-migrating-globe-kv-data" style="scroll-margin-top: 12rem">Part 6: Migrating Globe KV Data</h2>
 
 Globe KV is powered by Cloudflare Workers KV under the hood. KV data is stored as key-value pairs in a Cloudflare namespace.
 
@@ -482,7 +482,7 @@ wrangler kv bulk put kv_data.json --namespace-id=YOUR_NEW_NAMESPACE_ID
 
 ---
 
-<h2 id="migration-checklist" style="scroll-margin-top: 6rem">Migration Checklist</h2>
+<h2 id="migration-checklist" style="scroll-margin-top: 12rem">Migration Checklist</h2>
 
 Use this checklist to make sure you have covered everything.