AWS documentdb documentation change
Summary
Minor editorial updates: replaced 'Please see' with 'See', changed 'listed above' to 'listed in the preceding section', and updated screenshot reference wording.
Security assessment
Changes are purely editorial improvements with no modification to security content. The updates don't address vulnerabilities or alter security guidance.
Diff
diff --git a/documentdb/latest/devguide/ca_cert_rotation.md b/documentdb/latest/devguide/ca_cert_rotation.md index abee039bb..33fa24ee3 100644 --- a//documentdb/latest/devguide/ca_cert_rotation.md +++ b//documentdb/latest/devguide/ca_cert_rotation.md @@ -64 +64 @@ For examples of using a CA bundle with your application, see [Encrypting data in -Currently, the MongoDB Go Driver 1.2.1 only accepts one CA server certificate in `sslcertificateauthorityfile`. Please see [Connecting with TLS enabled](./connect_programmatically.html#connect_programmatically-tls_enabled) for connecting to Amazon DocumentDB using Go when TLS is enabled. +Currently, the MongoDB Go Driver 1.2.1 only accepts one CA server certificate in `sslcertificateauthorityfile`. See [Connecting with TLS enabled](./connect_programmatically.html#connect_programmatically-tls_enabled) for connecting to Amazon DocumentDB using Go when TLS is enabled. @@ -83 +83 @@ Amazon DocumentDB provides the following CAs to sign the DB server certificate f -If you are using the AWS CLI, you can see the validities of the certificate authorities listed above by using [describe-certificates](https://docs.aws.amazon.com/cli/latest/reference/docdb/describe-certificates.html). +If you are using the AWS CLI, you can see the validities of the certificate authorities listed in the preceding section by using [describe-certificates](https://docs.aws.amazon.com/cli/latest/reference/docdb/describe-certificates.html). @@ -117 +117 @@ Complete the following steps to identify and rotate the old server certificate f - 5. In the **Clusters** table, you’ll see the column **Cluster identifier** on the far left. Your instances are listed under clusters, similar to the screenshot below. + 5. In the **Clusters** table, you’ll see the column **Cluster identifier** on the far left. Your instances are listed under clusters, similar to the following screenshot.