[Docs] Fix capitalization of HashiCorp

Author: pedrosousa

.github/styles/config/vocabularies/cloudflare/accept.txt

@@ -7,6 +7,7 @@ cloudflared
 Datadog
 GitHub
 GitLab
+HashiCorp
 Hono
 HTTP
 HTTPS

src/content/docs/fundamentals/api/how-to/make-api-calls.mdx

@@ -37,7 +37,7 @@ For specific guidance on making API calls, refer to the following resources:
 
 - The product's [Developer Docs section](/products/) for how-to guides.
 - [API schema docs](/api/) for request and response payloads for each endpoint.
-- The first-party libraries for [Go](https://github.com/cloudflare/cloudflare-go), [TypeScript](https://github.com/cloudflare/cloudflare-typescript), [Python](https://github.com/cloudflare/cloudflare-python), or [Hashicorp's Terraform](https://github.com/cloudflare/terraform-provider-cloudflare).
+- The first-party libraries for [Go](https://github.com/cloudflare/cloudflare-go), [TypeScript](https://github.com/cloudflare/cloudflare-typescript), [Python](https://github.com/cloudflare/cloudflare-python), or [HashiCorp's Terraform](https://github.com/cloudflare/terraform-provider-cloudflare).
 
 ## Query parameters
 

src/content/docs/terraform/tutorial/track-history.mdx

@@ -104,7 +104,7 @@ git commit -m "Step 2 - Initial commit with webserver definition."
  create mode 100644 cloudflare.tf
 ```
 
-Notice that the `.terraform` directory and `terraform.tfstate` file were not committed. The `.terraform` directory was not committed because the repository may be used on a different architecture, and the plugins contained in the directory are built for the system on which `terraform init` was run. The `terraform.tfstate` file was not committed because it may eventually contain sensitive strings, and it is not a good way to keep state in sync, as explained in Hashicorp's documentation on [Remote State](https://developer.hashicorp.com/terraform/language/state/remote).
+Notice that the `.terraform` directory and `terraform.tfstate` file were not committed. The `.terraform` directory was not committed because the repository may be used on a different architecture, and the plugins contained in the directory are built for the system on which `terraform init` was run. The `terraform.tfstate` file was not committed because it may eventually contain sensitive strings, and it is not a good way to keep state in sync, as explained in HashiCorp's documentation on [Remote State](https://developer.hashicorp.com/terraform/language/state/remote).
 
 To prevent Git from notifying you about the two files, add them to a new `.gitignore` file, commit it, and push everything to GitHub.
 

src/content/products/terraform.yaml

@@ -7,11 +7,11 @@ product:
 
 meta:
   title: Cloudflare Terraform docs
-  description: 
-    Manage your edge using the same familiar tools you use to automate the 
-    rest of your infrastructure, with Cloudflare’s Terraform provider. 
-    Define and store configuration in source code repositories like GitHub, 
-    track and version changes over time, and roll back when needed — all 
+  description:
+    Manage your edge using the same familiar tools you use to automate the
+    rest of your infrastructure, with Cloudflare's Terraform provider.
+    Define and store configuration in source code repositories like GitHub,
+    track and version changes over time, and roll back when needed — all
     without needing to learn the Cloudflare APIs.
   author: "@cloudflare"
 
@@ -20,7 +20,7 @@ externals:
     url: https://github.com/cloudflare/terraform-provider-cloudflare
   - title: Cloudflare in the Terraform registry
     url: https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/record
-  - title: Hashicorp Cloudflare integration
+  - title: HashiCorp Cloudflare integration
     url: https://www.hashicorp.com/integrations/cloudflare/terraform
   - title: Terraform homepage
     url: https://www.terraform.io/