Update README.md

Author: jezzsantos

README.md

@@ -1,8 +1,10 @@
 # Serilog.Sinks.Async [![Build status](https://ci.appveyor.com/api/projects/status/rostpmo2gq08ecag?svg=true)](https://ci.appveyor.com/project/mindkin/serilog-sinks-async)
 An async Serilog sink
 
-Use this buffered async delegating sink to reduce the time it takes to write your log events to a sink.
-This sink can work with any `IEventLogSink`. Especially suited to sinks that are either slow to write or wait on I/O (like databases, files systems etc). This sink uses a separate thread pool thread to execute your sink, freeing up the calling thread to run in your app.
+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. 
+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. 
+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.
 
 Install from NuGet:
 
@@ -21,9 +23,9 @@ Log.Logger = new LoggerConfiguration()
 
 Now `YourSink` will write messages using another [thread pool] thread while your logging thread gets on with more important stuff.
 
-If you think your code is logging faster than your sink can handle, then the buffer is going to grow in memory.
-Set a maximum size of the buffer so that your machine memory is not filled up. 
-Buffered logevents are then (async) postponed until your sink catches up.
+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.
 
 ```csharp
 Log.Logger = new LoggerConfiguration()