Clean up for review

Author: crandmck

docs/manifest/reading/ingredients-reading.md

@@ -6,9 +6,9 @@ title: Reading ingredients
 ## Overview 
 
 Existing manifests may contain any of these three kinds of ingredients:
-- V1, with label `c2pa.ingredient` (deprecated).
-- V2, with label `c2pa.ingredient.v2` (deprecated).
-- V3, with label `c2pa.ingredient.v3`, which addresses the issue of validating ingredients after redaction.
+- V1, with labels starting with `c2pa.ingredient` (deprecated). See [Reading legacy manifest data](legacy.md#legacy-ingredients).
+- V2, with labels starting with `c2pa.ingredient.v2` (deprecated). See [Reading legacy manifest data](legacy.md#legacy-ingredients).
+- V3, with labels starting with `c2pa.ingredient.v3`, which addresses the issue of validating ingredients after redaction.
 
 :::note
 The C2PA Technical Specification describes _ingredient assertions_ but the CAI SDK treats ingredients separately as their own objects in the JSON manifest rather than as a type of assertion.
@@ -20,6 +20,8 @@ The `ingredients` array contains an element for each ingredient used to create a
 
 The `ingredients` array contains an [ingredient object](manifest/json-ref/manifest-def.mdx#ingredient) for each ingredient.  The only required property of the `ingredient` object is the `title` property, which usually is the source file name.
 
+The `label` property for the first ingredient in a manifest is `c2pa.ingredient.v3` When there is more than one ingredient, subsequent labels have a monotonically increasing index: `c2pa.ingredient.v3__1`, `c2pa.ingredient.v3__2`, and so on.
+
 Other important properties of the ingredient object include:
 - `format`: MIME type of the source file (optional).
 - `document_id` (optional) and `instance_id` (required) which are derived from the ingredient asset's XMP metadata.

docs/manifest/reading/legacy.md

@@ -7,10 +7,11 @@ As much as possible, an application should **write** manifest data that conforms
 
 ## Legacy ingredients
 
-Existing manifests may contain any of these three kinds of ingredients:
-- V1, with label `c2pa.ingredient` (deprecated).
-- V2, with label `c2pa.ingredient.v2` (deprecated).
-- V3, with label `c2pa.ingredient.v3`, which addresses the issue of validating ingredients after redaction.
+Old manifests may contain these kinds of deprecated ingredient data:
+- V1 ingredients, with label `c2pa.ingredient`.
+- V2 ingredients, with label `c2pa.ingredient.v2`.
+
+<a name="question"></a>
 
 <div class="review-comment">
 What should we say about reading v1 and v2 ingredients?

docs/manifest/reading/reading-cawg-id.md

@@ -68,7 +68,7 @@ The following table describes the allowed values of the `type` property of `veri
 | Value        |  Meaning |
 |--------------|----------|
 | `cawg.document_verification` | The identity provider verified one or more government-issued identity documents presented by the content creator.
-| `cawg.web_site` | The content creator has proven control over a specific domain to the identity claims aggregator._
+| `cawg.web_site` | The content creator has proven control over a specific domain to the identity claims aggregator.
 | `cawg.affiliation` | The identity provider is attesting to the content creator’s membership in an organization. This could be a professional organization or an employment relationship.
 | `cawg.social_media` | The content creator has demonstrated control over an account (typically a social media account) hosted by the identity provider.
 | `cawg.crypto_wallet` | The content creator has demonstrated control over an account (typically a crypto-wallet) hosted by the identity provider.

docs/manifest/writing/assertions-actions.md

@@ -37,6 +37,8 @@ Changes include:
 
 The [C2PA Technical Specification](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_actions) describes expanded v2 actions.  While v1 actions are fully specified in the actions array v2 actions may either be specified by an element of the actions array or from an element in the templates array with the same action name.
 
+<a name="question1"></a>
+
 <div class="review-comment">
 The CAI APIs can read all v2 actions and write most v2 actions.  What v2 actions can it NOT write?
 </div>
@@ -51,10 +53,6 @@ The C2PA Technical Specification defines a [set of standard assertions](https://
 
 The following table summarizes some of the most important standard assertions.
 
-<div class="review-comment">
-What other c2pa stadard assertions should we call out?
-</div>
-
 | Assertion | Label | Description |
 |-----------|-------|-------------|
 | [Content bindings](#content-bindings) | `c2pa.hash.*`, `c2pa.soft-binding`, etc. | Uniquely identify portions of an asset and bind the assertion to it, for example using cryptographic hashes. |

docs/manifest/writing/ingredients.md

@@ -9,9 +9,7 @@ Digital assets are often not created entirely from scratch, but instead created
 
 [Old manifests](../reading/legacy.md) may contain deprecated v1 and v2 ingredients, but applications should only write v3 ingredients.
 
-<div class="review-comment">
-This page should cover only v3 ingredients.
-</div>
+Applications should write only v3 ingredients, with label starting with `c2pa.ingredient.v3` and are described in the [C2PA specification](https://spec.c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#ingredient_assertion) .
 
 :::note
 The C2PA Technical Specification describes _ingredient assertions_ but the CAI SDK treats ingredients separately as their own objects in the JSON manifest rather than as a type of assertion.
@@ -23,6 +21,8 @@ The `ingredients` array contains an element for each ingredient used to create a
 
 The `ingredients` array contains an [ingredient object](manifest/json-ref/manifest-def.mdx#ingredient) for each ingredient.  The only required property of the `ingredient` object is the `title` property, which usually is the source file name.
 
+The `label` property for the first ingredient in a manifest is `c2pa.ingredient.v3` When there is more than one ingredient, subsequent labels have a monotonically increasing index: `c2pa.ingredient.v3__1`, `c2pa.ingredient.v3__2`, and so on.
+
 Other important properties of the ingredient object include:
 - `format`: MIME type of the source file (optional).
 - `document_id` (optional) and `instance_id` (required) which are derived from the ingredient asset's XMP metadata.