Fix Readme

README.md

@@ -10,10 +10,19 @@ using [Java Microbenchmark Harness (JMH)](https://github.com/openjdk/jmh)
 
 [![img.png](assets/2023-12-11T20:00:49Z.png)](https://github.com/Dhi13man/jsonata4java-benchmark/blob/218dd4403842fecb80a0713c1a80c83396089eb9/reports/2023-12-11T20%3A00%3A49Z/native_vs_jsonata_vs_jsonata_precompiled.txt)
 
-As per the benchmarking results, the native implementation is between 2 and 3 orders of magnitude
-faster than the Jsonata implementation. The Jsonata precompiled implementation is between 1 and 2
-orders of magnitude faster than the Jsonata implementation.
+### Key Findings
 
-However, the Jsonata implementation is much more readable and maintainable than the native
-implementation and most systems are not going to be doing this order of magnitude of processing
-anyway. So, the Jsonata implementation is a good choice for most systems for its flexibility.
+As per the benchmarking results,
+
+1. logic implemented natively in Java is between 2 and 3 orders of magnitude faster than
+   the same logic being implemented in Jsonata.
+2. The Jsonata precompiled implementation is up to 1 order of magnitude faster than the
+   compiled-at-runtime Jsonata implementation.
+3. The Jsonata implementation code is much more repeatable and flexible than the native
+   implementation.
+
+### Summary
+
+Despite Jsonata seeming much slower than native implementation, most systems are not going to be
+doing this order of magnitude of processing anyway. So, the Jsonata implementation is a good choice
+for most systems, because of its flexibility.