Narrative and procedural close reading
Book Isle recipe-text checks: connect yield, ingredient lists and step quantities
Read recipe text for yield, divided quantities and step references, recording unspecified conditions without assuming an automatic formula calculator.
On this page
An ingredient list may give a total later divided across several steps, making repeated addition easy to misread. Check one recipe’s yield, ingredients and instructions in Book Isle as a textual task, without specific cooking, safety or dietary advice. Use the app for reading and notes and calculate in a personal log; no automatic recipe scaling is assumed.
Fix one edition and one recipe
Choose a recipe book you are entitled to read and record title, author, edition and target entry. Read heading, yield and preliminary notes fully. Start with one short recipe whose ingredient list is legible, without mixing an online variant into it. If tables flatten into running text, consult the original for column correspondence instead of guessing which number belongs to which ingredient. Keep the source and organise complex tables externally if necessary. The task is interpreting this page, not supplying unstated equipment, temperature or time; mark missing conditions unspecified.
Separate yield, total quantities and per-portion information
Record the stated yield exactly, distinguishing servings, item count and total mass rather than automatically interpreting a 2 as two people. Preserve ingredient name, value, unit and qualifiers such as extra, to taste or divided, with interpretation separately. Retain decimals and ranges instead of exact integers, and do not exchange grams and millilitres without a basis. Keep qualitative quantities rather than inventing numbers for tidy tables. Reread the list against the text before following steps so every later ingredient refers to one stable record instead of a remembered guess.
Mark each ingredient reference step by step
Read from step one, logging each ingredient’s step number, any stated amount and references to a remainder. An ingredient appearing in three steps does not mean adding its listed total three times. An invented textual example—10 grams of ingredient A divided into 4 and 6—can illustrate addition, explicitly not attributed to the book or used as an actual recipe. If a step names the ingredient without allocating quantity, mark it unresolved rather than dividing equally. Check separate garnish or finishing notes before calling an ingredient omitted merely because early steps do not mention it.
Check totals against divided quantities on paper
Where the text specifies divided amounts, add them in one unit and compare with the list total. A mismatch first calls for checking reserved portions, units and transcription. The invented 10=4+6 example agrees; a 4+8 record needs source investigation rather than silently assigning the discrepancy to the last step. Preserve approximations and ranges instead of claiming precise formula validation. This checks textual relationships, not flavour or a physical result. Record exact locations/numbers for genuine source questions and consult official errata when appropriate rather than overwriting the only source.
Keep yield scaling within its arithmetic limits
For a scaling exercise, use a separate arithmetic-only copy: explicitly change two portions to four, factor 2, and change a quantified 10 grams of ingredient A to 20 while preserving the original list. This invented example does not establish doubled heating time, container or process for any real recipe. A qualitative quantity cannot become an invented number, and undefined portions cannot yield a forced factor. Label the table personal arithmetic practice, separate from the author’s formula; this tutorial does not recommend cooking from it. Mathematical correspondence is distinct from verified practical conditions.
Record order and explicitly concurrent instructions
Mark explicit first, after, meanwhile and finally instructions and read their complete conditions rather than isolated actions. Waiting for a prior stage does not authorise arbitrary ingredient order, while two actions in one paragraph need not be simultaneous. An external table can hold step, input, prior reference and unspecified conditions, with app notes retaining sources. No timer, shopping-list or cooking mode is assumed; ordinary reading records suffice. Label personal reordering as inference rather than continuing to attribute it to the author.
Retrieve the original steps through ingredient records
Leave the page and use one divided-ingredient record to retrieve both list and relevant steps, rechecking name, unit and total/parts. Screen pages may shift with layout, so retain headings and short phrases. For unsearchable scans, inspect image pages rather than treating no search hit as no ingredient. Export important notes through available means and inspect table headings and step numbers externally, keeping the book separately. State the checked entry, mapped relationships and unresolved items; one-page checking does not certify the whole cookbook.
Check total-versus-part identity and table order first
For apparently doubled use, check whether totals and per-step amounts were added twice, then inspect table-column alignment. An ingredient in instructions but not the list needs note/subingredient review before inventing a new author entry. Leave time questions after scaling unresolved rather than applying the same factor. Preserve differing units until a reliable conversion basis exists instead of guessing from number size. Recheck list-to-steps and steps-to-list. Explain every quantified source and which practical conditions remain unassessed; textual organisation is not automatic recipe optimisation.
Related tutorials and sources
Check DOCX quality in Book Isle: verify table relationships and footnotes, Book Isle errata reading: match author corrections to your copy.
Sources checked on November 5, 2026: Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Capability scope follows the official App Store description and Apple public version lookup. These are exercises and checks you can perform, without a claim of step-by-step physical-device testing or verification in every target environment. Example content is instructional; follow the controls in your installed version.