[Registrar] Add FAQ entries for top support questions

[allan-leinwand]

Summary

Weaves the highest-volume Registrar support questions into the existing FAQ, reusing the page's question/answer format. Adds new entries for refunds, email verification/suspension, moving a domain between Cloudflare accounts, "charged but can't find my domain", pending transfers, and transfer billing/double charges. Enhances the existing contact-update and "why can't I transfer" answers with the 60-day Change of Registrant lock and .us/.uk notes.

Also lightly reorders within sections so the most common questions surface first, and fixes two pre-existing grammar issues.

Documentation checklist

• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.

[cloudflare-docs-bot]

Review

⚠️ 1 warning, 💡 2 suggestions found in commit f280a38.

👉 Fix in your agent 👈

Fix the following review findings in PR #32374 (https://github.com/cloudflare/cloudflare-docs/pull/32374).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Style Guide Review

### Warnings (1)

#### SG-7c44bc403e2f · Avoid directional words
- **File:** `src/content/docs/dns/nameservers/nameserver-options.mdx` line 16
- **Issue:** Uses "sections below"
- **Fix:** Replace "the sections below" with a direct reference, such as "the following sections" or name the section.

### Suggestions (2)

#### SG-a8769ea6d4cf · Use the Oxford comma for lists of three or more items
- **File:** `src/content/docs/registrar/faq.mdx` line 49
- **Issue:** Details that may be updated include name, email, address, organization and telephone number.
- **Fix:** Add a comma before "and": name, email, address, organization, and telephone number.

#### SG-3ef14624762e · Avoid LLM-filler phrases
- **File:** `src/content/docs/dns/nameservers/nameserver-options.mdx` line 16
- **Issue:** Uses "Note that" before "the availability of these options depends on your plan."
- **Fix:** Remove the filler phrase and state the fact directly: "The availability of these options depends on your plan."

Code Review

This code review is in beta and may not always be helpful — use your judgment.

_{No code review issues found.}

Conventions

_{No convention issues found.}

Style Guide Review

Warnings (1)

File	Issue
dns/nameservers/nameserver-options.mdx line 16	Avoid directional words — Uses "sections below" Fix: Replace "the sections below" with a direct reference, such as "the following sections" or name the section.

Suggestions (2)

File	Issue
registrar/faq.mdx line 49	Use the Oxford comma for lists of three or more items — Details that may be updated include name, email, address, organization and telephone number. Fix: Add a comma before "and": name, email, address, organization, and telephone number.
dns/nameservers/nameserver-options.mdx line 16	Avoid LLM-filler phrases — Uses "Note that" before "the availability of these options depends on your plan." Fix: Remove the filler phrase and state the fact directly: "The availability of these options depends on your plan."

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[allan-leinwand]

Verified the changes locally and they look good given the feedback on our FAQ page.

[allan-leinwand]

as an example, new billing section