Living document · continuously updated

Errata & Community Corrections

Help us keep the book accurate — report typos, broken links, stale facts, or suggest improvements

All errata is tracked publicly at github.com/thebackendofluck/book. Every accepted correction ships in the next revision with attribution to the reporter.

bug_report Open GitHub Issue edit_note Submit via Form
Why it matters

Technical books are living artifacts

auto_stories

Scale of the book

At 844K words spanning 47 chapters, 2,581+ scripts, and 397 diagrams, the surface area for subtle errors is large. Internal review catches the obvious ones — community review catches the rest.

update

The world keeps moving

Regulatory frameworks evolve (new gambling laws, SIGAP updates, UKGC rule changes), third-party APIs deprecate endpoints, CVEs get patched, and library versions drift. Facts that were accurate at publication may not be accurate today.

groups

Community multiplier

Every accepted correction ships in the next revision with full attribution to the reporter. Your expertise helps every future reader — and your name goes in the changelog.

Two ways to contribute

How to submit a correction

Choose the channel that works best for you. All paths lead to the same review queue.

Recommended
bug_report

Option 1 — GitHub Issue

For typos, factual errors, broken links, and code bugs. The fastest path to a fix — issues are typically triaged within 48 hours.

  • ✓ Typos & grammar
  • ✓ Factual / technical errors
  • ✓ Broken links
  • ✓ Code bugs in scripts
  • ✓ Outdated regulatory info
open_in_new Open Issue on GitHub
edit_note

Option 2 — Inline Form

Submit directly from this page. The form pre-fills a GitHub issue with your details so review is seamless.

  • ✓ Guided field selection
  • ✓ Optional name & email
  • ✓ No copy-paste required
arrow_downward Go to Form Below
Inline submission

Submit a correction

Clicking "Preview & Submit" will open a pre-filled GitHub issue in a new tab. You can review and edit it before posting. A free GitHub account is required to submit the issue itself.

Submitting opens a pre-filled GitHub issue in a new tab. A free GitHub account is needed to post the issue.

Live from GitHub

Current status

Stats fetched live from the GitHub API. Refresh the page to update.

—
Open issues
—
Closed this month
—
Releases published
—
Contributors
open_in_new View full tracker on GitHub | new_releases Release history
Process

How corrections are processed

From report to published fix, every correction follows the same transparent pipeline.

send
Report submitted
GitHub or form
bug_report
Issue created
Labelled & queued
manage_search
Editor triage
SLA: 48 hours
verified
Author verifies
Confirmed or closed
merge
Fix PR merged
With attribution
new_releases
Revision published
Monthly / quarterly
timer
Triage SLA
48 hours for initial response
calendar_month
Revision cadence
Monthly minor / quarterly major
attribution
Attribution
Every reporter credited by default
Changelog

Recent errata releases

Loading release history from GitHub…

Attribution

Crediting contributors

Every accepted errata reporter is added to the public "Contributors" list in the book's revision history. You can opt to stay anonymous — just note it in your submission.

If you submitted via a GitHub issue, your GitHub username is automatically linked in the fix PR, giving you a permanent public record of the contribution. Each revision's changelog explicitly lists who reported what.

There is no monetary reward — the incentive is accuracy, attribution, and the knowledge that your correction will help every reader who comes after you.

Recent contributors

person Waiting for first community corrections — be the first!

add_circle Submit your correction
Common questions

Frequently asked questions

Only if you choose. The default is anonymous. If you want attribution, include your name or GitHub username in the submission. To stay anonymous, leave the name field blank or write "anonymous".
No monetary reward is offered. The incentive is public credit in the revision history and the satisfaction of helping every future reader. All accepted corrections receive a response and changelog mention.
Yes — use the "Suggestion / improvement" type in the form or issue template. These go into a separate backlog reviewed during each quarterly planning cycle. We cannot commit to adding every suggestion, but everything is read and considered.
Submit in either language — Portuguese or English are both fine. We translate internally before applying the fix to the canonical English text. The portrasdasorte.com.br site mirrors errata updates alongside the English edition.
If you submitted via GitHub issue, you will receive a notification when the issue is closed with a "fixed" label and linked PR. All accepted fixes also appear in the release notes of the next revision.
Help keep it accurate

Found something?

Open a GitHub issue in under two minutes. Your correction will ship in the next revision with your name in the changelog.

bug_report Open an Issue on GitHub

github.com/thebackendofluck/book