updates per mtg with KK

genwhittTTD · genwhittTTD · commit 91dfa560cc0e · 2025-03-27T15:48:40.000-04:00
diff --git a/docs/guides/integration-javascript-client-server.md b/docs/guides/integration-javascript-client-server.md
@@ -124,8 +124,6 @@ Based on the status and availability of a valid identity, the SDK does the follo
 1. Stores identity information in [local storage or a first-party cookie](../sdks/sdk-ref-javascript.md#uid2-storage-format).
 1. Uses the identity information to initiate requests for targeted advertising.
 
-<!-- (**GWH_TODO. Q: Not sure about the relationship between the steps above and the table below. And the diagram 2-a which says "the publisher calls the SSP for ads using the UID2 token". A: Diagram needs to be updated.**) -->
-
 The bidding step is shown in the following table.
 
 | Step | Endpoint/SDK | Description |
diff --git a/docs/intro.md b/docs/intro.md
@@ -32,7 +32,7 @@ The UID2 framework has the following principles as its foundation:
 
 - **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/).
 
-### Technical Design Principles
+## Technical Design Principles
 
 The UID2 framework is built on the following technical principles:
 
@@ -48,17 +48,13 @@ The UID2 framework is built on the following technical principles:
 
 ## Elements of the UID2 Infrastructure
 
-For information about key elements of the UID2 infrastructure, refer to the following pages:
+For information about key elements of the UID2 infrastructure, and other aspects of UID2, refer to the following pages:
 
 - [UID2 Identifier Types](ref-info/uid-identifier-types.md)
 - [UID2 Components](ref-info/uid-components.md)
 - [UID2 Participants](overviews/participants-overview.md)
 - [Workflows](ref-info/uid-workflows.md)
 
