Clarify Sync tab intro copy to describe connecting existing sites

[wojtekn]

Related issues

• Fixes STU-1512

How AI was used in this PR

Claude Code located the Sync tab intro string, rewrote the copy, and ran lint + typecheck. The wording was reviewed by a human.

Proposed Changes

The Sync tab's introductory paragraph said "Launch your existing WordPress.com or Jetpack-activated Pressable sites, or import an existing one." This was misleading: you don't "launch" sites that already exist — the feature connects and syncs them, and "launch" implies creating something new. "or import an existing one" was also redundant with "your existing sites."

The copy now reads: "Connect your existing WordPress.com or Jetpack-activated Pressable sites to keep your local and live work in sync." This accurately describes what the feature does and matches the clarity of the bullet points below it (push/pull changes, staging/production support, database and file sync).

Testing Instructions

1. Open Studio and go to the Sync tab (when not yet authenticated/connected).
2. Confirm the intro paragraph reads "Connect your existing WordPress.com or Jetpack-activated Pressable sites to keep your local and live work in sync."

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wpmobilebot]

📊 Performance Test Results

Comparing a7819ce vs trunk

app-size

Metric	trunk	a7819ce	Diff	Change
App Size (Mac)	2341.17 MB	2341.17 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	a7819ce	Diff	Change
load	1074 ms	757 ms	317 ms	🟢 -29.5%

site-startup

Metric	trunk	a7819ce	Diff	Change
siteCreation	6492 ms	6495 ms	+3 ms	⚪ 0.0%
siteStartup	6484 ms	6978 ms	+494 ms	🔴 7.6%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[gavande1]

Nice. It looks much better. LGTM 👍

[katinthehatsite]

The changes look good and make sense 👍