AWS connect documentation change
Summary
Minor terminology updates replacing 'leveraging' with 'using' and 'utilizing' with 'using' to improve consistency and readability.
Security assessment
Changes are purely stylistic word substitutions without modifying technical functionality, security implications, or adding security features. No evidence of vulnerability fixes or security improvements.
Diff
diff --git a/connect/latest/adminguide/ctr-contact-record-template.md b/connect/latest/adminguide/ctr-contact-record-template.md index bb8e7a050..d9ecf247f 100644 --- a//connect/latest/adminguide/ctr-contact-record-template.md +++ b//connect/latest/adminguide/ctr-contact-record-template.md @@ -40 +40 @@ In cases where neither the `_ctrContactId` key nor the `_phone` key yield an exi -This process ensures efficient handling of contact events, promoting auto-association with existing profiles and enabling the creation of inferred profiles when necessary. By leveraging these mechanisms, organizations can maintain a comprehensive record of customer interactions and effectively manage their contact event data within the system. +This process ensures efficient handling of contact events, promoting auto-association with existing profiles and enabling the creation of inferred profiles when necessary. By using these mechanisms, organizations can maintain a comprehensive record of customer interactions and effectively manage their contact event data within the system. @@ -58 +58 @@ The purpose of using the CTR-AutoAssociateOnly template is to enable automatic a -By utilizing the CTR-AutoAssociateOnly template, organizations can leverage auto-association while adhering to specific rules regarding profile creation. This approach allows for streamlined contact event handling and precise control over the profile ecosystem, ensuring accurate data representation and facilitating efficient customer management. +By using the CTR-AutoAssociateOnly template, organizations can use auto-association while adhering to specific rules regarding profile creation. This approach allows for streamlined contact event handling and precise control over the profile ecosystem, ensuring accurate data representation and facilitating efficient customer management. @@ -70 +70 @@ Although this behavior ensures that contact events are captured even when no pre -To address this concern and promote better profile management practices, we highly recommend utilizing the CTR-NoInferred template as the default option. By using the CTR-NoInferred template, the system eliminates the creation of inferred profiles, thereby reducing the occurrence of duplicate profiles. This template allows for a more streamlined and efficient handling of contact events, resulting in improved data integrity and accuracy. +To address this concern and promote better profile management practices, we highly recommend using the CTR-NoInferred template as the default option. By using the CTR-NoInferred template, the system eliminates the creation of inferred profiles, thereby reducing the occurrence of duplicate profiles. This template allows for a more streamlined and efficient handling of contact events, resulting in improved data integrity and accuracy.