[A few web-page tweaks.
Malcolm.Wallace@me.com**20101101065655
 Ignore-this: fc0ae7509e7508cdb4fafa3ca65c0a74
] {
hunk ./docs/index.html 85
+     These modules are internal details.
hunk ./docs/index.html 90
-     here.  The actual implementations for strict, lazy, and so on, are
-     instances of the class, defined in modules at the same level in the
+     here.  The datatype implementations for strict, lazy, and so on, are
+     more-or-less identical, but with separate
+     instances of the classes, defined in modules at the same level in the
hunk ./docs/index.html 94
-     re-exports these base combinators, so there should be no need to
-     import this module directly.
+     re-exports the base combinators, and base types, so there should be
+     no need to import these modules directly.
hunk ./docs/index.html 169
-    http://www.cs.york.ac.uk/fp/darcs/polyparse</tt>
+    http://code.haskell.org/polyparse</tt>
hunk ./docs/index.html 173
-polyparse-1.5, release date 2010.05.29<br>
+polyparse-1.5, release date 2010.xx.xx<br>
hunk ./docs/index.html 175
-<a href="http://www.cs.york.ac.uk/fp/polyparse/polyparse-1.5.tar.gz">.tar.gz</a>,
-<a href="http://www.cs.york.ac.uk/fp/polyparse/polyparse-1.5.zip">.zip</a>.
-<br>
-By FTP: 
-<a href="ftp://ftp.cs.york.ac.uk/pub/haskell/polyparse/">
-ftp://ftp.cs.york.ac.uk/pub/haskell/polyparse/</a>
+<a href="http://code.haskell.org/polyparse/polyparse-1.5.tar.gz">.tar.gz</a>,
+<a href="http://code.haskell.org/polyparse/polyparse-1.5.zip">.zip</a>.
hunk ./docs/index.html 333
-implementation of the nhc98 compiler are monadic and space-efficient.
-However, they do not use the standard do-notation, because in fact they
-are more general than the standard monad category.
+implementation of the nhc98 compiler are designed for space-efficiency.
+They were the first example of Applicative parsers (although the term
+was not known then), as opposed to Monadic parsers.
hunk ./docs/index.html 339
-Daan Leijen's parsec.</a> The parsec library is widely used, since it is
-distributed with ghc.  Its combinators are fairly robust, but you need
-to place explicit backtracking into your parsers, using the <tt>try</tt>
-operator.  This can be tricky.
+Daan Leijen's parsec.</a> The parsec library is widely used, because it
+was once distributed with ghc.  Its combinators are fairly robust, but
+you need to place explicit backtracking into your parsers, using the
+<tt>try</tt> operator.  This can be tricky.
hunk ./docs/index.html 351
-Read class.  It is a whole lot more efficient that Read, but because it
+Read class.  It is a whole lot more efficient than Read, but because it
}