Update README.md

Author: electricessence

README.md

@@ -28,7 +28,7 @@ var result = connectionFactory
 
 End-to-end asynchronous methods suffixed with `Async`.
 
-When using the SQL Client, asychronous methods are available as well as `.ToTargetBlockAsync<T>(target)` and `.AsSourceBlockAsync<T>()` Dataflow methods.
+When using the SQL Client, asychronous methods are available as well as ```.ToTargetBlockAsync<T>(target)``` and ```.AsSourceBlockAsync<T>()``` Dataflow methods.
 
 ## Extensions
 
@@ -51,7 +51,7 @@ var myResult = await cmd.ToListAsync(transform);
 
 In order to keep connection open time to a minimum, some methods cache data before closing the connection and then subsequently applying the transformations as needed.
 
-#### `Results<T>()` and `ResultsAsync<T>()`
+#### ```Results<T>()``` and ```ResultsAsync<T>()```
 
 Queues all the data.  Then using the provided type `T` entity, the data is coerced by which properties intersect with the ones available to the ```IDataReader```.
 
@@ -86,18 +86,18 @@ var people = cmd.Results<Person>(new Dictionary<string,string>{
 
 #### `Retrieve()` and `RetrieveAsync()`
 
-Queues all the data.  Returns a `QueryResult<Queue<object[]>>` containing the requested data and column information.  The `.AsDequeueingMappedEnumerable()` extension will iteratively convert the results to dictionaries for ease of access.
+Queues all the data.  Returns a ```QueryResult<Queue<object[]>>``` containing the requested data and column information.  The `.AsDequeueingMappedEnumerable()` extension will iteratively convert the results to dictionaries for ease of access.
 
-#### `AsSourceBlockAsync<T>()`
+#### ```AsSourceBlockAsync<T>()```
 
 (Fully asynchronous.) Retuns a Dataflow source block.  Then asynchronously buffers and transforms the results allowing for any possible Dataflow configuration.  The source block is marked as complete when there are no more results.  If the block is somehow marked as complete externally, the flow of data will stop and the connection will close.
 
-### `AsSourceBlockAsync<T>()` versus `ResultsAsync<T>`
+### ```AsSourceBlockAsync<T>()``` versus ```ResultsAsync<T>```
 
 Depending on the level of asynchrony in your application, you may want to avoid too much buffering of data. 
 
-`AsSourceBlockAsync<T>()` is fully asynchronous from end-to-end and can keep total buffering to a minimum by consuming (receiving) results as fast as possible, but may incur additional latency between reads.
+```AsSourceBlockAsync<T>()``` is fully asynchronous from end-to-end and can keep total buffering to a minimum by consuming (receiving) results as fast as possible, but may incur additional latency between reads.
 
-`ResultsAsync<T>()` is fully asynchronous from end-to-end but returns an `IEnumerable<T>` that although has fully buffered the all the data into memory, has deferred the transformation until enumerated.  This way, the asynchronous data pipeline is fully complete before synchronously transforming the data.
+```ResultsAsync<T>()``` is fully asynchronous from end-to-end but returns an `IEnumerable<T>` that although has fully buffered the all the data into memory, has deferred the transformation until enumerated.  This way, the asynchronous data pipeline is fully complete before synchronously transforming the data.
 
-Both methods ultimately are using a `Queue<object[]>` or `ConcurrentQueue<object[]>` (Dataflow) to buffer the data, but `ResultsAsync<T>()` buffers the entire data set before dequeuing and transforming the results.
+Both methods ultimately are using a ```Queue<object[]>``` or ```ConcurrentQueue<object[]>``` (Dataflow) to buffer the data, but ```ResultsAsync<T>()``` buffers the entire data set before dequeuing and transforming the results.