Fixes the conflicting primary-channel naming guidance that was breaking interoperability for new users (flagged in the EF Meshtastic Discord thread).
The problem: the site gave three different names for the primary channel. The QR encodes it unnamed, the manual-entry table told people to name it "Primary", and Step 7 displayed it as "Primary Channel". Channels with different names do not see each other even on the same key, so this confused people and broke connectivity.
What changed:
- The recommended setup is now to leave the primary channel name BLANK, which is exactly what the EF QR already does (verified by decoding the share payload: channel 0 carries the default key and no name field).
- Explained the per-app auto-naming so the behavior is no longer surprising: with a blank name, iOS displays "Primary channel" and Android displays "MediumFast". Both are the same blank/default channel and interoperate fine. The blank name is what matters, not the label.
- If a user insists on setting a name manually, the guidance now says to type exactly "MediumFast" (no space, exact capitalization), and to never type "Primary" or "Primary Channel" (those are just iOS's display label and will not connect to the mesh).
- Reconciled the QR, the manual-entry table, Step 7, and the recommended-settings channel tables so they are all consistent with the blank-name reality. Kept the separate Channel Role = Primary field (distinct from the name) and clarified that it is fine.
Pages updated: How to Connect, Recommended Settings.