Updates to validation

Author: crandmck

docs/manifest/reading/validation.md

@@ -13,37 +13,33 @@ In the latest version of the SDK,
 Need a high-level summary of full validation, what we're looking for, etc.
 </div>
 
-## Validation errors in manifests
-
-When you load an asset, all the manifests in the manifest store are validated and any [failure codes](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_failure_codes) are assigned to the `validation_status` array. Inspect the array to find the validation errors.
-
 `Reader` has these validation methods:
-- `validation_state()` returns `ValidationState`, which can be `Invalid`, `Valid` or `Trusted`.
-- `validation_results()` returns `ValidationResults`, which returns `success`, `informational`, and `failure` codes for the active manifest and ingredients. NOTE: `ValidationStatus` is deprecated in favor of `ValidationResults`.
+- `validation_state()` returns `ValidationState` object (`validation_state` in JSON), which can be `Invalid`, `Valid` or `Trusted`.
+- `validation_results()` returns `ValidationResults` (`validation_results` in JSON), which can be `success`, `informational`, and `failure` codes for the active manifest and ingredients.
 
-:::tip
-Validation returns ONLY error codes; success is not explicitly indicated. If there are no validation errors, then the manifest won't have the `validation_status` element.
+:::note 
+The old `ValidationStatus` and `validation_status` array in previous SDK releases are deprecated in favor of `ValidationResults` / `validation_results` and `ValidationState` / `validation_state`.
 :::
 
+## Validation errors in manifests
+
+When you load an asset, all the manifests in the manifest store are validated and [result codes](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_failure_codes) are assigned to properties in the `validation_results` object.
+
 Manifest validation errors can occur, for example, when:
 
 - The bits of an asset are edited after it was signed.
 - A claim or assertion is missing or tampered with.
 - The manifest is signed with an invalid credential.
 
-:::caution
-Don't assume that just because you didn't get an error from the function return value that there are not validation errors. You MUST check the `validation_status` array to see if there are errors or not.
-:::
-
 ## Validation errors in ingredients
 
-Ingredients are validated when they are imported into an asset and the result is stored in the ingredient's `validation_status` array.
+Ingredients are validated when they are imported into an asset and the result is stored in the ingredient's `validation_results` object.
 
-Only errors that are not already recorded in the `validation_status` of an ingredient are reported. See [ValidationStatus](../json-ref/manifest-def.mdx#validationstatus) object in Manifest store reference.
+Only errors that are not already recorded in the `validation_results` of an ingredient are reported. See [ValidationStatus](../json-ref/manifest-def.mdx#validationresults) object in Manifest store reference.
 
 ## Error status codes
 
-The following table describes some common validation error status codes. Refer to the [C2PA Technical Specification](https://c2pa.org/specifications/specification2.2/specs/C2PA_Specification.html#_failure_codes) for the full list.
+The following table describes some common validation error status codes. Refer to the [C2PA Technical Specification](https://spec.c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_failure_codes) for the full list.
 
 | Validation Status Code| Description  | Type of URI |
 | --------------------- | ------------ | ----------- |
@@ -64,26 +60,3 @@ Validation error status codes can contain JUMBF URIs that reference assertions o
 - **Signature Box URI**: A URI like `self#jumbf=c2pa.signature`.
 
 For more information, see the [C2PA Technical Specification](https://c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_uri_references).
-
-<!--
-Actions and assertions:
-
-For actions - reference the spec e.g. common actions we refer to
-
-How to describe an EXIF assertion in JSON
-
-CreativeWork assertion
-
-Actions
-- Examples
-- Ref to spec and schema.org
-- GenAI - variation of Created Action
-
-Assertions
-
-- CreativeWork assertion
-- DNT - Special assertion
-- EXIF
-
-User-defined assertion
--->