[9/1] Update HCP Terraform and Waypoint package names [IPE-1232] (#861)

Author: BrianMMcClain

content/terraform-docs-common/docs/cloud-docs/api-docs/feature-sets.mdx

@@ -165,11 +165,11 @@ curl \
         "default-runs-ceiling": 10,
         "description": "Automated infrastructure provisioning and management at any scale",
         "global-run-tasks": true,
-        "identifier": "plus",
+        "identifier": "standard",
         "is-current": true,
         "is-free-tier": true,
         "module-tests-generation": true,
-        "name": "Plus",
+        "name": "Standard",
         "no-code-modules": true,
         "plan": null,
         "policy-enforcement": true,
@@ -322,11 +322,11 @@ curl \
         "default-runs-ceiling": 10,
         "description": "Automated infrastructure provisioning and management at any scale",
         "global-run-tasks": true,
-        "identifier": "plus",
+        "identifier": "standard",
         "is-current": true,
         "is-free-tier": true,
         "module-tests-generation": true,
-        "name": "Plus",
+        "name": "Standard",
         "no-code-modules": true,
         "plan": null,
         "policy-enforcement": true,

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

@@ -40,7 +40,7 @@ description: >-
 
 <!-- BEGIN: TFC:only name:pnp-callout -->
 
--> **Note:** Team management is available in HCP Terraform **Standard**, **Plus**, and **Premium** editions. Free organizations can also use this API, but can only manage membership of their owners team. [Learn more about HCP Terraform pricing here](https://www.hashicorp.com/products/terraform/pricing).
+-> **Note:** Team management is available in HCP Terraform **Essentials**, **Standard**, and **Premium** editions. Free organizations can also use this API, but can only manage membership of their owners team. [Learn more about HCP Terraform pricing here](https://www.hashicorp.com/products/terraform/pricing).
 
 <!-- END: TFC:only name:pnp-callout -->
 

content/terraform-docs-common/docs/cloud-docs/api-docs/workspaces.mdx

@@ -116,7 +116,7 @@ By supplying the necessary attributes under a `vcs-repository` object, you can c
 | `data.attributes.name` | string  | none | The name of the workspace. Workspace names can only include letters, numbers, `-`, and `_`. The name a unique identifier n the organization. |
 | `data.attributes.agent-pool-id` | string  | none | Required when `execution-mode` is set to `agent`. The ID of the agent pool belonging to the workspace's organization. This value must not be specified if `execution-mode` is set to `remote` or `local` or if `operations` is set to `true`. |
 | `data.attributes.allow-destroy-plan` | boolean | `true` | Whether destroy plans can be queued on the workspace. |
-| `data.attributes.assessments-enabled`           | boolean | `false`   | (previously `drift-detection`) Whether or not HCP Terraform performs health assessments for the workspace. May be overridden by the organization setting `assessments-enforced`. Only available for Plus tier organizations, in workspaces running Terraform version 0.15.4+ and operating in [Remote execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode). |
+| `data.attributes.assessments-enabled`           | boolean | `false`   | (previously `drift-detection`) Whether or not HCP Terraform performs health assessments for the workspace. May be overridden by the organization setting `assessments-enforced`. Only available for Standard tier organizations, in workspaces running Terraform version 0.15.4+ and operating in [Remote execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode). |
 | `data.attributes.auto-apply` | boolean | `false`   | Whether to automatically apply changes when a Terraform plan is successful in runs initiated by VCS, UI or CLI, [with some exceptions](/terraform/cloud-docs/workspaces/settings#auto-apply-and-manual-apply). |
 | `data.attributes.auto-apply-run-trigger`        | boolean | `false`   | Whether to automatically apply changes when a Terraform plan is successful in runs initiated by run triggers. |
 | `data.attributes.auto-destroy-at` | string  | (nothing) | Timestamp when the next scheduled destroy run will occur, refer to [Scheduled Destroy](/terraform/cloud-docs/workspaces/settings/deletion#automatically-destroy). |
@@ -538,7 +538,7 @@ Properties without a default value are required.
 | `data.attributes.name`                        | string         | (previous value) | A new name for the workspace, which can only include letters, numbers, `-`, and `_`. This will be used as an identifier and must be unique in the organization. **Warning:** Changing a workspace's name changes its URL in the API and UI.                                                                                                                                                                                                                                     |
 | `data.attributes.agent-pool-id`               | string         | (previous value) | Required when `execution-mode` is set to `agent`. The ID of the agent pool belonging to the workspace's organization. This value must not be specified if `execution-mode` is set to `remote` or `local` or if `operations` is set to `true`.                                                                                                                                                                                                                                   |
 | `data.attributes.allow-destroy-plan`          | boolean        | (previous value) | Whether destroy plans can be queued on the workspace.                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `data.attributes.assessments-enabled`         | boolean        | `false`          | (previously `drift-detection`) Whether or not HCP Terraform performs health assessments for the workspace. May be overridden by the organization setting `assessments-enforced`. Only available for Plus tier organizations, in workspaces running Terraform version 0.15.4+ and operating in [Remote execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode).                                                                                               |
+| `data.attributes.assessments-enabled`         | boolean        | `false`          | (previously `drift-detection`) Whether or not HCP Terraform performs health assessments for the workspace. May be overridden by the organization setting `assessments-enforced`. Only available for Standard tier organizations, in workspaces running Terraform version 0.15.4+ and operating in [Remote execution mode](/terraform/cloud-docs/workspaces/settings#execution-mode).                                                                                               |
 | `data.attributes.auto-apply`                  | boolean        | (previous value) | Whether to automatically apply changes when a Terraform plan is successful in runs initiated by VCS, UI or CLI, [with some exceptions](/terraform/cloud-docs/workspaces/settings#auto-apply-and-manual-apply).                                                                                                                                                                                                                                                                                                      |
 | `data.attributes.auto-apply-run-trigger`      | boolean        | (previous value) | Whether to automatically apply changes when a Terraform plan is successful in runs initiated by run triggers.                                                                                                                                                                                                                                                                                                    |
 | `data.attributes.auto-destroy-at`             | string         | (previous value) | Timestamp when the next scheduled destroy run will occur, refer to [Scheduled Destroy](/terraform/cloud-docs/workspaces/settings/deletion#automatically-destroy).                                                                                                                                                                                                                                                                                                               |

content/terraform-docs-common/docs/cloud-docs/index.mdx

@@ -13,7 +13,7 @@ tfc_only: true
 
 HCP Terraform is available as a hosted service at <https://app.terraform.io>. Small teams can sign up for free to connect Terraform to version control, share variables, run Terraform in a stable remote environment, and securely store remote state. Paid editions allow you to add more than five users, create teams with different levels of permissions, and collaborate more effectively.
 
-HCP Terraform **Plus** Edition allows organizations to enable audit logging, continuous validation, and automated configuration drift detection.
+HCP Terraform **Standard** Edition allows organizations to enable audit logging, continuous validation, and automated configuration drift detection.
 
 -> **Introducing HCP Terraform**: Effective April 22, 2024, Terraform Cloud is now HCP Terraform. HCP Terraform's functionality remains the same, and we plan to introduce new features soon to support a unified HCP experience. To learn more about HashiCorp's vision, refer to [Introducing the Infrastructure Cloud](https://www.hashicorp.com/blog/introducing-the-infrastructure-cloud).
 

content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx

@@ -99,7 +99,7 @@ $ echo -n $WEBHOOK_BODY | openssl dgst -sha512 -hmac "$HMAC_KEY"
 ```
 
 ## HCP Packer Run Task
-> **Hands On:** Try the [Set Up HCP Terraform Run Task for HCP Packer](/packer/tutorials/hcp/setup-hcp-terraform-run-task), [Standard tier run task image validation](/packer/tutorials/hcp/run-tasks-data-source-image-validation), and [Plus tier run task image validation](/packer/tutorials/hcp/run-tasks-resource-image-validation) tutorials to set up and test the HCP Terraform Run Task integration end to end.
+> **Hands On:** Try the [Set Up HCP Terraform Run Task for HCP Packer](/packer/tutorials/hcp/setup-hcp-terraform-run-task), [Essentials tier run task image validation](/packer/tutorials/hcp/run-tasks-data-source-image-validation), and [Standard tier run task image validation](/packer/tutorials/hcp/run-tasks-resource-image-validation) tutorials to set up and test the HCP Terraform Run Task integration end to end.
 
 [Packer](/packer) lets you create identical machine images for multiple platforms from a single source template. The [HCP Packer registry](/hcp/docs/packer) lets you track golden images, designate images for test and production environments, and query images to use in Packer and Terraform configurations.
 

content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/troubleshoot.mdx

@@ -96,7 +96,7 @@ To configure ServiceNow to poll HCP Terraform more frequently:
 
 If ServiceNow fails to deploy a no-code module catalog item, verify the following:
 
-1. Ensure that your HCP Terraform organization has an [HCP Plus tier](https://www.hashicorp.com/products/terraform/pricing) subscription. 
+1. Ensure that your HCP Terraform organization has an [HCP Standard tier](https://www.hashicorp.com/products/terraform/pricing) subscription. 
 1. Ensure the name you enter for your no-code module in the catalog user form matches the no-code module in HCP Terraform. 
 ### Updating no-code workspaces
 

content/terraform-docs-common/docs/cloud-docs/overview/activate-flex.mdx

@@ -7,7 +7,7 @@ tfc_only: true
 
 # Activate HashiCorp Flex
 
-Follow these steps to activate HashiCorp Flex for a **Standard**, **Plus**, or **Premium** edition HCP Terraform organization. 
+Follow these steps to activate HashiCorp Flex for a **Essentials**, **Standard**, or **Premium** edition HCP Terraform organization. 
 
 ## Prerequisites
 
@@ -54,7 +54,7 @@ to complete this step.
 
 Navigate to the **HCP Org > Billing**. If HashiCorp sales has allocated Flex, the page displays a **Contract Summary** with an available balance. If it only shows your credit card information or a $500 free trial credit, your HashiCorp Flex account may be scheduled to be allocated at a future date. Please contact your **HashiCorp Sales Account Manager** for more information.
 
-~> **Note**: All New HashiCorp organizations are automatically allocated $500 in trial credits. If your HashiCorp Flex account is not yet allocated, you can use the trial credits to temporarily activate **Standard Edition** for your HCP Terraform organization and immediately access paid features such as team management or more concurrency.
+~> **Note**: All New HashiCorp organizations are automatically allocated $500 in trial credits. If your HashiCorp Flex account is not yet allocated, you can use the trial credits to temporarily activate **Essentials Edition** for your HCP Terraform organization and immediately access paid features such as team management or more concurrency.
 
 ![A view of the HCP Terraform account summary showing billing summary and available balance](/img/docs/tfc-account-summary.png)
 

content/terraform-docs-common/docs/cloud-docs/overview/activate-payg.mdx

@@ -1,21 +1,21 @@
 ---
 page_title: Activate pay-as-you-go for HCP Terraform
 description: >-
-    Activate pay-as-you-go for your HCP Terraform organization in order to upgrade to standard, plus, or premium editions.
+    Activate pay-as-you-go for your HCP Terraform organization in order to upgrade to Essentials, Standard, or Premium editions.
 tfc_only: true
 ---
 
 # Pay-as-you-go
 
-Pay-as-you-go accounts are billed for the resources consumed. You can use pay-as-you-go for the **Standard**, **Plus**, and **Premium** editions. 
+Pay-as-you-go accounts are billed for the resources consumed. You can use pay-as-you-go for the **Essentials**, **Standard**, and **Premium** editions. 
 
 Pay-as-you-go offers dynamic billing based on monthly consumption. Larger organizations can access lower rates through Flex contracts. Review the [billing model documentation](/hcp/docs/hcp/admin/billing#billing-models) to determine which model is right for your organization.
 
 ## Activate pay-as-you-go
 
 To enable pay-as-you-go and change your organization's plan, sign in to [HCP Terraform](https://app.terraform.io/) and select your organization. Then choose **Settings** from the sidebar, then **Plan & Billing**. 
 
-In order to upgrade to **Standard**, **Plus**, or **Premium** edition and use pay-as-you-go billing, you must sign in to your HashiCorp Cloud Platform account and [link](/terraform/cloud-docs/users-teams-organizations/users#linking-hcp-and-hcp-terraform-accounts) your HCP Terraform account to your [HashiCorp Cloud Platform billing account](/hcp/docs/hcp/admin/billing). Click **Edit plan** to authenticate with HCP and link your accounts.
+In order to upgrade to **Essentials**, **Standard**, or **Premium** edition and use pay-as-you-go billing, you must sign in to your HashiCorp Cloud Platform account and [link](/terraform/cloud-docs/users-teams-organizations/users#linking-hcp-and-hcp-terraform-accounts) your HCP Terraform account to your [HashiCorp Cloud Platform billing account](/hcp/docs/hcp/admin/billing). Click **Edit plan** to authenticate with HCP and link your accounts.
 
 ![Screenshot: Notification reading that the user must link their HashiCorp Cloud Platform account to change their plan. Click the "edit plan" button](/img/docs/tfc-pnb-link-hcp.png)
 
@@ -25,7 +25,7 @@ Select the HCP organization to bill your usage to. Then click **Next**.
 
 Select the plan to use for your organization, then click **Next**.
 
-![Screenshot: The prompt allowing the user to select their HCP Terraform plan. Four choices are shown: Free, Standard, Plus, and Premium](/img/docs/tfc-select-plan.png)
+![Screenshot: The prompt allowing the user to select their HCP Terraform plan. Four choices are shown: Free, Essentials, Standard, and Premium](/img/docs/tfc-select-plan.png)
 
 Review your plan summary, then click **Activate**. Once activated, the new feature set will be available and usage and consumption will start immediately. Refer to [Estimate HCP Terraform cost](/terraform/cloud-docs/overview/estimate-hcp-terraform-cost) for more information on how to review your organization's consumption.
 

content/terraform-docs-common/docs/cloud-docs/overview/estimate-hcp-terraform-cost.mdx

@@ -7,15 +7,15 @@ tfc_only: true
 
 # Estimate HCP Terraform cost
 
-HCP Terraform offers [multiple plans](https://www.hashicorp.com/products/terraform/pricing) with increasing benefits to match your business scale. This page describes the flat rate per managed resource per hour for Standard Edition users on pay-as-you-go billing. Additional options are available such as greater discounts at larger scale with contracted plans. [Contact Sales](https://www.hashicorp.com/contact-sales) for additional information.
+HCP Terraform offers [multiple plans](https://www.hashicorp.com/products/terraform/pricing) with increasing benefits to match your business scale. This page describes the flat rate per managed resource per hour for Essentials Edition users on pay-as-you-go billing. Additional options are available such as greater discounts at larger scale with contracted plans. [Contact Sales](https://www.hashicorp.com/contact-sales) for additional information.
 
 ## What is a Managed Resource?
 
 A “Managed Resource” or “Resources Under Management (RUM)” is a resource in a Terraform-Cloud-managed state file where `mode = "managed"`. HCP Terraform counts a resource as part of this count starting from the first `terraform plan` or `terraform apply` operation on the resource. HCP Terraform does not include resources defined as a `null_resource` or `terraform_data` resource in the total managed resource count.
 
 Examples of managed resources include resources provisioned by a Terraform provider (e.g. an AWS VPC), by [count](/terraform/language/meta-arguments/count) and [for_each](/terraform/language/meta-arguments/for_each) meta-arguments, and resources provisioned by [modules](/terraform/language/modules) and [no-code ready modules](/terraform/cloud-docs/no-code-provisioning/module-design).  
 
-## Standard Edition cost on pay-as-you-go billing
+## Essentials Edition cost on pay-as-you-go billing
 
 HashiCorp charges for each managed resource on a per-hour basis, from the time a managed resource is provisioned until it is destroyed. Each partial hour is billed as a full hour. The peak number of managed resources in a given hour determines the cost. 
 
@@ -28,7 +28,7 @@ The Usage report gives an at a glance view of general usage limits in the Organi
 
 ![Screenshot: An example of an organization's usage report, showing a count of 1001 total managed resources](/img/docs/tfc-org-usage.png)
 
-An example on HCP Terraform **Standard Edition** that assumes 24x7 usage for a full month for 1000 Managed Resources:
+An example on HCP Terraform **Essentials Edition** that assumes 24x7 usage for a full month for 1000 Managed Resources:
 
 - Per Hour Price: 1000 Managed Resources x $0.0001359 = **$0.14**  
 - Per Month Price: (Per Hour Price x 24 x 30) = **$97.85**