From fcc75176fd8d9ef551e0932dd9430415da3156fb Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:07:38 -0400 Subject: [PATCH 1/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.7.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.7.x/docs/intro/core-workflow.mdx b/content/terraform/v1.7.x/docs/intro/core-workflow.mdx index 0e675ded0d..5e69b4a085 100644 --- a/content/terraform/v1.7.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.7.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From f4884eb3c51997b2cf82abae04491c60adb9fa06 Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:14:57 -0400 Subject: [PATCH 2/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.1.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.1.x/docs/intro/core-workflow.mdx b/content/terraform/v1.1.x/docs/intro/core-workflow.mdx index e73cb326d2..15fde1a7fe 100644 --- a/content/terraform/v1.1.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.1.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From 73ec47e926df9fe8eea121da719804fa90fa1f0c Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:15:30 -0400 Subject: [PATCH 3/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.2.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.2.x/docs/intro/core-workflow.mdx b/content/terraform/v1.2.x/docs/intro/core-workflow.mdx index e73cb326d2..15fde1a7fe 100644 --- a/content/terraform/v1.2.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.2.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From c085f694bdd2f6e2b882cbed5517aca8e92f608c Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:15:48 -0400 Subject: [PATCH 4/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.3.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.3.x/docs/intro/core-workflow.mdx b/content/terraform/v1.3.x/docs/intro/core-workflow.mdx index e73cb326d2..15fde1a7fe 100644 --- a/content/terraform/v1.3.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.3.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From 6d37bf09beddf1fb960c641e1670980edb028ed5 Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:16:07 -0400 Subject: [PATCH 5/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.4.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.4.x/docs/intro/core-workflow.mdx b/content/terraform/v1.4.x/docs/intro/core-workflow.mdx index e73cb326d2..15fde1a7fe 100644 --- a/content/terraform/v1.4.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.4.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From 27f6d372b01b404098c3d1523827824dc13b1f7d Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:16:27 -0400 Subject: [PATCH 6/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.5.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.5.x/docs/intro/core-workflow.mdx b/content/terraform/v1.5.x/docs/intro/core-workflow.mdx index 0e675ded0d..5e69b4a085 100644 --- a/content/terraform/v1.5.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.5.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner From 273a4d11e60cbe25a88c2c16c36ac2da2dfbe790 Mon Sep 17 00:00:00 2001 From: Andrew Wilson <162396742+andrewwilson5454@users.noreply.github.com> Date: Sun, 31 Aug 2025 21:16:45 -0400 Subject: [PATCH 7/7] update name from Terraform Cloud to HCP Terraform --- content/terraform/v1.6.x/docs/intro/core-workflow.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform/v1.6.x/docs/intro/core-workflow.mdx b/content/terraform/v1.6.x/docs/intro/core-workflow.mdx index 0e675ded0d..5e69b4a085 100644 --- a/content/terraform/v1.6.x/docs/intro/core-workflow.mdx +++ b/content/terraform/v1.6.x/docs/intro/core-workflow.mdx @@ -13,7 +13,7 @@ The core Terraform workflow has three steps: This guide walks through how each of these three steps plays out in the context of working as an individual practitioner, how they evolve when a team is -collaborating on infrastructure, and how Terraform Cloud enables this +collaborating on infrastructure, and how HCP Terraform enables this workflow to run smoothly for entire organizations. ## Working as an Individual Practitioner