From 0c478fa1c75d38e80709be51a6458b7471062d7f Mon Sep 17 00:00:00 2001 From: matiasz Date: Sat, 30 Dec 2017 08:25:49 -0800 Subject: [PATCH] Fix typo in docs for third tutorial --- pollen/scribblings/tutorial-third.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pollen/scribblings/tutorial-third.scrbl b/pollen/scribblings/tutorial-third.scrbl index c05d738..3ff6a10 100644 --- a/pollen/scribblings/tutorial-third.scrbl +++ b/pollen/scribblings/tutorial-third.scrbl @@ -88,7 +88,7 @@ In this tutorial, I'll be rendering Pollen markup with an HTML template. But you Pollen markup is a free-form markup system that lets you add arbitrary @defterm{tags} and @defterm{attributes} to your text. By arbitrary, I mean that you needn't constrain your tags to an existing specification (e.g., the tags permitted by HTML). You can — but that's an option, not a requirement. -I like to think of Pollen markup a way of capturing not just the text, but also my @bold{ideas about the text}. Some of these are low-level ideas (``this text should be italicized''). Some are high-level ideas (``this text is the topic of the page''). Some are just notes to myself. In short, everything I know about the text becomes part of the text. +I like to think of Pollen markup as a way of capturing not just the text, but also my @bold{ideas about the text}. Some of these are low-level ideas (``this text should be italicized''). Some are high-level ideas (``this text is the topic of the page''). Some are just notes to myself. In short, everything I know about the text becomes part of the text. In so doing, Pollen markup becomes the source code of the book. Let's try it out.