Keep the offer identity beside the clause
A phone can show a bonus amount clearly while hiding its practical conditions several scrolls below. When reading Zora terms, keep the offer name and the relevant rule connected. A paragraph copied without its heading can belong to another category, edition or general account rule.
A large promotional amount and a small terms panel can draw attention unevenly on a phone. Begin by recording the offer title and category before scrolling into the detail. If the page opens another panel or tab, confirm that it still concerns the same campaign. A saved sentence without its heading can later be mistaken for a universal rule. The aim is to preserve enough context to understand who the clause applies to, what action it governs and when it takes effect.
Identify the document’s role
Begin by identifying the document you are reading. Is it the selected promotion's detail, the general bonus rules or the account terms? These texts can work together, but they answer different questions. Note any reference that makes another section part of the offer, then read that section before accepting.
Promotion details can describe the particular reward, general bonus conditions can explain wider restrictions, and account terms can address identity or payments. They may be connected without being interchangeable. Follow any explicit reference that makes another section applicable, then return to the original offer to see how the pieces fit. Do not assume that a brief Help summary contains every condition. It can provide a useful explanation while leaving a calculation base or an account-specific requirement to the detailed accepted offer.

Search within the page and read the surrounding rule
Use the browser's page search where it is available to locate specific terms such as expiry, stake, withdrawal or eligible games. Search is a navigation aid, not a substitute for surrounding sentences. A match for withdrawal could appear in an exception or an example, so read the whole clause and its heading.
Page search is useful for locating a word, but a highlighted match is only a starting point. Read the heading, complete sentence and any exception immediately before or after it. A match for maximum might concern a prize, a stake or a package ceiling, which are different limits. If the term is absent, try the wording actually used in the interface rather than concluding there is no restriction. Search should reduce navigation effort without stripping the clause of the context that determines its meaning.
Create a compact note without filling gaps by guesswork
For a compact personal note, record the qualifying action, bonus calculation, game restrictions, remaining requirement and deadline. Mark anything that is not stated. Do not fill a missing number with a value remembered from a different casino or another promotion. A precise unanswered question is more useful than a confident assumption.
For example, Zora’s welcome Help summary dated 18 August 2026 lists 35x for Slots, Instant and Live and 20x for Sports, but does not state the multiplication base in that short article. A personal note should therefore record the multiplier and mark the base unresolved until the selected offer supplies it. Do not invent a bonus-only or deposit-plus-bonus formula. This is a practical example of why a precise unanswered field is more useful than a complete-looking calculation built from an assumption.
Fix the reading view before acceptance
If text is clipped, a table scrolls horizontally or the confirmation covers a clause, change the view or use a larger screen before acceptance. The aim is not to make the document look small enough to fit all at once; it is to read the conditions accurately. Save the relevant version with its date when you proceed.
When a table extends beyond the screen, inspect its remaining columns rather than reading only the first visible amount. If an overlay covers the clause, close it or use a view that exposes the text before accepting. Increasing readability is more important than fitting every line on one screen. Save the relevant title, date and accepted version privately, then crop only unnecessary personal details when sharing a support question. A readable record should explain the rule, not merely show that a terms page was opened.