AWS prescriptive-guidance documentation change
Summary
Minor wording change from 'For many customers' to 'For many'
Security assessment
Grammatical edit with no security implications or content changes
Diff
diff --git a/prescriptive-guidance/latest/privacy-reference-architecture/operationalizing-aws-services.md b/prescriptive-guidance/latest/privacy-reference-architecture/operationalizing-aws-services.md index 3739dde0d..b12de856b 100644 --- a//prescriptive-guidance/latest/privacy-reference-architecture/operationalizing-aws-services.md +++ b//prescriptive-guidance/latest/privacy-reference-architecture/operationalizing-aws-services.md @@ -11 +11 @@ We would love to hear from you. Please provide feedback on the AWS PRA by taking -For many customers, privacy is cross-cutting. Many different teams have a part to play, including regulatory, compliance, and engineering teams. When your organization has started to define the key people and policy components of your privacy program, you can map controls against a privacy compliance framework for consistent operations. A framework can serve as a rubric for implementing foundational and application-specific privacy controls for personal data in your AWS environment. +For many, privacy is cross-cutting. Many different teams have a part to play, including regulatory, compliance, and engineering teams. When your organization has started to define the key people and policy components of your privacy program, you can map controls against a privacy compliance framework for consistent operations. A framework can serve as a rubric for implementing foundational and application-specific privacy controls for personal data in your AWS environment.