Maurice review comments

Author: Rand McKinney

docs/getting-started.mdx

@@ -84,7 +84,7 @@ In practice, to use a certificate with the CAI SDK, follow this process:
 
 1. Purchase security credentials (certificate and key) from a certificate authority. Either email protection or document signing certificates are valid.
 2. Extract the certificate by using a tool such as OpenSSL. You could also host the certificate in a secure environment like a hardware security module (HSM).
-3. Use the Rust library or C2PA Tool to sign manifests using the certificate.
+3. Use one of the supporting CAI libraries or C2PA Tool to sign manifests using the certificate. Both the Rust library and the Python library providing signing support.
 
 :::tip
 For more details and a short tutorial example, see [Signing manifests](manifest/signing-manifests).
@@ -127,7 +127,7 @@ The _private key_ associated with the certificate is extremely sensitive. Always
 
 The simplest way to add a C2PA manifest to an asset file is by using C2PA Tool (`c2patool`). You can run C2PA Tool tool manually from the command line (for example, during development) and more generally from any executable program that can call out to the shell, such as a Node.js application as shown in the [c2patool Node.js service example](c2pa-service-example).
 
-You can also add Content Credentials using the prerelease libraries for [Node.js](c2pa-node/), [Python](c2pa-python/), and [C++/C](c2pa-c/)
+The prerelease libraries for [Node.js](c2pa-node/), [Python](c2pa-python/), and [C++/C](c2pa-c/) can also add and sign a manifest.
 
 Similarly, using the Rust SDK, you can [add a manifest to an asset file](https://docs.rs/c2pa/latest/c2pa/#example-adding-a-manifest-to-a-file), referencing the certificate and private key file. For a simple example of creating and signing a manifest from a C program, see the [c2c2pa repository](https://github.com/contentauth/c2c2pa).
 

docs/manifest/signing-manifests.md

@@ -49,7 +49,7 @@ Although not recommended due to complexity and difficulty, you can create your o
 
 ### Signature types
 
-The following table describes the signature algorithms and recommended signature types that the CAI SDK supports. You must supply credentials (certificates and keys) that correspond to the signing algorithm. Signing/validation will fail if the the supplied credentials don't support the signature type. 
+The following table describes the signature algorithms and signature types that the CAI SDK supports. You must supply credentials (certificates and keys) that correspond to the signing algorithm. Signing/validation will fail if the the supplied credentials don't support the signature type. 
 
 | Certificate `signatureAlgorithm` | Description  | Recommended signature type | RFC Reference |
 | -------------------------------- | ------------ | -------------------------- | ------------- |

docs/prod-cert.mdx

@@ -21,7 +21,7 @@ The certificate chain starts with the certificate from the last tool that signed
 
 ### Certificate signing requests (CSRs)
 
-A CSR is just an unsigned certificate that's a template for the certificate that you're requesting. The CA create a new certificate with the parameters specified in the CSR, and signs it with their root certificate, which makes it a "real" certificate.
+A CSR is just an unsigned certificate that's a template for the certificate that you're requesting. The CA create a new certificate with the parameters specified in the CSR, and signs it with their root certificate, which makes it a valid certificate.
 
 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, including 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.