Update README.md

README.md

@@ -30,7 +30,7 @@ Serial queues offer a very interesting option in the "middle" of these two space
  - They are very lightweight (each queue is literally not much more than a List and a few lock objects), so you can easily have thousands of them
  - They have a usage model which is similar to threads and is easier to reason about
 
- # Example
+# Example
 
     var q = new SerialQueue();
     q.DispatchAsync(() => {
@@ -45,4 +45,4 @@ Thus, the actions are thread-safe and easy to reason about.
 
 The actual execution of the functions is managed by the built-in .NET ThreadPool (the default implementation just uses `Task.Run`) so many thousands of queues will be backed by perhaps 8 or so underlying OS threads in the threadpool
 
-More Documentation is available on the [Github wiki](https://github.com/borland/SerialQueue/wiki)
+More Documentation is available on the [Github wiki](https://github.com/borland/SerialQueue/wiki)