Remove some <h5>s

snaplets/heist/templates/docs/tutorials/snap-api.md

@@ -64,19 +64,19 @@ matching the rest of the path and serve them.
 
 Let's go over each of the Snap API functions used here.
 
-##### [`dir`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:dir)
+### [`dir`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:dir)
 
 `dir` runs its action only if the request path starts with the specified
 directory.  You can combine successive dir calls to match more than one
 subdirectory into the path.
 
-##### [`ifTop`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:ifTop)
+### [`ifTop`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:ifTop)
 
 `ifTop` only executes its argument if the client requested the root URL.  Use
 this for your home page.  It can also be combined with the `dir` function to
 define your index handler for a certain URL directory.
 
-##### [`writeBS`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:writeBS)
+### [`writeBS`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:writeBS)
 
 `writeBS` appends a strict ByteString to the response being constructed.  Snap
 also provides an analogous function `writeLBS` for lazy ByteStrings.  You can
@@ -101,7 +101,7 @@ your site.  For large sites, this could be quite noticeable.  To remedy this,
 Snap also provides you with the `route` function that routes requests based on the
 request path in `O(log n)` time:
 
-##### [`route`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:route)
+### [`route`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:route)
 
 `route` takes a list of (route, handler) tuples and succeeds returning the
 result of the associated handler of the route that matches.  If no route
@@ -111,7 +111,7 @@ In a real application, you will want to use `route` for almost everything.
 We didn't do it that way in this example because we wanted to demonstrate
 more of the API.
 
-##### [`getParam`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:getParam)
+### [`getParam`](http://hackage.haskell.org/packages/archive/snap-core/0.8.0/doc/html/Snap-Core.html#v:getParam)
 
 `getParam` retrieves a GET or POST parameter from the request.  In this
 example, the `route` function binds a captured portion of the URL to the

snaplets/heist/templates/faq.md

@@ -261,7 +261,7 @@ Note that in order to quit a running Snap app on Windows, you need to press `Ctr
 
 ### How can I help?
 
-##### Use Snap to build real websites.
+#### Use Snap to build real websites.
 
 This is perhaps the best way to help.  Let us know what issues you encounter
 and work on fixing the ones you care about most.  If you are unable to fix a
@@ -275,21 +275,21 @@ become more evident as we find code patterns common to real-world Snap
 websites.  Communicating real-world Snap development experiences to us is a
 great way to contribute to this effort.
 
-##### Develop automated memory leak and performance regression testing.
+#### Develop automated memory leak and performance regression testing.
 
 Currently our top priority is working out correctness and performance issues in
 the server.  We have a CI build server that automatically runs all our test
 cases, but we don't have an automated system to test for performance and memory
 leaks.  This would be a very helpful addition.
 
 
-##### Improve test cases and code coverage.
+#### Improve test cases and code coverage.
 
 While not an exotic task, expanding our test suite can contribute significantly
 to the stability of the project.
 
 
-##### Improve documentation and tutorials.
+#### Improve documentation and tutorials.
 
 It's easy for documentation to get out of date.  We try to keep it up-to-date,
 but we can always use more eyes to catch things that slip through the cracks.