Update references from claim->statement and ledger-->append-only log (#…

…45)

* Update references from claim->statment and ledger-->append-only log
* Apply suggestions from code review

Signed-off-by: steve lasker <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]>
Co-authored-by: Yogesh Deshpande <[email protected]>

README.md

@@ -15,30 +15,30 @@ SCITT supports the ongoing verification of goods and services where the authenti
 In practice, SCITT provides information about artifacts, enabling a mesh of dependencies to understand what each subsystem is consuming.
 Detailed information comes in varying formats, from structured to unstructured.
 
-In SCITT, structured data is a claim. A claim is a well-structured statement, made by a verifiable entity that may have supporting evidence.
+In SCITT, structured data is represented as a Statement. A Statement is a well-structured statement, made by a verifiable entity that may have supporting evidence.
 
-<img src="./assets/claims-evidence-relationship.png" alt="Identity, Claim, Evidence, Artifact relationship" style="width:300px;"/>
+<img src="./assets/statement-evidence-relationship.png" alt="Identity, Statement, Evidence, Artifact relationship" style="width:300px;"/>
 
 ### Continual Updates
 
-Documenting claims at the time software is built or deployed would sell SCITT short, as software isn't static. Software is continually updated, and more importantly, we continually learn and want to convey new information about artifacts that have already been released. Reputable OSS Projects and Independent Software Vendors (ISVs) don't intentionally produce software they know to be vulnerable. Only after the software is public do we often find out about new vulnerabilities. SCITT is a means to convey a stream of continual updates for each versioned artifact.
+Documenting Statements at the time software is built or deployed would sell SCITT short, as software isn't static. Software is continually updated, and more importantly, we continually learn and want to convey new information about artifacts that have already been released. Reputable OSS Projects and Independent Software Vendors (ISVs) don't intentionally produce software they know to be vulnerable. Only after the software is public do we often find out about new vulnerabilities. SCITT is a means to convey a stream of continual updates for each versioned artifact.
 
 ## SCITT Persistence
 
-SCITT is intended to store verifiable claims for the life of the of the SCITT instance. One of the many questions that surfaces is how big will the SCITT ledger get? What kind of data will go on the SCITT ledger that would cause it to grow?
+SCITT is intended to store Signed Statements for the life of the of the SCITT instance. One of the many questions that surfaces is how big will the SCITT append-only log get? What kind of data will go on the SCITT append-only log that would cause it to grow?
 
 ### eNotary
 
-SCITT is analogous to a digital, or electronic notary service (eNotary), where minimal information is written to the ledger, endorsing the claim. When users notarize legal documents, the notary ledger records the verified identity of the parties, referencing the legal document they are notarizing. The notary ledger doesn't store the legal document, but does have a reference to it. 
+SCITT is analogous to a digital or electronic notary service (eNotary), where minimal information is written to the append-only log and an augmented counter-signature over the Statement and corresponding metadata (Receipt) is produced. When users notarize legal documents, the notary append-only log records the verified identity of the parties, referencing the legal document they are notarizing. The notary append-only log doesn't store the legal document, but does have a reference to it. 
 
-In SCITT, the ledger will contain pointers to the artifact, which the claims are made, with pointers to any supporting evidence.
+In SCITT, the append-only log will contain pointers to the artifact, which Statements are made, with optional pointers to any supporting evidence.
 
 ### Evidence Persistence
 
-A SCITT instance will persist verifiable claims to its ledger. Any optional evidence will be persisted in associated storage. 
+A SCITT instance will persist  Signed Statements to its append-only log. Any optional evidence will be persisted in associated storage. 
 
 <img src="./assets/scitt-persistence.png" alt="SCITT persistence" style="width:600px;"/>
 
-While a SCITT instance should provide a default storage, there's no limit on what storage services are used. For package managers that support breadths of content types, the evidence may be stored alongside the artifact by which the claim is being made. For package managers that limit the content types to the specific package type, a SCITT instance should provide default storage persistence.
+While a SCITT instance should provide a default storage, there's no limit on what storage services are used. For package managers that support breadths of content types, the evidence may be stored alongside the artifact by which the Statement is being made. For package managers that limit the content types to the specific package type, a SCITT instance should provide default storage persistence.
 
 For more info, see: [Supply Chains]({% link supply-chain.md %})