From ea618723c224a997594f5ecd68e4dd15c48a99aa Mon Sep 17 00:00:00 2001 From: Mark Phillips Date: Wed, 4 Jan 2012 14:38:50 -0800 Subject: [PATCH] adding a dash --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 94794b6..c74e2f5 100644 --- a/README.md +++ b/README.md @@ -14,8 +14,8 @@ This should be updated fairly regularly. As usual, **pull requests are encourage * [BrightBox Devloper Docs](docs.brightbox.com) - Clean design, easy to navigate, very in-depth. * [Riaknostic](riaknostic.basho.com) - Made possible by [Bootstrap](https://github.com/twitter/bootstrap), this is a great example of a project homepage that doubles as a documentation teaser. * [GitHub Developer Docs](http://developer.github.com/v3/) - I don't always get excited about accordion-based navigation, but when I do... -* [Dropwizard](http://dropwizard.codahale.com/) Beautiful and concise; another Bootstrap joint. -* [Riak Pipe README](github.com/basho/riak_pipe) - The simplicity of READMEs means that you can't obscure shitty content with flashy design. This one is written by my Basho colleague [Bryan Fink](https://twitter.com/#!/hobbyist) and should be committed to memory as an excellent example. +* [Dropwizard](http://dropwizard.codahale.com/) - Beautiful and concise; another Bootstrap joint. +* [Riak Pipe README](github.com/basho/riak_pipe) - The simplicity of READMEs means that you can't obscure shitty content with flashy design. This one is written by my Basho colleague [Bryan Fink](https://twitter.com/#!/hobbyist) and should be committed to memory as an excellent example of how to write READMEs. * [Learn You Some Erlang](http://learnyousomeerlang.com/) (via [@lenary](https://twitter.com/lenary)) * [Django Documentation](https://docs.djangoproject.com/en/1.3/) (via [@bretthoerner](https://twitter.com/bretthoerner)) * [Erldocs.com](http://erldocs.com/) (via [@bradfordw](https://twitter.com/#!/bradfordw))