More s&r

Author: crandmck

docs/manifest/understanding.md

@@ -13,7 +13,7 @@ A manifest store can be linked to an asset in three ways:
 
 1. Directly embedded in the asset's metadata.
 1. In a sidecar file, a file with the same file name as the asset but with a `.c2pa` extension.
-1. In a remote URL, linked from the asset's metadata, as detailed in the [C2PA specification](https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html#_embedding_a_reference_to_the_active_manifest).  NOTE: A given asset can have a remote manifest store plus a local manifest store linked in one of the first two ways. 
+1. In a remote URL, linked from the asset's metadata, as detailed in the [C2PA specification](https://spec.c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_external_manifests).  NOTE: A given asset can have a remote manifest store plus a local manifest store linked in one of the first two ways. 
 
 To determine if an asset has Content Credentials, the SDK checks for the presence of a manifest store (in the order shown above). So, for example to see if `foo.jpg` has Content Credentials, the SDK first checks if there's a manifest store in the file itself, then looks for a sidecar file (`foo.c2pa` in the same directory), and finally looks in the asset's metadata for a reference to a remote manifest store.  
 
@@ -48,4 +48,4 @@ The time-stamp is typically defined as part of the signing information. You can
 ## References
 
 - [JUMBF](https://www.iso.org/standard/84635.html): A framework for JPEG standards to add universal metadata, supplementary images, or other elements in addition to the base image.
-- [C2PA Technical Specification v1.4](https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html)
+- [C2PA Specifications](https://spec.c2pa.org/specifications/)