Update content/terraform-docs-common/docs/docs/partnerships.mdx

bear359 · trujillo-adam · web-flow · commit 458c0c015cdc · 2025-10-02T08:32:29.000-06:00
Co-authored-by: trujillo-adam &lt;47586768+trujillo-adam@users.noreply.github.com&gt;
diff --git a/content/terraform-docs-common/docs/docs/partnerships.mdx b/content/terraform-docs-common/docs/docs/partnerships.mdx
@@ -216,7 +216,7 @@ For partners who are new to working with Hashicorp, we recommend [signing up for
 
 Partners should build an integration using the [run tasks APIs in HCP Terraform](/terraform/cloud-docs/api-docs/run-tasks/run-tasks). To learn more about how post-plan run tasks can enhance the HCP Terraform workflow, refer to the following diagram and read our [run tasks announcement](https://www.hashicorp.com/blog/terraform-cloud-run-tasks-beta-now-available). For a more hands-on experience with run tasks follow the [HCP Packer run tasks learn guide here](/terraform/tutorials/cloud/setup-hcp-terraform-run-task).
 
-Beyond run tasks, partners should leverage the [APIs in HCP Terraform](https://developer.hashicorp.com/terraform/cloud-docs/api-docs) or [APIs in Terraform Enterprise](https://developer.hashicorp.com/terraform/enterprise/api-docs) to programmatically manage most aspects of the platform and their accompanying integrations.
+Beyond run tasks, partners should leverage the [APIs in HCP Terraform](/terraform/cloud-docs/api-docs) or [APIs in Terraform Enterprise](/terraform/enterprise/api-docs) to programmatically manage most aspects of the platform and their accompanying integrations.
 
 Please note to consider network access configuration when integrating with Terraform Enterprise, specifically around configuring [secondary hostnames](https://developer.hashicorp.com/terraform/enterprise/deploy/reference/configuration#tfe_hostname_secondary) that allow Terraform Enterprise to connect to and integrate with external systems when deployed in a private environment
 
