AWS connect documentation change
Summary
Updated language for clarity in hierarchy-based access control documentation, changing 'his hierarchy' to 'this hierarchy' and 'his or his supervisor's knowledge' to 'their supervisor's knowledge'
Security assessment
The changes are language improvements for clarity and inclusivity, not related to any specific security issue or feature
Diff
diff --git a/connect/latest/adminguide/hierarchy-based-access-control.md index da07ad498..d48464e34 100644 --- a/connect/latest/adminguide/hierarchy-based-access-control.md +++ b/connect/latest/adminguide/hierarchy-based-access-control.md @@ -73 +73 @@ For example, to enable granular access control for a given user based on the hie -This option ensures that the user being given access can only manage users that belong to his hierarchy. For example, enabling this configuration for a given user enables them to manage other users that either belong to their hierarchy group or a child hierarchy group. This ensures that the user being given access can only manage users that belong to his hierarchy. For example, enabling this configuration for a supervisor enables them to manage other users that either belong to their hierarchy group or a child hierarchy group. +This option ensures that the user being given access can only manage users that belong to this hierarchy. For example, enabling this configuration for a given user enables them to manage other users that either belong to their hierarchy group or a child hierarchy group. @@ -112 +112 @@ For example, if you try to assign a user to a quick connect but you don't have a - * Be thoughtful about the permissions granted on parent resources since a user could be disassociated without his or his supervisor’s knowledge. + * Be thoughtful about the permissions granted on parent resources since users could be disassociated without their supervisor’s knowledge.