From 01caf25f864f571769dd236d7eb919476cf70276 Mon Sep 17 00:00:00 2001 From: Reagan Middlebrook Date: Tue, 11 Apr 2023 15:11:02 -0700 Subject: [PATCH] Typo fix (changed 'wether' to 'whether') --- CCPA/USP API.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CCPA/USP API.md b/CCPA/USP API.md index 356eca5..ef59f09 100644 --- a/CCPA/USP API.md +++ b/CCPA/USP API.md @@ -108,7 +108,7 @@ To support sending and receiving of the US Privacy String within the US API, the As a baseline, digital properties must create a US Privacy String and make it available to vendors using this API. The created String communicates signals as compliant with the regulation that applies. -For example, in the case of CCPA, the String communicates wether CCPA applies in the given transaction, whether explicit notice was given to the consumer, the consumer's choice on opt-out of sale of data, and whether the transaction is operating under the IAB Limited Service Provider Agreement (LSPA). +For example, in the case of CCPA, the String communicates whether CCPA applies in the given transaction, whether explicit notice was given to the consumer, the consumer's choice on opt-out of sale of data, and whether the transaction is operating under the IAB Limited Service Provider Agreement (LSPA). ## Where should the string be stored?