feat: update faucet docs

[SpectreMercury]

Summary by CodeRabbit

Release Notes

• Documentation
  • Simplified the faucet guide with streamlined instructions for token claiming. Condensed extensive guidance content to provide a clearer, more direct process for obtaining tokens.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request simplifies the faucet setup documentation by replacing an extensive multi-section guide with a streamlined Morph Faucet usage flow. The change removes detailed instructions for third-party faucets, wallet addresses, and bridging procedures while retaining essential claiming steps.

Changes

Cohort / File(s)	Summary
Documentation Update docs/quick-start/3-faucet.md	Replaces detailed faucet guide (Hoodi faucet, Discord faucet, addresses, bridging instructions) with simplified Morph Faucet section describing claim flow and token delivery timeline. Net change: +7/-73 lines.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Narrative change + more Holesky to Hoodi changes #97 — Removes faucet images from the same file, complementing this content simplification.
• Holesky to Hoodi update to Faucet & Bridge #96 — Updates USDT addresses and Holesky→Hoodi references in the same faucet documentation file.

Suggested reviewers

• secmgt

Poem

🐰 The faucet guide now flows so clean,
Detailed clutter swept away serene,
Three simple steps, no more, no less,
Morph tokens falling—pure success! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: update faucet docs' is directly related to the changeset, which simplifies the faucet documentation by replacing a multi-section guide with a streamlined Morph Faucet usage section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@docs/quick-start/3-faucet.md`:
- Line 16: Update the vague instruction "Click to claim testnet tokens" to
specify the exact UI element or button label users should interact with (for
example, replace that sentence with "Click the 'Claim' button" or "Click the
'Claim Testnet Tokens' button" depending on the actual label), so readers know
precisely which control to click; locate the text "Click to claim testnet
tokens" in the 3-faucet.md content and replace it with the clearer button-label
instruction.
- Around line 8-18: Update the "## Morph Faucet" section to include operational
details: state the typical token amount dispensed per claim (e.g., "X test
tokens per claim"), the rate limit (e.g., "one claim per 24 hours" or the actual
limit enforced), and a short troubleshooting subsection with steps such as
verifying the correct wallet address, checking network explorers for pending
transactions, waiting a few minutes, and contacting support/raising an issue if
tokens don't arrive. Reference the "Morph Faucet" header and add a brief
"Troubleshooting" bullet list so users can immediately see token amount, rate
limits, and next steps if a claim fails.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for network setup, wallet configuration, and faucet-related documentation

echo "=== Searching for network configuration docs ==="
fd -e md -e mdx . docs/ | xargs rg -l "Morph.*Holesky|network.*add|add.*network|wallet.*setup|RPC.*endpoint" 2>/dev/null | head -20

echo ""
echo "=== Searching for faucet or testnet token references ==="
fd -e md -e mdx . docs/ | xargs rg -l "faucet|testnet.*token|claim.*token" 2>/dev/null | head -20

echo ""
echo "=== Listing quick-start directory structure ==="
fd -e md -e mdx . docs/quick-start/ 2>/dev/null | sort

echo ""
echo "=== Checking for troubleshooting or FAQ docs ==="
fd -e md -e mdx . docs/ | xargs rg -l "troubleshoot|FAQ|error|fail" 2>/dev/null | grep -i -E "(trouble|faq|error|help)" | head -10

Repository: morph-l2/morph-doc

Length of output: 1653

---

🏁 Script executed:

#!/bin/bash
# Check wallet-setup doc for Morph Holesky network configuration
echo "=== Content of wallet-setup.md (lines 1-60) ==="
head -60 docs/quick-start/2-wallet-setup.md

echo ""
echo "=== Checking for 'Morph Holesky' or 'network' in wallet-setup ==="
rg "Morph.*Holesky|add.*network|network.*config" docs/quick-start/2-wallet-setup.md -A 3 -B 1

echo ""
echo "=== Checking FAQ for faucet-related content ==="
rg "faucet|claim.*token|testnet.*token" docs/about-morph/7-faqs.md -A 3 -B 1

echo ""
echo "=== Checking if there's rate limiting or token amount info elsewhere ==="
rg "rate.*limit|token.*limit|amount.*claim|daily.*claim" docs/ -l 2>/dev/null | head -5

Repository: morph-l2/morph-doc

Length of output: 4083

---

Simplification is appropriate given the sequential documentation flow, but add operational details.

The wallet setup prerequisites are already covered in the preceding document (2-wallet-setup.md), which users complete before reaching the faucet step. However, consider adding practical information that users may encounter:

• Token amount: How many testnet tokens are dispensed per claim?
• Rate limits: How often can users claim (e.g., once per 24 hours)?
• Troubleshooting: What should users do if the claim fails or tokens don't arrive?

These details would make the documentation more self-sufficient without requiring users to discover this information through trial and error.

🤖 Prompt for AI Agents

In `@docs/quick-start/3-faucet.md` around lines 8 - 18, Update the "## Morph
Faucet" section to include operational details: state the typical token amount
dispensed per claim (e.g., "X test tokens per claim"), the rate limit (e.g.,
"one claim per 24 hours" or the actual limit enforced), and a short
troubleshooting subsection with steps such as verifying the correct wallet
address, checking network explorers for pending transactions, waiting a few
minutes, and contacting support/raising an issue if tokens don't arrive.
Reference the "Morph Faucet" header and add a brief "Troubleshooting" bullet
list so users can immediately see token amount, rate limits, and next steps if a
claim fails.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Make the claim instruction more specific.

The instruction "Click to claim testnet tokens" is vague. Users would benefit from knowing the exact button label or element to interact with (e.g., "Click the 'Claim' button").

📝 Suggested improvement

-3. Click to claim testnet tokens.
+3. Click the "Claim" button to receive testnet tokens.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	3. Click to claim testnet tokens.
	3. Click the "Claim" button to receive testnet tokens.

🤖 Prompt for AI Agents

In `@docs/quick-start/3-faucet.md` at line 16, Update the vague instruction "Click
to claim testnet tokens" to specify the exact UI element or button label users
should interact with (for example, replace that sentence with "Click the 'Claim'
button" or "Click the 'Claim Testnet Tokens' button" depending on the actual
label), so readers know precisely which control to click; locate the text "Click
to claim testnet tokens" in the 3-faucet.md content and replace it with the
clearer button-label instruction.