docs: clarify what we're providing in a machine readable format and for what purpose

Author: PLeVasseur

GOALS.md

@@ -31,7 +31,7 @@ There will be an addendum which covers how various safety standards like ISO 262
 * We aim to produce evidence-based guidelines, with statistics around human error when programming Rust, to support:
   1. What guidelines are written, and 
   2. Why a specific suggestion was made
-* We will produce the guidelines in an artifact that's easily machine readable and of a consistent format, to make it easier to consume by tool vendors to some minimal viable artifact.
+* We will produce the guidelines and a hash of their contents in a machine readable and consistent format, to make consumption simpler for tool vendors. These artifacts are:
   * a `needs.json` containing the contents of the coding guidelines
   * a `guidelines-ids.json` which has hashes of the guidelines' contents, which can be used to check against (and break) a tool vendor's build, until an audit is performed