Clarify timeline of goals in the README

Author: jlb6740

README.md

@@ -12,7 +12,7 @@ Typically a benchmark reports either the amount of work done over a constant amo
 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.
 
 ## Benchmark principles
-WasmScore aims to serve as a standalone benchmark that:
+WasmScore aims to serve as a standalone Wasm benchmark and benchmarking framework that:
 - Is convenient to build and run with useful and easy to interpret results.
 - Is portable, enabling cross-platform comparisons.
 - Provides a breadth of coverage for typical current standalone use cases and expected future use cases.
@@ -26,13 +26,13 @@ Any number of test can be created but "wasmscore" is the initial and default tes
 - AI: (Coming)
 - Regex: (Coming)
 
-## Q4 Plan
+## 2023 Q4 Goals
 Next steps include:
 - Improving stability and user experience
 - Adding benchmarks to the AI, Regex, and APP suites
 - Adding more benchmarks
 - Complete the SIMD test
-- Publish a list of planned milestone
+- Publish a list of planned milestone with corresponding releases
 
 ## Usage