fix more links, etc

Author: Rand McKinney

docs/getting-started.mdx

@@ -87,7 +87,7 @@ In practice, to use a certificate with the CAI SDK, follow this process:
 3. Use one of the supporting CAI libraries or C2PA Tool to sign manifests using the certificate. 
 
 :::tip
-For more details and a short tutorial example, see [Signing manifests](manifest/signing-manifests).
+For more details and a short tutorial example, see [Signing manifests](manifest/signing-manifests.md).
 :::
 
 ### Getting a security certificate
@@ -113,7 +113,7 @@ Certificate authorities offer many levels of validation. For Content Credentials
 - **Organization Validated (OV).** The CA validates the organization's identity by checking its credentials against extensive databases, including those held by local governments.
 - **Extended Validation (EV).** A fully authenticated certificate, needed to offer secure web locations, email, and financial transactions.
 
-If you don't get an OV certificate, then the Content Credentials that use the certificate won't display your organization name, as shown in the examples on [verify.contentauthenticity.org](https://verify.contentauthenticity.org/).
+If you don't get an OV certificate, then the [C2PA Verify tool](https://verify.contentauthenticity.org/) won't display your organization name in the Content Credentials.
 
 ### Extracting the certificate
 
@@ -143,7 +143,7 @@ The C2PA [Verify tool](https://contentcredentials.org/verify) uses a list of _kn
 
 ## Identity
 
-To identify who created or modified an asset, identity needs to be verifiable and bound to an asset and its manifest store. The CAI SDK supports the [W3C verifiable credentials](https://c2pa.org/specifications/specifications/1.3/specs/C2PA_Specification.html#_w3c_verifiable_credentials) standard recommendation (part of the C2PA specification), but doesn't currently have a way to validate these credentials or ensure that they properly reflect authorship of the content. An actor can add one or more identities to a manifest using the W3C verifiable credentials data model. Currently, a verifier must trust the manifest signer to properly authenticate the identity.
+To identify who created or modified an asset, identity needs to be verifiable and bound to an asset and its manifest store. The CAI SDK supports the [W3C verifiable credentials](https://c2pa.org/specifications/specifications/1.4/specs/C2PA_Specification.html#_w3c_verifiable_credentials) standard recommendation (part of the C2PA specification), but doesn't currently have a way to validate these credentials or ensure that they properly reflect authorship of the content. An actor can add one or more identities to a manifest using the W3C verifiable credentials data model. Currently, a verifier must trust the manifest signer to properly authenticate the identity.
 
 Identity can be bolstered with other kinds of evidence such as _Adobe connected accounts_. In the future, the identity credentials will be separately verifiable. In the future, these verifiable credentials will be strongly bound to the manifest and media and be independently verifiable.
 
@@ -227,7 +227,7 @@ Embedding a manifest in an asset usually increases the size of the file. Two thi
 
 ### Storing a manifest in the cloud
 
-In addition to storing the manifest with the asset, Adobe tools use the _Adobe Content Credentials Cloud_, a public, persistent storage option for attribution and history data. Publishing to this cloud keeps files smaller and makes Content Credentials more resilient, because if stripped from an asset they can be recovered by searching at [verify.contentauthenticity.org](https://verify.contentauthenticity.org/). On the other hand, embedding the manifest keeps the file self-contained and means no web access is required to validate.
+In addition to storing the manifest with the asset, Adobe tools use the _Adobe Content Credentials Cloud_, a public, persistent storage option for attribution and history data. Publishing to this cloud keeps files smaller and makes Content Credentials more resilient, because if stripped from an asset they can be recovered by searching with the [C2PA Verify tool](https://verify.contentauthenticity.org/). On the other hand, embedding the manifest keeps the file self-contained and means no web access is required to validate.
 
 Currently, Adobe Content Credentials Cloud (ACCC) is only available to Adobe tools, though in the future other credentials clouds may become available if other organizations want to host a credential service. Currently, most manifests will be embedded in assets since ACCC is specific to Adobe.
 

docs/introduction.mdx

@@ -7,7 +7,7 @@ import cr_pin from '../static/img/cr-pin.png';
 import cai_open_source_red from '../static/img/cai-open-source-red.jpg';
 
 :::tip
-You're strongly encouraged to read this introduction and [Getting started](getting-started) to give you some basic background and context, before you dive right into development. [Working with manifests](manifest/understanding-manifest) also has some crucial information, regardless of which language and library you use.
+You're strongly encouraged to read this introduction and [Getting started](getting-started.mdx) to give you some basic background and context, before you dive right into development. [Working with manifests](manifest/understanding.md) also has some crucial information, regardless of which language and library you use.
 :::
 
 The Coalition for Content Provenance and Authenticity (C2PA) and Content Authenticity Initiative (CAI) are groups working together to develop and promote adoption of an open industry standard for content authenticity and provenance.
@@ -37,7 +37,7 @@ To see a summary of what each tool and library can do, see [Which tool is right
 
 ### JavaScript library
 
-The client [JavaScript library](js-sdk/getting-started/overview) enables **working with manifest data in the browser**. Use this library to:
+The client [JavaScript library](js-sdk/getting-started/overview.mdx) enables **working with manifest data in the browser**. Use this library to:
 
 - Verify and display manifest data on a website or web application.
 - Link manifest data displayed on your site to [Verify](https://verify.contentauthenticity.org/).

docs/trust-list.mdx

@@ -12,7 +12,7 @@ The C2PA **[Verify tool](https://contentcredentials.org/verify)** uses a list of
   style={{ width: '300px', display: 'block', margin: '10px auto' }}
 />
 
-Conversely, if the Content Credential was signed by a known certificate, the Verify tool will display the [name of the certificate owner and time of the claim signature](../verify#title-and-signing-information).
+Conversely, if the Content Credential was signed by a known certificate, the Verify tool will display the [name of the certificate owner and time of the claim signature](verify.mdx#title-and-signing-information).
 
 :::note
 The C2PA intends to publish an official public list of known certificates. Until then, **[Verify](https://contentcredentials.org/verify)** uses a temporary list. The list is subject to change and will be deprecated when C2PA publishes the official list.