docs: update FAQ RPC provider text for self-custodial wallet connections

[devin-ai-integration]

Description

Updates the "Using your own RPC provider?" paragraph in the FAQ entry "Is there a limit on self-custodial wallet connections?" with improved copy that:

• Clarifies the RPC threshold "likely" won't apply rather than stating it definitively doesn't
• Notes that some RPC usage may still occur (e.g., fetching user balances)
• Reframes the fair use clause around concrete examples (spike attacks, sustained automated abuse) rather than abstract terms
• Emphasizes that normal app traffic is not a concern

Follow-up polish: Removed repeated "Likely" for a more confident tone, and fixed possessive users' (was missing apostrophe).

Human review checklist

• Verify the updated wording reads naturally in context of the full FAQ accordion
• Note: the pre-existing broken link (ttps:// missing the h) in the same FAQ entry was not touched by this PR

Tests

• Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
• Ran a grammar check on the updated/created content using ChatGPT.

Direct links to the deployed changes in Mintlify

• FAQ page – "Is there a limit on self-custodial wallet connections?"

Link to Devin session: https://app.devin.ai/sessions/4d59f32283d040fda3b77feebd2b1fef

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

Claude finished @devin-ai-integration[bot]'s task in 49s —— View job

---

🤖 Auto Review

• Gather context
• Read tone of voice guide
• Review changed file
• Post findings

---

Found 2 issue(s)

Issue 1: Missing possessive apostrophe — "users balances"

ID: faq-grammar-apostrophe-a3f1
File: appkit/faq.mdx:166
Severity: LOW
Category: code_quality

Context:

• Pattern: "RPC usage may still occur from time to time to fetch users balances"
• Risk: Grammatically incorrect — "users" here is possessive, not plural
• Impact: Reduces documentation quality and trust

Recommendation:

fetch users' balances

---

Issue 2: Repeated word "Likely" in consecutive sentences weakens tone

ID: faq-tone-likely-repetition-b2c4
File: appkit/faq.mdx:166
Severity: LOW
Category: code_quality

Context:

• Pattern: "The RPC threshold will likely not apply to you. … Likely the only limit that could apply…"
• Risk: Word repetition feels unpolished; also, the excessive hedging conflicts with Reown's "confident, but approachable" tone principle (docs should be professional and straightforward)
• Impact: Developers may feel less certain about what limits actually apply

Recommendation: Remove the second "Likely" or restructure:

The RPC threshold will likely not apply to you. RPC usage may still occur from time to time to fetch users' balances. The only limit that could apply is the general fair use clause in our ToS…