mods, fix links

Author: genwhittTTD

docs/getting-started/gs-credentials.md

@@ -9,7 +9,7 @@ import Link from '@docusaurus/Link';
 
 # UID2 Credentials
 
-Each UID2 <a href="../intro#participants">participant</a> needs at least one set of unique credentials. The set of credentials you need is determined by how you are participating in UID2, as shown in the following table.
+Each UID2 <a href="../overviews/participants-overview#uid2-external-participants">participant</a> needs at least one set of unique credentials. The set of credentials you need is determined by how you are participating in UID2, as shown in the following table.
 
 | Audience | Credentials | Integration |
 | :--- | :--- | :--- |

docs/getting-started/gs-opt-out.md

@@ -9,7 +9,7 @@ import Link from '@docusaurus/Link';
 
 # User Opt-Out
 
-Many different publishers and advertisers use UID2. Different publishers might have different opt-out processes for their individual sites; however, UID2 as a whole has very specific opt-out processes that all UID2 [participants](../ref-info/glossary-uid.md#gl-participant) are expected to honor.
+Many different publishers and advertisers use UID2. Different publishers might have different opt-out processes for their individual sites; however, UID2 as a whole has very specific opt-out processes that all UID2 [participants](overviews/participants-overview.md#uid2-external-participants) are expected to honor.
 
 ## How Users Can Opt Out of UID2
 

docs/intro.md

@@ -10,23 +10,49 @@ import Link from '@docusaurus/Link';
 
 # Unified ID 2.0 Overview
 
-UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](#participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements.
+UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](overviews/participants-overview.md#uid2-external-participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements.
 
 :::note
 The term "UID2" can refer to either the framework or an actual identifier. Unless otherwise indicated, this page provides an overview of the UID2 framework.
 :::
 
 ## Guiding Principles
 
-For details, see [UID2 Guiding Principles](ref-info/uid-principles.md).
+The UID2 framework has the following principles as its foundation:
+
+- **First-party relationships**: UID2 enables advertisers to activate their first-party data on publisher websites across the open internet.
+
+- **Non-proprietary (universal) standard**: All [participants](overviews/participants-overview.md#uid2-external-participants) in the advertising ecosystem who execute an appropriate participation agreement can access UID2.
+
+- **Open source**: The source code for the [UID2 Component Services](overviews/participants-overview.md#uid2-component-services) is publicly available.
+
+- **Interoperable**: The framework allows other identity solutions (commercial and proprietary) to integrate and provide UID2 tokens with their offerings.
+
+- **Secure and encrypted data**: UID2 leverages multiple layers of security to help protect user and other participant data.
+
+- **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/).
+
+### Technical Design Principles
+
+The UID2 framework is built on the following technical principles:
+
+- **Distributed integration**: Multiple certified integration paths provide options for publishers, advertisers, and third-party data providers to manage and exchange UID2 tokens.
+
+- **Decentralized storage**: The framework does not have centralized storage for personal data (<Link href="ref-info/glossary-uid#gl-dii">DII</Link>) mappings. All participants maintain only their own data.
+
+- **Lean infrastructure**: The UID2 system is light and inexpensive to operate.
+
+- **Internet scale**: The UID2 infrastructure can scale to address the continuously increasing needs of [participants](overviews/participants-overview.md#uid2-external-participants) and to meet the performance demands of specific geographic regions.
+
+- **Self-reliant**: UID2 does not rely on external services for the processing of real-time bidding (RTB) data.
 
 ## Elements of the UID2 Infrastructure
 
 For details, see [UID2 Infrastructure](ref-info/uid-infrastructure.md).
 
 ## Components
 
-For details, see [xxx](ref-info/uid-infrastructure.md).
+For details, see [UID2 Component Services](overviews/participants-overview.md#uid2-component-services).
 
 ## FAQs
 

docs/overviews/overview-advertisers.md

@@ -58,7 +58,7 @@ To get started, follow these steps:
 1. Request access to UID2 by filling out the form on the [Request Access](/request-access) page.
 
    Someone will contact you to discuss your needs and advise on appropriate next steps.
-1. Decide on your [participant](../intro.md#participants) role or roles.
+1. Decide on your [participant](../overviews/participants-overview.md#uid2-external-participants) role or roles.
 1. Decide which implementation option you want to use.
 1. Receive your credentials (see [UID2 Credentials](../getting-started/gs-credentials.md)) and follow the instructions in the implementation guide for the option you chose.
 

docs/overviews/overview-data-providers.md

@@ -63,7 +63,7 @@ To get started, follow these steps:
 1. Request access to UID2 by filling out the form on the [Request Access](/request-access) page.
 
    Someone will contact you to discuss your needs and advise on appropriate next steps.
-1. Decide on your [participant](../intro.md#participants) role or roles.
+1. Decide on your [participant](../overviews/participants-overview.md#uid2-external-participants) role or roles.
 1. Decide which implementation option you want to use.
 1. Receive your credentials (see [UID2 Credentials](../getting-started/gs-credentials.md)) and follow the instructions in the implementation guide for the option you chose.
 

docs/overviews/participants-overview.md

@@ -26,8 +26,8 @@ For a diagram of how the different services work together, see [UID2 Workflows](
 
 | Participant | Role Description |
 | :--- | :--- |
-| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). 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. |
+| **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. |
 
 ## UID2 External Participants
 
@@ -50,8 +50,8 @@ Consumers can opt out of UID2 in the [Transparency and Control Portal](https://w
 
 <!-- | Participant | Role Description |
 | :--- | :--- |
-| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). 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. |
+| **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. |