Merge pull request #273 from contentauth/link-fixes

More verify/inspect fixes

Author: crandmck

docs/getting-started/aca-inspect.mdx

@@ -7,12 +7,12 @@ import aca_inspect from '@site/static/img/aca-inspect.png';
 import inspect_actions from '@site/static/img/inspect_actions.png';
 import MarkdownCell from '@site/src/components/MarkdownCell';
 
-The [**Inspect tool on Adobe Content Authenticity (Beta)**](https://verify.contentauthenticity.org) (often referred to as "ACA Inspect" or simply "Inspect") is a [C2PA conforming validator product](../conformance.mdx#validator-products) that validates and displays Content Credentials for various asset types.
+The [**Inspect tool on Adobe Content Authenticity (Beta)**](https://inspect.cr) (often referred to as "ACA Inspect" or simply "Inspect") is a [C2PA conforming validator product](../conformance.mdx#validator-products) that validates and displays Content Credentials for various asset types.
 
 <img
   src={aca_inspect}
   style={{
-    width: '500px',
+    width: '600px',
     border: '1px solid #ccc',
   }}
 />
@@ -21,12 +21,7 @@ For more information, see [Inspect Content Credentials](https://helpx.adobe.com/
 
 ## How to use Inspect
 
-You can use Inspect to view Content Credentials for an asset in two ways:
-
-- [Upload an asset file](#uploading-an-asset) from your local computer.
-- [Use an asset URL](#using-an-asset-url).
-
-Supported asset file types include:
+You can use Inspect to view Content Credentials for the following asset file types:
 
 - **Image**: AVIF, DNG, GIF, HEIC, HEIF, JPEG, PNG, SVG, TIFF, and WebP.
 - **Video and audio**: AVI, M4A, MOV, MP3, MP4, and WAV.
@@ -36,6 +31,11 @@ Supported asset file types include:
 When you first load the site and no asset is displayed on the page, Inspect shows the complete current list of supported file types.
 :::
 
+You can use Inspect in two ways:
+
+- [Upload an asset file](#uploading-an-asset) from your local computer.
+- [Use an asset URL](#using-an-asset-url).
+
 ### Uploading an asset
 
 Click **Select a file from your device** then use the native picker or drag and drop a file to upload it and display information from the associated Content Credentials (if any) such as the author, the tools used to create the asset, and so on.
@@ -169,7 +169,7 @@ import verify_validation_error from '@site/static/img/verify-validation-error.pn
 Inspect displays this warning if the `validation_status` array contains any elements. For example, here is an snippet from the manifest of an image with a hard binding hash mismatch error,
 
 
-For example, a [this image](https://verify.contentauthenticity.org?source=https://spec.c2pa.org/public-testfiles/image/jpeg/adobe-20220124-E-dat-CA.jpg) with a hard binding hash mismatch error, as shown in [this manifest store](https://spec.c2pa.org/public-testfiles/image/jpeg/manifests/adobe-20220124-E-dat-CA/manifest_store.json):
+For example, a [this image](https://inspect.cr?source=https://spec.c2pa.org/public-testfiles/image/jpeg/adobe-20220124-E-dat-CA.jpg) with a hard binding hash mismatch error, as shown in [this manifest store](https://spec.c2pa.org/public-testfiles/image/jpeg/manifests/adobe-20220124-E-dat-CA/manifest_store.json):
 
 
 ```
@@ -182,7 +182,7 @@ For example, a [this image](https://verify.contentauthenticity.org?source=https:
   ]
 ```
 
-Another example that can result in this message is shown in [this image](https://verify.contentauthenticity.org?source=https://spec.c2pa.org/public-testfiles/image/jpeg/adobe-20220124-E-clm-CAICAI.jpg) with a missing referenced claim, as shown in [this manifest store](https://spec.c2pa.org/public-testfiles/image/jpeg/manifests/adobe-20220124-E-clm-CAICAI/manifest_store.json):
+Another example that can result in this message is shown in [this image](https://inspect.cr?source=https://spec.c2pa.org/public-testfiles/image/jpeg/adobe-20220124-E-clm-CAICAI.jpg) with a missing referenced claim, as shown in [this manifest store](https://spec.c2pa.org/public-testfiles/image/jpeg/manifests/adobe-20220124-E-clm-CAICAI/manifest_store.json):
 
 
 Another example that can result in this message is a missing referenced claim, as shown in snippet of manifest data:

docs/getting-started/faqs.mdx

@@ -35,7 +35,7 @@ Notable implementations using blockchain:
 
 ### Are Content Credentials about digital rights management?
 
-No; Content Credentials do not enforce permissions for access to content. In many cases, the name displayed by validator products such as the [**Inspect tool on Adobe Content Authenticity (Beta)**](https://verify.contentauthenticity.org) (ACA Inpsect) is the name of the exporter of the content, not the rights owner.
+No; Content Credentials do not enforce permissions for access to content. In many cases, the name displayed by validator products such as the [**Inspect tool on Adobe Content Authenticity (Beta)**](https://inspect.cr) (ACA Inpsect) is the name of the exporter of the content, not the rights owner.
 
 The [Title and signing information](aca-inspect.mdx#title-and-signing-information) in ACA Inspect refers to the name of the exporter. If the image was created with an Adobe Product such as Photoshop with Content Credentials (Beta) enabled, the "Produced by" section shows the name of the Adobe ID associated with the user who exported the image.
 

docs/getting-started/index.mdx

@@ -93,9 +93,9 @@ import verify_unknown_source from '@site/static/img/verify-cc-unknown-source.png
 
 The _C2PA trust list_ is a curated list of certification authorities (CAs) that are authorized to issue signing certificates for conforming generator products.
 
-Conforming validator products such as the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) use the C2PA trust list to determine whether a Content Credential was issued using a certificate that can be traced back to a CA on the C2PA trust list.
+Conforming validator products such as the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) use the C2PA trust list to determine whether a Content Credential was issued using a certificate that can be traced back to a CA on the C2PA trust list.
 
-Before the introduction of the C2PA trust list, during the early adoption phase of C2PA the C2PA [Verify tool](https://verify.contentauthenticity.org) used [the interim trust list](trust-list.mdx) to determine which certificates were considered valid and prevent unknown signers from appearing as valid. Verify will be updated to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
+Before the introduction of the C2PA trust list, during the early adoption phase of C2PA, the [Verify tool](https://verify.contentauthenticity.org) used [the interim trust list](trust-list.mdx) to determine which certificates were considered valid and prevent unknown signers from appearing as valid. Verify will be updated to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
 
 ## Identity
 
@@ -122,7 +122,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 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.
+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 someone can find them by searching with the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr). 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.
 
@@ -139,15 +139,15 @@ The example shown below illustrates one way to implement levels of disclosure:
 
 - The Content Credentials pin <img src={cr_pin} width="25" /> shown over the image indicates that the image has Content Credentials (level 1).
 - Clicking on the pin displays level 2 information, and an **Inspect** button.
-- Clicking the **Inspect** button opens the image on the [Verify site](https://verify.contentauthenticity.org/) that provides level 3 information.
+- Clicking the **Inspect** button opens the image on [ACA Inpsect](https://inspect.cr/) that provides level 3 information.
 
 <img src={cai_levels} width="800" />
 
 ## Example uses
 
 Numerous Adobe tools and products implement Content Credentials. For example, you can optionally attach credentials to images you create or modify using [Photoshop](https://helpx.adobe.com/photoshop/using/content-credentials.html) and [Lightroom](https://helpx.adobe.com/lightroom-cc/using/content-credentials-lightroom.html). Additionally, all images created using the [Firefly](https://blog.adobe.com/en/publish/2023/03/21/bringing-gen-ai-to-creative-cloud-adobe-firefly) generative AI tool automatically have attached Content Credentials. [Behance displays Content Credentials](https://www.behance.net/blog/cai-on-behance) if they are attached to media shared on the site, and still images provided through [Adobe Stock](https://stock.adobe.com/) automatically have Content Credentials attached. Other Adobe products also support Content Credentials.
 
-The [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) inspects image files and displays their Content Credentials if they exist. See [Using ACA Inspect](aca-inspect.mdx) for more information.
+The [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) inspects image files and displays their Content Credentials if they exist. See [Using ACA Inspect](aca-inspect.mdx) for more information.
 
 Additionally, several other organizations have implemented CAI solutions, including:
 

docs/signing/get-cert.md

@@ -48,7 +48,7 @@ A CSR is just an unsigned certificate that's a template for the certificate that
 A CSR comprises a public key, as well as ["distinguished name" information](https://knowledge.digicert.com/general-information/what-is-a-distinguished-name) that identifies the individual or organization requesting the certificate. The distinguished name includes a common name, organization, city, state, country, and e-mail address. Not all of these fields are required and will vary depending with the assurance level of the desired certificate.
 
 :::tip
-For the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) to display your organization name in the Content Credentials, your CSR must include the "O" or Organization Name attribute in the distinguished name information. 
+For the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) to display your organization name in the Content Credentials, your CSR must include the "O" or Organization Name attribute in the distinguished name information. 
 :::
 
 You sign the CSR with your private key; this proves to the CA that you have control of the private key that corresponds to the public key included in the CSR. Once the requested information in a CSR passes a vetting process and domain control is established, the CA may sign the public key to indicate that it can be publicly trusted.
@@ -74,7 +74,7 @@ You must select at least one of the extended key usage (EKU) fields that specify
 
 ### Organization name
 
-If you want the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) to display your organization name in the Content Credentials, your certificate must include the "O" or [Organization Name attribute](https://www.alvestrand.no/objectid/2.5.4.10.html) (OID value 2.5.4.10) in the distinguished name information. The CA may require some validation steps to prove you are part of that organization (details vary by CA).
+If you want the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) to display your organization name in the Content Credentials, your certificate must include the "O" or [Organization Name attribute](https://www.alvestrand.no/objectid/2.5.4.10.html) (OID value 2.5.4.10) in the distinguished name information. The CA may require some validation steps to prove you are part of that organization (details vary by CA).
 
 ### Signature types
 

docs/signing/local-signing.md

@@ -26,7 +26,7 @@ Accessing a private key and certificate directly from the file system is fine du
 Here is an example of getting signing credentials using [GlobalSign](http://globalsign.com/) certificate authority (CA) and then using them with C2PA Tool.  GlobalSign is just one of many CAs. For a list of some others, see [Getting a security certificate](get-cert.md#certificate-authorities-cas).
 
 :::note 
-This example uses an inexpensive personal certificate, which is fine for development and testing, but in production, an enterprise certificate is strongly recommended. An enterprise certificate is required for [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) to display your organization name when for signed assets.
+This example uses an inexpensive personal certificate, which is fine for development and testing, but in production, an enterprise certificate is strongly recommended. An enterprise certificate is required for [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) to display your organization name when for signed assets.
 :::
 
 ### 1. Purchase credentials 
@@ -157,5 +157,5 @@ This command displays the manifest attached to `signed_image.jpg` and should inc
 ```
 
 :::info
-You can also use the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) to confirm that your image was signed, but if you used a personal certificate (not an organization certificate) then it won't show [the organization name](get-cert.md#organization-name) and if your certificate is not on the [known certificate list](../getting-started/trust-list.mdx), it [displays the message](../getting-started/aca-inspect.mdx#title-and-signing-information) "The Content Credential issuer couldn't be recognized...."
+You can also use the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) to confirm that your image was signed, but if you used a personal certificate (not an organization certificate) then it won't show [the organization name](get-cert.md#organization-name) and if your certificate is not on the [known certificate list](../getting-started/trust-list.mdx), it [displays the message](../getting-started/aca-inspect.mdx#title-and-signing-information) "The Content Credential issuer couldn't be recognized...."
 :::

docs/signing/test-certs.md

@@ -15,6 +15,6 @@ While these test credentials are useful during development, you must [get your o
 
 Although not recommended due to complexity and difficulty, you can create your own certificates for development and testing. Follow the requirements in the C2PA Technical Specification [X.509 Certificates](https://c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html#x509_certificates) and [Digital Signatures](https://c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html#_digital_signatures) sections.
 
-For manifest claims signed with one of the test certificates, the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) will display the message "The Content Credential issuer couldn't be recognized."  See [Using ACA Inspect](../getting-started/aca-inspect.mdx#signing-information) for more information.
+For manifest claims signed with one of the test certificates, the [Inspect tool on Adobe Content Authenticity (Beta)](https://inspect.cr) will display the message "The Content Credential issuer couldn't be recognized."  See [Using ACA Inspect](../getting-started/aca-inspect.mdx#signing-information) for more information.
 
 

sidebars.js

@@ -198,7 +198,7 @@ const sidebars = {
         {
           type: 'doc',
           id: 'rust-sdk/docs/settings',
-          label: 'Configuring the SDK',
+          label: 'Configuring SDK settings',
         },
         {
           type: 'doc',