Use as evidence about visitor interpretation, not as proof that a tour presents a complete or neutral history.
The book's methodological statement explaining why visitor experience is central to its selection and interpretation of distilleries.
Harrison argues that the value of visiting a distillery is the opportunity to see where, why, and by whom whisky is made, and to understand the place and people that a process-only description leaves out.
Displayed p. 10 / complete PDF sheet 19
Displayed p. 10 / complete PDF sheet 18
Introduction > What makes a good whisky distillery trip?
Text and rendered page reverified 2026-08-29 in the complete 571-sheet edition; legacy partial PDF sheet 17 is retained for provenance.
Capture evidence faithfully. Select one Source, record a usable locator, and preserve enough surrounding context to prevent misquotation.
Evidence
Paste the exact quote, paraphrase, statistic, definition, or source claim into Excerpt Text. Use Excerpt Type to distinguish quotation from interpretation.
Location and context
Record Locator Type, Locator Start, Locator End when needed, and Source Section. Explain the surrounding argument in Context.
Annotation
In Annotation, state why this evidence matters. Add approved Tags for retrieval and connect it to every relevant Literature Note.
Verification checklist
Fresh supplied-copy evidence audit
PDF 18–19, displayed 10: supports Harrison’s argument for visiting people and places as well as observing equipment. It does not establish that visits reveal a complete, neutral account or improve measured learning outcomes.
This excerpt was checked against the newly completed sequential text and visual review of the 571-screen supplied PDF (SHA256 f7b627c3dedd2ac73908bac5def6723630feeace626330086fcec53e830ab932). The locator is supported independently of whole-copy completeness. Use the supplied PDF screen number alongside the displayed page; retained partial-copy locators refer to a different file. Verification concerns fidelity to this source, not independent truth of its claims. Existing relationships and legacy provenance are preserved. API read-back is separate from browser rendering.