Update README Benchmarks section

Author: jlb6740

README.md

@@ -9,7 +9,7 @@ One of the most important and challenging aspect of benchmarking is deciding how
 ## Benchmarks
 Typically a benchmark reports either the amount of work done over a constant amount of time or it reports the time taken to do a constant amount of work. The benchmarks here all do the later. The initial commit of the benchmarks available have been pulled from Sightglass however the benchmarks used with WasmScore come from the local directory here and have no dependency on the benchmarks stored in the Sightglass repo. However, how the benchmarks here are built and run do directly dependent on changes to the external Sightglass repo.
 
-Benchmarks are often categorized based on their origin. Two such buckets are (1) codes written with the intent of being user facing (common paths in library code, a typical application usage, etc) and (2) codes written specifically to benchmark some important or common code construct or platform feature. WasmScore does not aim to favor either of these benchmarking buckets as both are valuable for the evaluation of standalone Wasm performance depending on what you want to test and what you are trying to achieve.
+Benchmarks are often categorized based on their purpose and origin. Two such buckets are (1) codes written with the original intent of being user facing (hot paths in library codes, a typical application usage, etc) and (2) codes written specifically to target benchmarking some important or commonly used code construct or platform component. WasmScore does not aim to favor either of these benchmarking buckets as both are valuable in the evaluation of standalone Wasm performance, depending on what you want to test and what you are trying to achieve.
 
 ## Benchmark principles
 WasmScore aims to serve as a standalone Wasm benchmark and benchmarking framework that: