minor grammar fixes in README

1 files changed, 9 insertions, 9 deletions

diff --git a/README b/README
index f52beac..93b3a1a 100644
--- a/README
+++ b/README
@@ -4,12 +4,13 @@ Welcome to Yet Another JSON Library (YAJL)
 
 Good question.  In a review of current C JSON parsing libraries I was 
 unable to find one that satisfies my requirements.  Those are, 
-0. Written in C
+0. written in C
 1. portable
-2. robust, as close to "crash proof" as possible
+2. robust -- as close to "crash proof" as possible
 3. data representation independent
 4. fast
-5. generates verbose, useful error messages including.
+5. generates verbose, useful error messages including context of where
+   the error occurs in the input text.
 6. can parse JSON data off a stream, incrementally
 7. simple to use
 8. tiny
@@ -22,18 +23,17 @@ of the more important aspects of YAJL.
 
 BSD licensing means you can use it in open source and commercial products
 alike.  My request beyond the licensing is that if you find bugs drop
-me a email.  I'm eager to hear feedback about the design.
+me a email, or better yet, fork me on git and fix it!
 
 Porting YAJL should be trivial, the implementation is ANSI C.  If you
-port to new systems I'd love to hear of it, and I'd love to integrate
-your patches.
+port to new systems I'd love to hear of it and integrate your patches.
 
 ## YAJL is data representation independent.
 
 BYODR!  Many JSON libraries impose a structure based data representation
 on you.  This is a benefit in some cases and a drawback in others.
-YAJL uses call-backs to remain agnostic of the in memory representation.
-So if you wish to build up an in memory representation, you may do so
+YAJL uses callbacks to remain agnostic of the in-memory representation.
+So if you wish to build up an in-memory representation, you may do so
 using YAJL, but you must bring the code that defines and populates the
 in memory structure.
 
@@ -65,4 +65,4 @@ application.
 Fat free.  No whip.
 
 enjoy,
-Lloyd - July, 2007
+Lloyd - July, 2007