Skip to content

Commit 30cf1ac

Browse files
authored
Merge pull request #140 from wirelessben/master
Fix the grammar in the Readme
2 parents d1b662e + e2f796a commit 30cf1ac

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,15 @@
44
[![Coverage Status](https://coveralls.io/repos/github/netplex/json-smart-v2/badge.svg?branch=master)](https://coveralls.io/github/netplex/json-smart-v2?branch=master)
55

66

7-
Json-smart development start in 2010, at that time SQL servers do not support native JSON fields, NoSQL databases slowly emerging, and all the existing JSON API were bogus. One this time I write lots of test to benchmark and compare JSON java parser.
7+
Json-smart development started in 2010, when SQL servers did not support native JSON fields, NoSQL databases were slowly emerging, and all the existing JSON APIs were bogus. I wrote lots of tests to benchmark and compare JSON java parsers.
88

9-
I never like SQL database, because it's almost impossible to update a data model without, impacting the production platform. Adding a column is a terrible operation.
9+
I never liked SQL databases because it's almost impossible to update a data model without impacting the production platform. Adding a column is a terrible operation.
1010

11-
That way I started json-smart. all non-indexed data in my datastores were stored in a column as a is serialized JSON message. To fit MySQL varchar(255) fields, I try to make my JSON as small as possible, that why json-smart il optimized to produce small JSON-like String.
11+
So I started json-smart. All non-indexed data in my datastores were stored in a column as a serialized JSON message. To fit MySQL varchar(255) fields, I tried to make my JSON as small as possible, so json-smart is optimized to produce small JSON-like Strings.
1212

13-
But now times had changed, most of the JSON API are now stable, and I'm now using document-oriented Databases and JSON native SQL types.
13+
Now times have changed: most of the JSON APIs are now stable, and I'm now using document-oriented databases and JSON-native SQL types.
1414

15-
So I do not use my json-smart anymore. I had fun with this project. If you want to apply some change on json-smart create pull request, with a lots JUnit test.
15+
So I do not use my json-smart anymore. I had fun with this project. If you want to apply some change on json-smart create a pull request with lots of JUnit tests.
1616

1717

1818
[WIKI is here](https://github.com/netplex/json-smart/wiki)

0 commit comments

Comments
 (0)