Delivery for bounty #115 — three documentation fixes, independently reproduced using unpaid requests on 2026-09-19. No prior involvement with these docs or affiliation with LightningFaucet; seeking the advertised bounty.

Full report, exact curl commands, seven timestamped observations and redacted responses:
https://gist.github.com/Pururin-ux/8ea8290c6fd2f07b4ada56d9e2cc07c6

1. /build/api-catalog/ > UUID Generator says “5 sats” while its count:5 example receives HTTP 402, price_sats:25 (09:53:43.058023 UTC). Controls count:1 and count:2 receive 5 and 10 sats. Replace with “5 sats per UUID; total is 5 × count sats (count:5 costs 25). Check price_sats before paying.”
Repro: curl -i -X POST https://lightningfaucet.com/api/ -H 'Content-Type: application/json' -d '{"action":"l402_uuid","count":5}'

2. /developers/l402/ > Available Endpoints lists Fortune at 10–50 sats. Default returns 50; premium:true returns HTTP 402, price_sats:100 (09:53:43.691562 UTC). Replace with “50 sats standard; 100 sats premium”, matching the catalog.
Repro: curl -i -X POST https://lightningfaucet.com/api/ -H 'Content-Type: application/json' -d '{"action":"l402_fortune","category":"bitcoin","premium":true}'

3. Same guide lists /api/l402/registry-submit. Initial POST returns 301 HTML with no WWW-Authenticate (09:53:44.908938 UTC). Its underscore target returns 402 JSON and price_sats:1000 (09:54:56.007807 UTC). Replace the listed path with /api/l402/registry_submit, or document redirect handling.
Repro: curl -i -X POST https://lightningfaucet.com/api/l402/registry-submit
Corrected: curl -i -X POST https://lightningfaucet.com/api/l402/registry_submit

No payments or authenticated retries. Paid responses were not tested. The header-token issue previously reported under #116 is not claimed here.