diff --git a/docs/getting-started/gs-encryption-decryption.md b/docs/getting-started/gs-encryption-decryption.md
index b0515ef75..6f99c8bb6 100644
--- a/docs/getting-started/gs-encryption-decryption.md
+++ b/docs/getting-started/gs-encryption-decryption.md
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 # Encrypting Requests and Decrypting Responses
 
 :::note
-If you're a publisher and are implementing UID2 on the client side, encryption and decryption is by your implementation, such as Prebid.js (see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [JavaScript Express Integration Guide](../guides/publisher-client-side.md)).
+If you're a publisher and are implementing UID2 on the client side, encryption and decryption is managed automatically by your implementation, such as Prebid.js (see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [JavaScript Express Integration Guide](../guides/publisher-client-side.md)).
 :::
 
 For almost all UID2 [endpoints](../endpoints/summary-endpoints.md), requests sent to the endpoint must be [encrypted](#encrypting-requests) and responses from the endpoint must be [decrypted](#decrypting-responses).