readme update

Author: DavidBM

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ion-binary-rs"
-version = "0.8.6"
+version = "0.8.7"
 authors = ["Couragium Solutions <[email protected]>"]
 edition = "2018"
 description="Pure Rust parser, encoder and hasher for Amazon's Ion binary format."

README.md

@@ -8,9 +8,15 @@ Ion binary is a library written in safe rust for parsing, encoding and hashing A
 [![Documentation](https://docs.rs/ion-binary-rs/badge.svg)](https://docs.rs/ion-binary-rs)
 [![Crates.io](https://img.shields.io/crates/v/ion-binary-rs)](https://crates.io/crates/ion-binary-rs)
 
-It should be able to **parse**, **encode** and **hash** anything you throw at it. Any failure to do so
+It **parses**, **encodes** and **hashes** anything you throw at it. Any failure to do so
 is a bug that we will fix and we will be very happy if you report them.
 
+The code is mature and way more tested than Amazon's alternatives, including their js
+library. Amazon, when implementing the "good tests" only check that it parses. We check
+that the value is the correct one too. Additionally, we seem to be implementing way 
+more of the ion protocol than Amazon's libraries, as we don't have huge skip lists in 
+the tests files. We test all their test suite, not only a few test.
+
 ## How to use the library
 
 First of all, you need to be aware of the trade offs that we took for this library:

src/lib.rs

@@ -7,8 +7,14 @@
 //! [![Documentation](https://docs.rs/ion-binary-rs/badge.svg)](https://docs.rs/ion-binary-rs)
 //! [![Crates.io](https://img.shields.io/crates/v/ion-binary-rs)](https://crates.io/crates/ion-binary-rs)
 //!
-//! It should be able to **parse**, **encode** and **hash** anything you throw at it. Any failure to do so
+//! It **parses**, **encodes** and **hashes** anything you throw at it. Any failure to do so
 //! is a bug that we will fix and we will be very happy if you report them.
+//! 
+//! The code is mature and way more tested than Amazon's alternatives, including their js
+//! library. Amazon, when implementing the "good tests" only check that it parses. We check
+//! that the value is the correct one too. Additionally, we seem to be implementing way 
+//! more of the ion protocol than Amazon's libraries, as we don't have huge skip lists in 
+//! the tests files. We test all their test suite, not only a few test.
 //!
 //! ## How to use the library
 //!