From c49756957d3186036b4a9984f0bcace85a110572 Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Wed, 10 Jan 2024 16:35:14 -0500 Subject: [PATCH] fix typo --- docs/getting-started/gs-encryption-decryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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).