add note on self-requirement

Author: DenTelezhkin

CHANGELOG.md

@@ -11,6 +11,8 @@ Examples:
 
 ### Limitations
 
+`ResponseParseable` and `JSONDecodable` are now Self-requirement protocols with all their limitations. Apart from that, there are some other limitations as well:
+
 #### Subclasses
 
 Subclassing ResponseParseable requires explicit typealias in subclassed model:
@@ -29,12 +31,10 @@ class Sibling: Ancestor {
 
 [Discussion in mailing Swift mailing lists](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151228/004645.html)
 
-
 #### Multiple custom mappers
 
 Current architecture does not support having more than one mapper in your project, because Swift is unable to differentiate between two ResponseParseable extensions on different types.
 
-
 #### Arrays and CollectionTypes
 
 Currently, there's no way to extend CollectionType or Array with `JSONDecodable` or `ResponseParseable` protocol, so creating request with ModelType of array(APIRequest<[Foo],Bar>) is not possible.

README.md

@@ -186,7 +186,7 @@ There are also default implementations of `JSONDecodable` protocol for Swift bui
 
 Starting with 0.2.0, we are adding support for any custom mapper to be used with TRON. Now, instead of JSONDecodable, all generic constraints on TRON accept `ResponseParseable` protocol, that can be easily implemented for your mapper.
 
-By default, we are using SwiftyJSON, and adding protocol default implementations on it, so existing code should not break.
+By default, we are using SwiftyJSON, and adding protocol default implementations on it.
 
 **Note** Custom mappers are supported only when installing framework from CocoaPods due to inability of Carthage to split framework to subspecs.