-## Components
-
-For details, see [UID2 Component Services](overviews/participants-overview.md#uid2-component-services).
-
 ## FAQs
 
 See [Frequently Asked Questions](getting-started/gs-faqs.md).
diff --git a/docs/overviews/participants-overview.md b/docs/overviews/participants-overview.md
@@ -31,14 +31,14 @@ For a diagram of how the different services work together, see [UID2 Workflows](
 
 ## UID2 External Participants
 
-The following table summarizes the main types of external participant partners for UID2.
+The following table summarizes the main types of external participant partners for UID2, with a link to the overview page for more information on each participant type.
 
-| Participant | Role Description | Link to Overview Page |
-| :--- | :--- | :--- |
-| **Publishers** | Organizations that propagate UID2 tokens to the bidstream via SSPs—for example, identity providers, publishers, and SSO providers. Publishers can choose to work with an SSO provider or an independent ID provider that is interoperable with UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | [UID2 Overview for Publishers](overview-publishers.md) |
-| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | [UID2 Overview for Advertisers](overview-advertisers.md) |
-| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | [UID2 Overview for DSPs](overview-dsps.md) |
-| **Data Providers** | Organizations that collect user data and push it to other UID2 participants&#8212;for example, advertisers, identity graph providers, and third-party data providers. | [UID2 Overview for Data Providers](overview-data-providers.md) |
+| Participant Type | Role Description |
+| :--- | :--- |
+| [Publishers](overview-publishers.md) | Organizations that propagate UID2 tokens to the bidstream via SSPs—for example, identity providers, publishers, and SSO providers. Publishers can choose to work with an SSO provider or an independent ID provider that is interoperable with UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. |
+| [Advertisers](overview-advertisers.md) | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. |
+| [DSPs](overview-dsps.md) | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. |
+| [Data Providers](overview-data-providers.md) | Organizations that collect user data and push it to other UID2 participants&#8212;for example, advertisers, identity graph providers, and third-party data providers. |
 
 ## UID2 Consumers
 
@@ -47,13 +47,3 @@ A UID2 consumer is a user who has had a UID2 token or raw UID2 created from an e
 UID2 leverages multiple layers of security to help protect user and other participant data. UID2 is a privacy-compliant identifier. With UID2, consumers can enjoy more personalized advertising without compromising privacy.
 
 Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/).
-
-<!-- | Participant | Role Description |
-| :--- | :--- |
-| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other component services. For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. |
-| **Operators** | Organizations that run the <Link href="../ref-info/glossary-uid#gl-operator-service">Operator Service</Link> (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash <Link href="../ref-info/glossary-uid#gl-dii">directly identifying information (DII)</Link> to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.<br/>Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.<br/>Any participant can also choose to become a Private Operator to generate and manage UID2s. |
-| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. |
-| **Data Providers** | Organizations that collect user data and push it to other UID2 participants&#8212;for example, advertisers, identity graph providers, and third-party data providers. |
-| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. |
-| **Publishers** | Organizations that propagate UID2 tokens to the bidstream via SSPs—for example, identity providers, publishers, and SSO providers. Publishers can choose to work with an SSO provider or an independent ID provider that is interoperable with UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. |
-| **Consumers** | Users who have had a UID2 token or raw UID2 created from their email address or phone number. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). | -->
diff --git a/docs/ref-info/uid-identifier-types.md b/docs/ref-info/uid-identifier-types.md
@@ -1,6 +1,6 @@
 ---
 title: UID2 Identifier Types
-description: Summary of xxx.
+description: Information about UID2 identifier types (raw UID2s and UID2 tokens).
 hide_table_of_contents: false
 sidebar_position: 01
 displayed_sidebar: docs
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md
@@ -124,8 +124,6 @@ SDKは、指定された [callback function](../sdks/sdk-ref-javascript.md#callb
 1. ID 情報を [ローカルストレージまたはファーストパーティクッキー](../sdks/sdk-ref-javascript.md#uid2-storage-format) に保存します。
 1. ID 情報を使用して、ターゲティング広告のリクエストを始めます。
 
-<!-- (**GWH_TODO. Q: Not sure about the relationship between the steps above and the table below. And the diagram 2-a which says "the publisher calls the SSP for ads using the UID2 token". A: Diagram needs to be updated.**) -->
-
 ビッドステップを次の表に示します。
 
 | Step | Endpoint/SDK | Description |
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md
@@ -92,8 +92,6 @@ To deploy a new UID2 Private Operator for AKS, you'll need to complete the follo
 
 ### Download ZIP File and Extract Files
 
-[**KC__GWH01 I've commented out some of what we had -- it doesn't make sense to include the table unless we add AKS to the release matrix. We need to include instructions to get the file. What I'm putting here is just a guess... please fix as needed.**]
-
 To get set up with the installation files, follow these steps:
 
 1. Ask your UID2 contact for the ZIP file containing the deployment files.
@@ -116,8 +114,6 @@ The latest ZIP file is linked in the AKS Download column in the following table.
 
 Run the following commands to prepare environment variables that you'll use later. Choose variable names to suit your needs.
 
-[**KC__GWH02 do we need to say where they need to run these commands? Maybe not... just checking. At the Azure command line?**]
-
 ```
 export RESOURCE_GROUP="my-vn-aks"
 export LOCATION="eastus"
@@ -135,7 +131,7 @@ export DEPLOYMENT_ENV="integ"
 
 ### Set Up AKS and Node Pool
 
-To set up AKS and the node pool, complete the following steps: [**KC__GWH03 do they have to be done in sequence? If so we could use numbers rather than bullets**]
+To set up AKS and the node pool, complete the following steps:
 
 - [Create Resource Group](#create-resource-group)
 - [Create Virtual Network](#create-virtual-network)
@@ -172,7 +168,7 @@ There are some limitations with regard to location:
 
 #### Create Virtual Network
 
-To create the virtual network, run the following command, using your own values as needed: [**KC__GWH04 please verify the intro line/modify as needed**]
+To create the virtual network, run the following command, using your own values as needed:
 
 ```
 az network vnet create \
@@ -184,7 +180,7 @@ az network vnet create \
 
 #### Create Subnets
 
-To create the subnets, run the following command, using your own values as needed: [**KC__GWH05 please verify the intro line/modify as needed**]
+To create the subnets, run the following command, using your own values as needed:
 
 ```
 # Default Subnet (10.0.0.0/24)
@@ -212,15 +208,15 @@ az network vnet subnet create \
 
 #### Create Public IP Address
 
-To create the public IP address, run the following command, using your own values as needed: [**KC__GWH06 please verify the intro line/modify as needed**]
+To create the public IP address, run the following command, using your own values as needed:
 
 ```
 az network public-ip create --name ${PUBLIC_IP_ADDRESS_NAME} --resource-group ${RESOURCE_GROUP} --sku standard --allocation static
 ```
 
 #### Create NAT Gateway
 
-To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed: [**KC__GWH07 please verify the intro line/modify as needed**]
+To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed:
 
 ```
 az network nat gateway create \
@@ -232,7 +228,7 @@ az network nat gateway create \
 
 #### Configure NAT Service for Source Subnet
 
-To configure the NAT service, run the following command, using your own values as needed: [**KC__GWH08 please verify the intro line/modify as needed**]
+To configure the NAT service, run the following command, using your own values as needed:
 
 ```
 az network vnet subnet update \
@@ -244,7 +240,7 @@ az network vnet subnet update \
 
 #### Get the AKS Subnet ID
 
-To create the AKS subnet ID, run the following command, using your own values as needed: [**KC__GWH09 please verify the intro line/modify as needed**]
+To create the AKS subnet ID, run the following command, using your own values as needed:
 
 ```
 export AKS_SUBNET_ID=$(az network vnet subnet show \
@@ -257,7 +253,7 @@ export AKS_SUBNET_ID=$(az network vnet subnet show \
 
 #### Create an AKS Service
 
-To create the AKS service, run the following command, using your own values as needed: [**KC__GWH10 please verify the intro line/modify as needed**]
+To create the AKS service, run the following command, using your own values as needed:
 
 ```
 # Create the AKS cluster
@@ -284,7 +280,7 @@ az aks create \
 
 #### Get the Principal ID of the Managed Identity
 
-To get the Principal ID, run the following command, using your own values as needed: [**KC__GWH11 please verify the intro line/modify as needed.**]
+To get the Principal ID, run the following command, using your own values as needed:
 
 ```
 export MANAGED_IDENTITY_PRINCIPAL_ID="$(az aks show --resource-group ${RESOURCE_GROUP} --name ${AKS_CLUSTER_NAME} --query "identityProfile.kubeletidentity.clientId" --output tsv)"
@@ -294,7 +290,7 @@ For details, see [Get the principal ID of the system-assigned managed identity](
 
 #### Create Contributor Role for the Two Resource Groups
 
-To create the contributor role for each group, run the following commands, using your own values as needed: [**KC__GWH12 please verify the intro line/modify as needed**]
+To create the contributor role for each group, run the following commands, using your own values as needed:
 
 ```
 az role assignment create \
@@ -314,7 +310,7 @@ Additional reference information in external documentation:
 
 ### Set Up AKS Cluster
 
-To set up the AKS cluster, run the following command, using your own values as needed: [**KC__GWH13 please verify the intro line/modify as needed**]
+To set up the AKS cluster, run the following command, using your own values as needed:
 
 ```
 az aks get-credentials --name ${AKS_CLUSTER_NAME} --resource-group ${RESOURCE_GROUP}
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md
@@ -16,7 +16,7 @@ UID2 は、広告エコシステム全体の多くの [参加者](overviews/part
 「UID2」という用語は、フレームワークと実際の識別子のいずれかを指すことがあります。特に断りのない限り、このページでは UID2 フレームワークの概要を説明します。
 :::
 
-### Guiding Principles
+## Guiding Principles
 
 UID2 フレームワークは、以下の原則を基本としています:
 
@@ -32,7 +32,7 @@ UID2 フレームワークは、以下の原則を基本としています:
 
 - **Consumer control**: 消費者はいつでも [Transparency and Control Portal](https://www.transparentadvertising.com/) を通じて UID2 からの脱退を選択できます。
 
-### Technical Design Principles
+## Technical Design Principles
 
 UID2 フレームワークは、以下の技術原則に基づいて構築されています:
 
@@ -75,10 +75,6 @@ UID2 は、メールアドレスや電話番号など、<Link href="ref-info/glo
 これらの例で使用されている架空のメールアドレス `user@example.com` に対応する Refresh Token は次のとおりです: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`.
 ::: -->
 
-### Components
-
-詳細については、[UID2 Component Services](overviews/participants-overview.md#uid2-component-services)
-
 <!-- ### Participants 
 
 UID2 は透明で相互運用可能なアプローチにより、広告エコシステム全体、すなわち広告主、パブリッシャー、DSP、SSP、シングルサインオン (SSO)プロバイダー、カスタマーデータプラットフォーム (CDP)、同意管理プロバイダー (CMP)、ID プロバイダー、サードパーティデータプロバイダー、測定プロバイダーなどの多くの参加者に協調フレームワークを提供しています。
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md
