From c3fedf8e8c53b299c1f697e95ee55d16c5227fb3 Mon Sep 17 00:00:00 2001 From: Matthew Butterick Date: Fri, 7 Mar 2014 19:32:15 -0800 Subject: [PATCH] doc typo --- scribblings/decode.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scribblings/decode.scrbl b/scribblings/decode.scrbl index 641ae6e..88f77fa 100644 --- a/scribblings/decode.scrbl +++ b/scribblings/decode.scrbl @@ -119,7 +119,7 @@ Because it's convenient, Pollen categorizes tagged X-expressions into two catego void?] Adds a tag to @racket[project-block-tags] so that @racket[block-txexpr?] will report it as a block, and @racket[decode] will process it with @racket[_block-txexpr-proc] rather than @racket[_inline-txexpr-proc]. -@bold{Hey, this is important!} Pollen tries to do the right thing without being told. But this is the rare case where you have to be explicit. If you introduce a tag into your markup that you wanted treated as a block, you @bold{must} use this function to identify it, or you will get spooky behavior later on. +@bold{Hey, this is important!} Pollen tries to do the right thing without being told. But this is the rare case where you have to be explicit. If you introduce a tag into your markup that you want treated as a block, you @bold{must} use this function to identify it, or you will get spooky behavior later on. For instance, @racket[detect-paragraphs] knows that block elements in the markup shouldn't be wrapped in a @racket[p] tag. So if you introduce a new block element called @racket[bloq] without registering it as a block, misbehavior will follow: