Update README.md

Author: Vlad Balin

README.md

@@ -2,45 +2,28 @@
 
 ![master build](https://api.travis-ci.org/Volicon/Type-R.svg?branch=master)
 
-Transactional, reactive, and serializable state management core written with TypeScript.
+Universal state container for modern JS applications written with TypeScript for both UI and domain state management.
 
-Properly implemented two-phase update transactions on object ownership tree, dude. Change events, with updates in the scope of current transaction. All serializable. All dynamically type safe. Just what the doctors prescribe for the modern data layer.
+Distributed application state is defined as supersposition of the recursively nested `Record` and `Collection` objects.
+State trees supports transactional and deeply observable changes, and is JSON-serializable by default. All state elements are _typed_ with run-time type assertions and type conversions on assignment. The declarative state validation is supported out of box as well.
 
-Mostly compatible by API with your backbonejs, but 10 times faster in all browsers and capable of way more than your old plugins are, dude. :) 
+Type-R explicitly supports both _aggregation_ and _associations by id_ with the majority of operations performed recursively on _ownership trees_.
 
-Will be the basis of NestedTypes 2.0 version. Does to your React app the same thing as mobx does, but adds serialization. And to be fair, we started earler, so it's appropriate to say that they do the part of tricks we're doing for two years.
+Mostly compatible by API with backbonejs, but 10 times faster in all browsers.
+
+Type-R represents the pinnacle of Volicon/Verizon R&D in the state management technology lasted for 3 previous years. 
 
 ## Rationale
 
 Because we can.
 
 ## Current state
 
-- [x] Basic regression tests passes. Transactional core seems to work.
-- [x] New integral performance tests shows 2-3 times performance improvement in complex structure updates. Good enough to go further.
-- [x] Launching backbone Model/Collection regression to implement missing core functionality. That's gonna be tough.
-    - [x] Model regression passes.
-    - [x] Collection regression passes.
-- [x] Implement relations.
-- [x] Implement NestedTypes compatibility layer.
-    - [x] Underscore/Lodash mixin for Model and Collection
-    - [x] Backbone Persistence API
-- [x] Test it with NestedReact examples.
-- [x] Release ObjectPlus as separate package.
-- [x] Implement classes support in NestedReact.
-- [x] Deploy NestedReact and NestedTypes 2.0 RC to Volicon Observer product.
-- [ ] Release NestedTypes 2.0 and NestedReact 1.0
-
-## To do later
-
-- [-] Fix silent option semantic. Now it's wrong (as in NestedTypes 1.3). Update should be propagated upper, just events must be supressed. (UPD: under the closer look, it's really the question what is wrong and what is not. Let's keep it like this for a while.)
-- [ ] Fix new event maps semantic in case of inheritance. There might be the problem with inherited models.
-- [x] Fix TypeDoc. It doesn't work.
-- [-] Tune-up the performance (UPD: seems to be fine for the first release - at least 2x gain compared to NestedTypes 1.3).  
+Tested and deployed to Volicon/Verizon production systems. Documentation is pending.
 
 ## Compatibility notes
 
-I bet you never was aware about the most of these things, but still:
+It highly unlikely that you even aware about the most of these Backbone API features, but still:
 
 - `object.trigger( 'a b' )` is not supported. Use `object.trigger( 'a' ).trigger( 'b' )`. Performance reasons. Not to mention, that when you doing so, you are most likely doing something wrong.
 - `model.initialize( attrs, options, owner )` uses third parameter to set owner, `options.collection` is ignored.
@@ -59,4 +42,4 @@ I bet you never was aware about the most of these things, but still:
 - Symbolic references - `store.x` syntax is deprecated, use `~x` instead.
 - `Integer` -> `Number.integer`
 - `Date` attribute doesn't parse MS format. Use `Date.microsoft`.
-- Object.extend.attach( Something ) => Nested.Messenger.mixTo( Something ).
+- Object.extend.attach( Something ) => Nested.Messenger.mixTo( Something ).