AWS privateca documentation change
Summary
Fixed typos: 'polices' to 'policies' in two places for grammatical accuracy
Security assessment
These are minor typographical corrections that don't relate to security issues or add security documentation. They improve readability but don't change security content.
Diff
diff --git a/privateca/latest/userguide/pca-rbp.md b/privateca/latest/userguide/pca-rbp.md index 89f64cb14..b83ba744f 100644 --- a//privateca/latest/userguide/pca-rbp.md +++ b//privateca/latest/userguide/pca-rbp.md @@ -29 +29 @@ This section provides example cross-account policies for various needs. In all c -In addition to specifying the ARN of a CA, the administrator provides an AWS account ID or an AWS Organizations ID that will be granted access to the CA. The JSON of each of the following polices is formatted as a file for readability, but can also be supplied as an inline CLI arguments. +In addition to specifying the ARN of a CA, the administrator provides an AWS account ID or an AWS Organizations ID that will be granted access to the CA. The JSON of each of the following policies is formatted as a file for readability, but can also be supplied as an inline CLI arguments. @@ -33 +33 @@ In addition to specifying the ARN of a CA, the administrator provides an AWS acc -The structure of the JSON resource-based polices shown below must be followed precisely. Only the ID fields for the principals (the AWS account number or the AWS Organizations ID) and the CA ARNs can be configured by customers. +The structure of the JSON resource-based policies shown below must be followed precisely. Only the ID fields for the principals (the AWS account number or the AWS Organizations ID) and the CA ARNs can be configured by customers.