Taking the footer off the docs to make room for a small brubeck icon

README.md

@@ -248,6 +248,3 @@ Then retrieve the cookie value by passing the application's secret key into the
                               secret=self.application.cookie_secret)
 
 What you do from there is up to you, but you'll probably be loading the user_id from a database or cache to get the rest of the account info. 
-
-
-# Brubeck.io

docs/DESIGN.md

@@ -145,6 +145,3 @@ A call to `recv()` on connection instance will block until a message arrives or
 `Request.method()` will tell us whether the message was HTTP GET or POST, etc. `Request.version()` tells us the HTTP version used.
 
 This class is kept simple on purpose and could be used outside Brubeck for parsing Mongrel2 messages.
-
-
-# Brubeck.io

docs/INDEX.md

@@ -29,6 +29,3 @@ __Listsurf__ is a simple to way to save links. Yeah... another delicious clone!
 It serves as a basic demonstration of what a complete site looks like when you build with Brubeck. It has authentication with secure cookies, offers a JSON API, uses [Jinja2](http://jinja.pocoo.org/) for templating and stores data in [MongoDB](http://mongodb.org).
 
 * [Listsurf on GitHub](https://github.com/j2labs/listsurf)
-
-
-# Brubeck.io

docs/INSTALLING.md

@@ -139,6 +139,3 @@ In short: any requests for `http://localhost:6767/` should be sent to the Brubec
 Don't forget that our Brubeck handler is only configured to answer `http://localhost:6767/brubeck` for now. You could add another route once you're comfortable building `MessageHandler`'s
 
 The web server answers requests on port `6767`. It logs to the `./log` directory. It also writes a pidfile in the `./run` directory. 
-
-
-# Brubeck.io

docs/LICENSE.md

@@ -24,5 +24,3 @@ EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 The views and conclusions contained in the software and documentation are
 those of the authors and should not be interpreted as representing official
 policies, either expressed or implied, of J2 Labs LLC.
-
-# Brubeck.io