[BUG] README has a duplicate "Deploying to Vercel" section

[magic-peach]

Bug description
README.md has two separate ### Deploying to Vercel H3 sections — one at line 149 (with an "Option 1 / Option 2" structure and a vercel.json code block) and a near-duplicate one at line 215 (same two options, slightly different wording, its own vercel.json block). They're redundant and reader-confusing.

Steps to reproduce
grep -n "### Deploying to Vercel" README.md → two hits.

Expected behavior
One "Deploying to Vercel" section.

Actual behavior
Two, with drifting content (worth checking whether either has details the other lacks before merging them).

[github-actions]

👋 Thanks for opening an issue, @magic-peach!

Our maintainers will review this shortly 🚀

Before you start working

• 📖 Read the CONTRIBUTING.md guide
• 💬 Wait for a maintainer to assign you the issue before starting work
• 🔍 Search for existing issues to avoid duplicates

For GSSoC'26 contributors

If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

"I'd like to work on this — contributing under GSSoC'26"

Architecture notes

Reframe is a static Next.js app with output: "export". Key points:

• All video processing uses FFmpeg.wasm (client-side, no server)
• headers() in next.config.ts won't work — use vercel.json instead
• not-found.tsx requires public/404.html + vercel.json routes config

Happy contributing! ⭐ Star the repo if you find it useful!

[github-actions]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[SatvikMishra08]

/assign

[github-actions]

Hey @SatvikMishra08, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.

[github-actions]

Hey @SatvikMishra08, just a friendly reminder that this issue has had no activity for 2 days. Please leave an update or let us know if you need help! ⏰

[github-actions]

Hey @SatvikMishra08, final warning! ⚠️ This issue has had no activity for 4 days and will be automatically unassigned in 24 hours if there is no update.