From d016106572b2449328b4f2151d32aec6e18f1d1c Mon Sep 17 00:00:00 2001
From: Jasper Van der Jeugt <jaspervdj@gmail.com>
Date: Mon, 28 Feb 2011 16:13:53 +0100
Subject: Typo fixes by simon meier
---
examples/hakyll/tutorial.markdown | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/examples/hakyll/tutorial.markdown b/examples/hakyll/tutorial.markdown
index 7a50f6d..9ee6066 100644
--- a/examples/hakyll/tutorial.markdown
+++ b/examples/hakyll/tutorial.markdown
@@ -10,7 +10,7 @@ anyone still care about a static website?
- Static websites are fast, because it's simply files served directly from the
hard disk.
-- Static websites are secure. Nobody has even found an SQL injection in static
+- Static websites are secure. Nobody has ever found an SQL injection in static
pages.
- Static websites are easy to deploy. Just copy them to your webhost using
(S)FTP/rsync/scp and you are done. They work on all webhosts: no CGI or extra
@@ -128,11 +128,11 @@ route "css/*" idRoute
~~~~~
Apart from specifying where the items should go (using `route`), we also have to
-specify *how* the need to be compiled. This is done using the `compile`
-function. As second argument, it takes a `Compiler`. These compilers can consist
-of very complicated constructions, but Hakyll also provides a number of good
-default compilers. The `compressCssCompiler` compiler will simply compress the
-CSS found in the files.
+specify *how* they need to be compiled. This is done using the `compile`
+function. It takes a `Compiler` as its second argument. These compilers can
+consist of very complicated constructions, but Hakyll also provides a number of
+good default compilers. The `compressCssCompiler` compiler will simply compress
+the CSS found in the files.
~~~~~{.haskell}
compile "css/*" compressCssCompiler
--
cgit v1.2.3