Merge pull request #616 from hashicorp/repo-sync

Repo sync

Author: LeahMarieBush

content/hcp-docs/content/docs/hcp/europe.mdx

@@ -52,7 +52,7 @@ HCP Europe provides the following benefits to managing your cloud deployments:
 
 HCP Europe provides the same reliability and uninterrupted access to data as the global HCP platform. To provide 24-hour support, data from HCP Europe may be accessed from members of our support team in other regions.
 
-To learn more about our data governance policies, visit the [HashiCorp EU Trust Center](https://www.hashicorp.com/en/trust/eu).
+To learn more about our data governance policies, visit the [HashiCorp EU Trust Center](https://www.hashicorp.com/en/trust/privacy/hcp-data-privacy).
 
 ## Accounts
 

content/terraform-docs-common/docs/cloud-docs/api-docs/team-tokens.mdx

@@ -161,13 +161,13 @@ curl \
 
 ## List team tokens
 
-Lists the team tokens for the team.
+Lists the team tokens for the organization with the option to filter by team name.
 
-`GET /organizations/:organization_id/team-tokens`
+`GET /organizations/:organization_name/team-tokens`
 
 | Parameter            | Description                                              |
 |----------------------|----------------------------------------------------------|
-| `:organization_id`   | The ID of the organization whose team tokens you want to list.   |
+| `:organization_name` | The name of the organization whose team tokens you want to list. |
 
 This endpoint returns object metadata and does not include secret authentication details of tokens. You can only view a token when you create it and cannot recover it later.
 
@@ -257,7 +257,7 @@ Use this endpoint to display a particular [team token](/terraform/cloud-docs/use
 | ----------- | ------------------------- |
 | `:token_id` | The ID of the Team Token. |
 
-The object returned by this endpoint only contains metadata, and does not include the secret text of the authentication token. A token's secret test is only shown upon creation, and cannot be recovered later.
+The object returned by this endpoint only contains metadata, and does not include the secret text of the authentication token. A token's secret text is only shown upon creation and cannot be recovered later.
 
 | Status  | Response                                                | Reason                                                       |
 | ------- | ------------------------------------------------------- | ------------------------------------------------------------ |
@@ -416,7 +416,7 @@ curl \
 
 Lists the [team tokens](/terraform/cloud-docs/users-teams-organizations/teams#api-tokens) in an organization.
 
-`GET organizations/:organization_name/team-tokens`
+`GET /organizations/:organization_name/team-tokens`
 
 | Parameter            | Description                                              |
 |----------------------|----------------------------------------------------------|

content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/concepts.mdx

@@ -1,27 +1,27 @@
 ---
-page_title: Hold your own key concepts
+page_title: Hold your own key concepts for HCP Terraform
 description: >-
   Learn how HCP Terraform's hold your own key feature encrypts and decrypts state and plan data, which data HCP Terraform encrypts, and the effects of hold your own key encryption on state and plan files.
 tfc_only: true
 ---
 
 # Hold your own key concepts
 
-Hold your own key lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control.
+The hold your own key (HYOK) feature lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control.
 
 @include 'tfc-package-callouts/hyok.mdx'
 
 Terraform artifacts can contain sensitive information, such as resource IDs, IP addresses, credentials, and other configuration details that Terraform uses to manage infrastructure. To secure sensitive data, HCP Terraform uses a HashiCorp-managed key to encrypt sensitive data such as state and plan files before storage.
 
-Hold your own key (HYOK) gives you control over your sensitive data by letting you provide your own encryption key to safeguard that data. Hold your own key lets you configure HCP Terraform artifact encryption using a key from a key management system (KMS) that you control.
+The hold your own key (HYOK) feature gives you control over your sensitive data by letting you provide your own encryption key to safeguard that data. HYOK lets you configure HCP Terraform artifact encryption using a key from a key management system (KMS) that you control.
 
-When you enable hold your own key, the HCP Terraform agent encrypts specific Terraform  artifacts using a data encryption key (DEK) before uploading those files to HCP Terraform storage. To ensure you retain control of the DEK, the HCP Terraform agent authenticates with your key management service (KMS) and uses a key encryption key (KEK) to encrypt the DEK.
+When you enable hold your own key encryption, the HCP Terraform agent encrypts specific Terraform  artifacts using a data encryption key (DEK) before uploading those files to HCP Terraform storage. To ensure you retain control of the DEK, the HCP Terraform agent authenticates with your key management service (KMS) and uses a key encryption key (KEK) to encrypt the DEK.
 
 You can run the HCP Terraform agent on your own infrastructure, meaning that neither your KEK nor unencrypted secrets are uploaded to HCP Terraform, and no out-of-network traffic needs to connect to your KMS.
 
 ## What is encrypted
 
-The artifacts that HCP Terraform agents encrypt with hold your own key are:
+The artifacts that HCP Terraform agents encrypt with HYOK are:
 
 - [State files](/terraform/language/state) and [JSON state files](/terraform/internals/json-format).
 - [Plan files](/terraform/cli/commands/plan#out-filename) and [JSON plan files](/terraform/internals/json-format#plan-representation).
@@ -39,7 +39,7 @@ Learn more about [Sensitive data in state](/terraform/language/state/sensitive-d
 
 ## Sanitized state and plan files
 
-Hold your own key also produces sanitized versions of artifacts that redact secrets from the artifacts it encrypts. Sanitized state and plan files let HCP Terraform continue running policy checks, run tasks, cost estimation, and assessments without using sensitive data.
+The hold your own key (HYOK) feature also produces sanitized versions of artifacts that redact secrets from the artifacts it encrypts. Sanitized state and plan files let HCP Terraform continue running policy checks, run tasks, cost estimation, and assessments without using sensitive data.
 
 The sanitized state and sanitized plan artifacts are JSON files with the same content and format as the `json-state` and `json-plan` outputs, with sensitive data redacted.
 

content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/configure.mdx

@@ -1,7 +1,7 @@
 ---
-page_title: Configure and manage keys
+page_title: Configure and manage keys for HCP Terraform
 description: >-
-  Learn how to set up hold your own key encryption for HCP Terraform, letting you secure your sensitive data in state and plan files using a key from an external key management system.
+  Learn how to set up hold your own key (HYOK) encryption for HCP Terraform, letting you secure your sensitive data in state and plan files using a key from an external key management system.
 tfc_only: true
 ---
 

content/terraform-docs-common/docs/cloud-docs/hold-your-own-key/index.mdx

@@ -1,13 +1,13 @@
 ---
-page_title: Encrypt your state and plan files
+page_title: Encrypt your state and plan files for HCP Terraform
 description: >-
-  Hold your own key lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you control.
+  The hold your own key (HYOK) feature lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you control.
 tfc_only: true
 ---
 
 # Encrypt your state and plan files
 
-Hold your own key lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control.
+The hold your own key (HYOK) feature lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control.
 
 ## Introduction
 
@@ -17,35 +17,35 @@ Terraform artifacts can contain sensitive information, such as resource IDs, IP
 
 For most users, the default level of security that HCP Terraform provides is  sufficient. However, the side effect of default encryption is that HCP Terraform maintains access to your Terraform artifacts. You cannot monitor or revoke HCP Terraform's access to your artifacts, which might be insufficient for your compliance requirements.
 
-Hold your own key (HYOK) gives you control over your sensitive data by letting you provide your own encryption key to safeguard that data. Hold your own key lets you configure HCP Terraform artifact encryption using a key from a key management system (KMS) that you control. Use hold your own key to retain control of the keys HCP Terraform uses to encrypt data in state and plan files, enhance your security, and meet your compliance requirements.
+The hold your own key (HYOK) feature gives you control over your sensitive data by letting you provide your own encryption key to safeguard that data. HYOK lets you configure HCP Terraform artifact encryption using a key from a key management system (KMS) that you control. Use HYOK to retain control of the keys HCP Terraform uses to encrypt data in state and plan files, enhance your security, and meet your compliance requirements.
 
-When you enable hold your own key, the [HCP Terraform agent](/terraform/cloud-docs/agents) secures certain Terraform artifacts using your key before uploading those artifacts to HCP Terraform storage. To accomplish this, the HCP Terraform agent authenticates with your key management service, then encrypts the necessary artifacts. You can run the HCP Terraform agent on your own infrastructure, meaning that neither your key nor unencrypted secrets are ever uploaded to HCP Terraform, and no out-of-network traffic needs to connect to your key management service.
+When you enable HYOK, the [HCP Terraform agent](/terraform/cloud-docs/agents) secures certain Terraform artifacts using your key before uploading those artifacts to HCP Terraform storage. To accomplish this, the HCP Terraform agent authenticates with your key management service, then encrypts the necessary artifacts. You can run the HCP Terraform agent on your own infrastructure, meaning that neither your key nor unencrypted secrets are ever uploaded to HCP Terraform, and no out-of-network traffic needs to connect to your key management service.
 
-The artifacts that HCP Terraform agents encrypt with hold your own key are:
+The artifacts that HCP Terraform agents encrypt with HYOK are:
 
 - [State files](/terraform/language/state) and [JSON state files](/terraform/internals/json-format)
 - [Plan files](/terraform/cli/commands/plan#out-filename) and [JSON plan files](/terraform/internals/json-format#plan-representation)
 
-Hold your own key supports the following key management services:
+The hold your own key feature supports the following key management services:
 
 - AWS Key Management Service
 - Azure Key Vault
 - Google Cloud Key Management
 - Vault transit secrets engine
 
-To learn how to configure hold your own key for your organization, refer to [Configure and manage keys](/terraform/cloud-docs/hold-your-own-key/configure).
+To learn how to configure HYOK for your organization, refer to [Configure and manage keys](/terraform/cloud-docs/hold-your-own-key/configure).
 
-Hold your own key also produces sanitized versions of artifacts which redact secrets from the artifacts it encrypts. Sanitized state and plan files let HCP Terraform continue running policy checks, run tasks, cost estimation, and assessments without accessing sensitive data.
+The hold your own key feature also produces sanitized versions of artifacts which redact secrets from the artifacts it encrypts. Sanitized state and plan files let HCP Terraform continue running policy checks, run tasks, cost estimation, and assessments without accessing sensitive data.
 
 Refer to [How hold your own key concepts](/terraform/cloud-docs/hold-your-own-key/concepts) to learn more about the details of how HYOK encryption and decryption works.
 
 ## Workflow
 
-To create a key configuration for hold your own key, you must perform the following steps:
+To create a key configuration for HYOK, you must perform the following steps:
 
 1. Configure your key management system to accept OIDC requests from HCP Terraform, and create a key that your KMS will use to encrypt and decrypt the keys HYOK uses to secure your data.
 1. Configure your key in HCP Terraform.
-1. Enable hold your own key on one or more workspaces.
+1. Enable HYOK on one or more workspaces.
 
 ### Configure your KMS and create a key
 

content/terraform-docs-common/docs/partials/tfc-package-callouts/hyok.mdx

@@ -1,5 +1,5 @@
 <Note>
 
-Hold your own key is available on the HCP Terraform **Premium** edition. Refer to [HCP Terraform pricing](https://www.hashicorp.com/products/terraform/pricing) for details.
+The hold your own key feature is available on the HCP Terraform **Premium** edition. Refer to [HCP Terraform pricing](https://www.hashicorp.com/products/terraform/pricing) for details.
 
 </Note>