#10 README updates [Skip CI]

Author: nblumhardt

README.md

@@ -1,12 +1,10 @@
-# Serilog.Sinks.Async [![Build status](https://ci.appveyor.com/api/projects/status/ewlh5x6xl4se5ech?svg=true)](https://ci.appveyor.com/project/JezzSantos/serilog-sinks-async)
-An async Serilog sink
+# Serilog.Sinks.Async [![Build status](https://ci.appveyor.com/api/projects/status/gvk0wl7aows14spn?svg=true)](https://ci.appveyor.com/project/serilog/serilog-sinks-async) [![NuGet](https://img.shields.io/nuget/vpre/Serilog.Sinks.Async.svg?maxAge=2592000)](https://www.nuget.org/packages/Serilog.Sinks.Async)
 
-Use this buffered, async, delegating, sink to reduce the time it takes for your app to write your log events to your sinks. This sink can work with any `IEventLogSink` you use.
+Use this buffered, async, delegating, sink to reduce the time it takes for your app to write your log events to your sinks. This sink can work with any `ILogEventSink` you use.
 
-Especially suited to sinks that are either slow to write or have I/O bottlenecks (like http, databases, file writes etc.). 
-This sink uses a separate thread pool thread to write to your sink, freeing up the calling thread to run in your app without having to wait. 
+Especially suited to non-batching sinks that are either slow to write or have I/O bottlenecks (like http, databases, file writes etc.). 
 
-Utilizes the producer/consumer pattern (using the TPL `BufferBlock<T>` class), where the calling thread produces log events (on your main thread), and the consumer runs on a thread pool thread consuming log events and writing them to your sink.
+This sink uses a separate worker thread to write to your sink, freeing up the calling thread to run in your app without having to wait.
 
 Install from NuGet:
 
@@ -18,23 +16,22 @@ Add this sink to your pipeline:
 
 ```csharp
 Log.Logger = new LoggerConfiguration()
-    .WriteTo.Async(x => x.Sink(new YourSink()))
+    .WriteTo.Async(x => x.YourSink())
     // Other logger configuration
     .CreateLogger()
 ```
 
-Now `YourSink` will write messages using another [thread pool] thread while your logging thread gets on with more important stuff.
+Now `YourSink` will write messages using a worker thread while your applicatoin thread gets on with more important stuff.
 
-If you think your code is producing log events faster than your sink can consume and write them, then the buffer is going to grow in memory, until you run out!
-Set a maximum size of the buffer so that your memory is not filled up. 
-Buffered log events are then (async) postponed in your app thread until your sink catches up.
+The default memory buffer feeding the worker thread is capped to 10,000 items, after which arriving events will be dropped. To increase or decrease this limit, specify it when configuring the async sink.
 
 ```csharp
 Log.Logger = new LoggerConfiguration()
-    .WriteTo.Async(x => x.Sink(new YourSink), 500) //Max number of logevents to buffer in memory
+    .WriteTo.Async(x => x.YourSink(), 500) // Max number of events to buffer in memory
     // Other logger configurationg
     .CreateLogger()
 ```
 
-## About this Sink
-This sink was created by this conversation thread: https://github.com/serilog/serilog/issues/809
+## About this sink
+
+This sink was created following this conversation thread: https://github.com/serilog/serilog/issues/809