updated differences and fixed typos

README.md

@@ -85,9 +85,9 @@ $ ./summitdb-server -p 7483 -dir data3 -join :7481
 
 That's it. Now if node1 goes down, node2 and node3 will continue to operate.
 
-## Difference between SummitDB and Redis
+## Differences between SummitDB and Redis
 
-*It may be worth noting that SummitDB is not a Redis clone. Redis has a lot of commands and data types that are not available in SummitDB, such Sets, Hashes, Sorted Sets, and PubSub.*
+It may be worth noting that while SummitDB supports many Redis features, it is not a strict Redis clone. Redis has a lot of commands and data types that are not available in SummitDB such as Sets, Hashes, Sorted Sets, and PubSub. SummitDB also has many features that are not available in Redis such as:
 
 - **Ordered key space** - SummitDB provides one key space that is a large B-tree. An ordered key space allows for stable paging through keys using the [KEYS](https://github.com/tidwall/summitdb/wiki/KEYS) command. Redis uses an unordered dictionary structure and provides a specialized [SCAN](http://redis.io/commands/scan) command for iterating through keys.
 - **Everything a string** - SummitDB stores only strings which are exact binary representations of what the user stores. Redis has many [internal data types](http://redis.io/topics/data-types-intro), such as strings, hashes, floats, sets, etc. 
@@ -218,7 +218,7 @@ Fencing Tokens
 A fencing token is simply a number that increases. 
 It's guaranteed to be consistent across the cluster and can never be deleted or decreased. 
 The value is a 64-bit unsigned integer. The first FENCE call will return "1".
-This is useful for things like distributed locking and preventing race conditions.
+This can be useful in applications that need things like distributed locking and preventing race conditions.
 
 ```
 > FENCE mytoken