This reference note uses Automaty81 as a named example for organising web reading and source notes. It describes a way to review information, not a recommendation to register, pay, or take part in an activity.
A short description can be convenient, but it does not replace checking the underlying page. Separate visible facts from interpretation and avoid treating a prominent heading as independent verification. When a detail depends on a version, language or date, keep that context alongside the note. This approach makes later comparisons more useful and reduces accidental overstatement.
The reference for this section is the Automaty81 website. Read the destination directly when a detail matters.
Use the same questions for each resource: what does it describe, which information is explicitly shown, and what remains unclear? Differences in wording do not necessarily mean differences in the underlying subject. A blank field should stay blank until a suitable source is available. Writing down uncertainty is more informative than filling a table with unsupported numbers.
For the original context, see Automaty81 reference. Read the destination directly when a detail matters.
A reference link should lead readers to the page discussed in the paragraph. Check the destination again when revising a note, because headings and navigation can change. Retain the distinction between a source statement and an independently confirmed result.
The retained reference is the page at automaty81.com. Read the destination directly when a detail matters.
Keep these notes concise, separate observation from inference, and revisit the source before reusing a detail in another document.