AWS connect documentation change
Summary
Changed 'click' to 'choose' in UI interactions and 'leveraging' to 'using' for APIs
Security assessment
Terminology updates for consistency. No changes to notification security model or permissions structure.
Diff
diff --git a/connect/latest/adminguide/amazon-connect-notifications.md b/connect/latest/adminguide/amazon-connect-notifications.md index e820b31ee..011845a5a 100644 --- a//connect/latest/adminguide/amazon-connect-notifications.md +++ b//connect/latest/adminguide/amazon-connect-notifications.md @@ -30 +30 @@ Notifications support the following use cases: -Notifications display in the Connect header with an icon indicating an unread message(s). Users click the icon to view messages. +Notifications display in the Connect header with an icon indicating an unread message(s). Users choose the icon to view messages. @@ -40 +40 @@ The notification panel shows: - * **Mark as read** : Users can mark as read or unread by clicking on the actions menu on the right of each message + * **Mark as read** : Users can mark as read or unread by choosing on the actions menu on the right of each message @@ -55 +55 @@ Any user can _receive_ notifications without additional permissions, but special -To compose and send a notification requires API permissions. For more information about leveraging notification APIs see the [API guide](https://docs.aws.amazon.com/connect/latest/APIReference/actions-by-resource.html). +To compose and send a notification requires API permissions. For more information about using notification APIs see the [API guide](https://docs.aws.amazon.com/connect/latest/APIReference/actions-by-resource.html).