diff --git a/build/site/specifications/2.1/specs/C2PA_Specification.html b/build/site/specifications/2.1/specs/C2PA_Specification.html index 3ec51fc..db58a68 100644 --- a/build/site/specifications/2.1/specs/C2PA_Specification.html +++ b/build/site/specifications/2.1/specs/C2PA_Specification.html @@ -449,7 +449,7 @@

1.2. Scope

-C2PA specifications SHOULD NOT provide value judgments about whether a given set of provenance data is 'good' or 'bad,' merely whether the assertions included within can be validated as associated with the underlying asset, correctly formed, and free from tampering. +C2PA specifications SHOULD NOT provide value judgments about whether a given set of provenance data is 'good' or 'bad'. The assertions can be: validated as associated with the underlying asset, can be correctly formed, and are free from tampering.
@@ -760,7 +760,7 @@

2

This is the preferred, non-technical, term for a C2PA Manifest. The C2PA Manifest Store therefore represents the Content Credentials of an asset.

-

Content Credentials also refers to the overall C2PA technology, and is therefore essentially treated as a plural noun. If a C2PA Manifest is a Content Credential, then multiple C2PA Manifest or the broader, universal concept is Content Credentials.

+

Content Credentials can also refer to the overall C2PA technology. If a C2PA Manifest is a Content Credential, then multiple C2PA Manifests or the universally aggreated concepts are Content Credentials.