Apply suggestions from code review

Co-authored-by: Patryk Szulczewski <[email protected]>
Co-authored-by: Stephen Corry <[email protected]>

Author: 3 people

README.md

@@ -7,6 +7,7 @@ Our primary use case is the examination of structured data returned from network
 * Compare the operational state of network devices pre and post change
 * Compare operational state of a device vs a "known healthy" state
 * Compare state of similar devices, such as a pair of leafs or a pair of backbone routers
+* Compare operational state of a component (interface, vrf, bgp peering, etc.) migrated from one device to another
 
 However, the library fits other use cases where structured data needs to be operated on.
 
@@ -24,14 +25,14 @@ The library provides the ability to ask more intelligent questions of a given da
 
 * Is the route table within 10% of routes before and after a change?
 * Is all of the interfaces that were up before the change, still up?
-* Is there at least 10k sessions of traffic on my firewall?
+* Are there at least 10k sessions of traffic on my firewall?
 * Is there there at least 2 interfaces up within lldp neighbors?
 
 ## Technical Overview
 
 The library heavily relies on [JMESPath](https://jmespath.org/) for traversing the JSON object and finding the values to be evaluated. More on that [here](#customized-jmespath).
 
-`jdiff` has been developed around diffing and testing structured data returned from APIs and other Python modules and libraries (such as TextFSM) but is equally useful when working or dealing with data returned from APIs.
+`jdiff` has been developed around diffing and testing structured data returned from Network APIs and libraries (such as TextFSM) but is equally useful when working or dealing with data returned from APIs.
 
 ## Documentation