Merge pull request #26 from Silv3rcircl3/small_doc_updates

adjust ISubscription.Cancel comment and Readme

Author: Marc Piechura

README.md

@@ -206,7 +206,7 @@ nioSelectorThreadOrigin | map(f) filter(p) consumeTo(toNioSelectorOutput)
 
 All of these variants are "asynchronous streams". They all have their place and each has different tradeoffs including performance and implementation complexity.
 
-The Reactive Streams contract allows implementations the flexibility to manage resources and scheduling and mix asynchronous and synchronous processing within the bounds of a non-blocking, asynchronous, push-based stream.
+The Reactive Streams contract allows implementations the flexibility to manage resources and scheduling and mix asynchronous and synchronous processing within the bounds of a non-blocking, asynchronous, dynamic push-pull stream.
 
 In order to allow fully asynchronous implementations of all participating API elements—`IPublisher`/`ISubscription`/`ISubscriber`/`IProcessor`—all methods defined by these interfaces return `void`.
 

src/api/Reactive.Streams/ISubscription.cs

@@ -42,7 +42,7 @@ public interface ISubscription
         /// Request the <see cref="IPublisher{T}"/> to stop sending data and clean up resources.
         /// </para>
         /// <para>
-        /// Data may still be sent to meet previously signalled demand after calling cancel as this request is asynchronous.
+        /// Data may still be sent to meet previously signalled demand after calling cancel.
         /// </para>
         /// </summary>
         void Cancel();