user -> customer

Author: robin-aws

changes/2020-07-14_multi-keyring-require-generation/change.md

@@ -63,7 +63,7 @@ then its usefulness is limited.
 Customers might have a compliance requirement that all data keys MUST be generated by a specific HSM,
 or might want to lock down true least-privilege permissions for their AWS KMS key policies.
 Under the current model,
-users have to be very careful to make sure that they know
+customers have to be very careful to make sure that they know
 exactly where and how a given multi-keyring configuration is being used
 rather than being certain that it will always do the same thing no matter what.
 
@@ -79,7 +79,7 @@ between security and usability.
 ## Security Implications
 
 Removing this flexibility might help identify potential security issues,
-as users might discover when upgrading their ESDK version
+as customers might discover when upgrading their ESDK version
 that data keys are not being generated as intended.
 Correcting this will in turn provide the opportunity
 to improve their security postures