@@ -1,7 +1,7 @@
11Introduction
22------------
33
4−*servant* has the following guiding principles:
4+**servant** has the following guiding principles:
55
66- concision
77
@@ -23,9 +23,9 @@ Introduction
2323- separation of concerns
2424
2525 Your handlers and your HTTP logic should be separate. True to the philosphy
26− at the core of HTTP and REST, with *servant* your handlers return normal
26+ at the core of HTTP and REST, with **servant** your handlers return normal
2727 Haskell datatypes - that's the resource. And then from a description of your
28− API, *servant* handles the *presentation* (i.e., the Content-Types). But
28+ API, **servant** handles the *presentation* (i.e., the Content-Types). But
2929 that's just one example.
3030
3131- type safety
@@ -38,7 +38,3 @@ might expect. The core idea is *reifying the description of your API*. Once
3838reified, everything follows. We think we might be the first web framework to
3939reify API descriptions in an extensible way. We're pretty sure we're the first
4040to reify it as *types*.
41−
42−To be able to write a webservice you only need to read the first two sections,
43−but the goal of this document being to get you started with servant, we also
44−cover the couple of ways you can extend servant for a great good.