diff --git a/docs/guides/operator-guide-aws-marketplace.md b/docs/guides/operator-guide-aws-marketplace.md index 9a98259cf..9e8209317 100644 --- a/docs/guides/operator-guide-aws-marketplace.md +++ b/docs/guides/operator-guide-aws-marketplace.md @@ -341,8 +341,8 @@ The following table includes some additional commands that might help you manage | Action | Command | | :--- | :--- | | Provides a detailed explanation of what will be rotated. | `sudo logrotate -f /etc/logrotate.conf --debug` | -| Runs one iteration of `logrotate` manually, without changing the scheduled interval. | `sudo logrotate -f /etc/logrotate.conf --force` | -| Reloads `syslog-ng`. | `sudo /usr/sbin/syslog-ng-ctl reload` | +| Runs one iteration of `logrotate` manually, without changing the scheduled interval. | `sudo logrotate -f /etc/logrotate.conf --force` | +| Reloads `syslog-ng`. | `sudo /usr/sbin/syslog-ng-ctl reload` | ## Technical Support diff --git a/docs/guides/operator-private-gcp-confidential-space.md b/docs/guides/operator-private-gcp-confidential-space.md index 846ac69cc..ba84f8edc 100644 --- a/docs/guides/operator-private-gcp-confidential-space.md +++ b/docs/guides/operator-private-gcp-confidential-space.md @@ -214,7 +214,7 @@ Provide values for the input parameters, as needed, in the `terraform.tfvars` fi | `network_name` | `string` | `uid-operator` | no | The VPC resource name (also used for rules/ instance tags). | | `min_replicas` | `number` | `1` | no | Indicates the minimum number of replicas you want to deploy. | | `max_replicas` | `number` | `5` | no | Indicates the maximum number of replicas you want to deploy. | - | `uid_operator_key_secret_name` | `string` | `"secret-operator-key"` | no | The name that you specify for your operator key secret. The Terraform template creates a secret in the GCP Secret Manager to hold the `uid_operator_key` value. You can define the name; for example, `uid2-operator-operator-key-secret-integ`. | + | `uid_operator_key_secret_name` | `string` | `"secret-operator-key"` | no | The name that you specify for your operator key secret. The Terraform template creates a secret in the GCP Secret Manager to hold the `uid_operator_key` value. You can define the name; for example, `uid2-operator-operator-key-secret-integ`. | | `debug_mode` | `bool` | `false` | no | Do not set to `true` unless you are working with the UID2 team to debug an issue. In any other circumstances, if you set this flag to `true`, attestation will fail. | #### Run Terraform diff --git a/docs/ref-info/glossary-uid.md b/docs/ref-info/glossary-uid.md index 0cf8ef86e..d73cebfe0 100644 --- a/docs/ref-info/glossary-uid.md +++ b/docs/ref-info/glossary-uid.md @@ -67,7 +67,7 @@ import Link from '@docusaurus/Link'; **N** Normalize - **O** +**O** Open Operator | Operator | Operator key | @@ -124,8 +124,8 @@ import Link from '@docusaurus/Link';
Advertising token is another term for a UID2 token.
API key
-
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
-
For details, see UID2 Credentials.
+
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
+
For details, see UID2 Credentials.
API secret
See client secret.
@@ -164,19 +164,19 @@ import Link from '@docusaurus/Link';
For details, see Subscription ID and Public Key.
Client secret
-
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
-
For details, see UID2 Credentials.
+
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
+
For details, see UID2 Credentials.
Client-server integration
One of the UID2 integration approaches is to integrate partially on the client side and partially on the server side (client-server).
For example, in a client-server integration for a publisher, the UID2 token is generated on the server side and refreshed on the client side.
-
Examples of documentation for publisher client-server integrations: UID2 Client-Server Integration Guide for Prebid.js, Client-Server Integration Guide for JavaScript, UID2 Client-Server Integration Guide for Mobile.
+
Examples of documentation for publisher client-server integrations:
- UID2 Client-Server Integration Guide for Prebid.js
- Client-Server Integration Guide for JavaScript
- UID2 Client-Server Integration Guide for Mobile
Client-side integration
One of the UID2 integration approaches is to integrate entirely on the client side.
In a client-side integration, UID2 tokens are generated and refreshed on the client side.
For example, in a client-side integration, advertisers generate UID2 tokens on the client side for tracking pixels, and publishers generate UID2 tokens on the client side for bidstream use, as well as refreshing the tokens.
-
Examples of documentation for publisher client-side integrations: UID2 Client-Side Integration Guide for Prebid.js, Client-Side Integration Guide for JavaScript, UID2 Client-Side Integration Guide for Mobile.
+
Examples of documentation for publisher client-side integrations:
- UID2 Client-Side Integration Guide for Prebid.js
- Client-Side Integration Guide for JavaScript
- UID2 Client-Side Integration Guide for Mobile
Closed Operator
Closed Operator is another term for a Private Operator.
@@ -200,7 +200,7 @@ import Link from '@docusaurus/Link';
Core Service
The UID2 Core Service is a centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem.
-
For an overview of all the UID2 services, see Components.
+
For an overview of all the UID2 services, see Components.
@@ -210,7 +210,7 @@ import Link from '@docusaurus/Link';
Data provider
In the context of UID2, a data provider is any entity that provides data and measurement services relating to advertising, such as a data partner, measurement partner, or offline measurement provider.
-
For details, see participant (Data Providers).
+
For details, see participant (Data Providers).
Demand-side platform
A demand-side platform (DSP) provides services to companies that want to buy digital advertising, such as advertisers, brands, and media agencies.
@@ -389,7 +389,7 @@ import Link from '@docusaurus/Link';
There are just over one million salt buckets, and each email address or phone number is assigned to a specific bucket in a deterministic manner. However, this assignment is not permanent; it might change when the bucket's current secret salt is rotated to a new value.
Salt bucket ID
-
A salt bucket ID is a unique string of characters that identifies a specific Salt bucket. The salt bucket ID can be used to check which salt buckets have recently had their salt values updated, indicating which emails or phone numbers need their raw UID2 values regenerated.
+
A salt bucket ID is a unique string of characters that identifies a specific salt bucket. The salt bucket ID can be used to check which salt buckets have recently had their salt values updated, indicating which emails or phone numbers need their raw UID2 values regenerated.
For an example of a salt bucket ID, see the response to the `POST /identity/buckets` endpoint: Decrypted JSON Response Format.
Salted hash
diff --git a/docs/sdks/summary-sdks.md b/docs/sdks/summary-sdks.md index 6740bec8e..a22dfd5b9 100644 --- a/docs/sdks/summary-sdks.md +++ b/docs/sdks/summary-sdks.md @@ -30,7 +30,7 @@ The following table summarizes the functionality available with each SDK. *Advertisers and Data Providers who need to generate raw UID2s from DII can also do this via Snowflake (see [Snowflake Integration Guide](../guides/snowflake_integration.md)) or by using the [POST /identity/map](../endpoints/post-identity-map.md) endpoint. - + ## SDK Documentation diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md index d96147a5c..c77de4619 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md @@ -67,7 +67,7 @@ import Link from '@docusaurus/Link'; **N** Normalize - **O** +**O** Open Operator | Operator | Operator key | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/summary-sdks.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/summary-sdks.md index ae94691f5..c1c00757d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/summary-sdks.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/summary-sdks.md @@ -30,7 +30,7 @@ SDK の機能を確認して使用する SDK を決定し、SDK の表をクリ *DII から raw UID2 を生成する必要がある広告主およびデータプロバイダは Snowflake ([Snowflake Integration Guide](../guides/snowflake_integration.md) を参照してください) または [POST /identity/map](../endpoints/post-identity-map.md) エンドポイントを使用することができます。 - + ## SDK Documentation