Don't put AvgStateRemoved in a float.

Doing this completely foobarred the strikethrough...

diff --git a/Chapters/Prototype.tex b/Chapters/Prototype.tex
index 1d87eeb50ee1cc49644ba3d787cadc5d7947c1df..23168242ccc098c594b8ae291db2b80ccb04b5a8 100644 (file)
--- a/Chapters/Prototype.tex
+++ b/Chapters/Prototype.tex
@@ -1301,11 +1301,10 @@
 
       When applying these rules to the function \lam{avg} from
       \in{example}[ex:AvgStateNormal], we be left with the description
-      in \in{example}[ex:AvgStateRemoved]. All the parts that do not
-      generate any \VHDL\ directly are crossed out, leaving just the
-      actual flow of values in the final hardware. To illustrate the
-      change of the types of \lam{s} and \lam{s'}, their types are also
-      shown.
+      below. All the parts that do not generate any \VHDL\ directly are
+      crossed out, leaving just the actual flow of values in the final
+      hardware. To illustrate the change of the types of \lam{s} and \lam{s'},
+      their types are also shown.
       
       \startbuffer[AvgStateRemoved]
         avg = iλ.λ--spacked.--
@@ -1326,8 +1325,7 @@
           in
             res
       \stopbuffer
-      \placeexample[here][ex:AvgStateRemoved]{Normalized version of \in{example}[ex:AvgState] with ignored parts crossed out}
-          {\typebufferlam{AvgStateRemoved}}
+      \typebufferlam{AvgStateRemoved}
               
       When we actually leave out the crossed out parts, we get a slightly
       weird program: there is a variable \lam{s} which has no value, and there