Remove terraform from file names in website folder

website/data/language-nav-data.json

@@ -97,7 +97,7 @@
       },
       {
         "title": "The <code>terraform_data</code> Resource Type",
-        "path": "resources/terraform-data"
+        "path": "resources/tf-data"
       }
     ]
   },
@@ -917,7 +917,7 @@
     "title": "Terraform Settings",
     "routes": [
       { "title": "Overview", "path": "settings" },
-      { "title": "Terraform Cloud", "path": "settings/terraform-cloud" },
+      { "title": "Terraform Cloud", "path": "settings/tf-cloud" },
       {
         "title": "Backends",
         "routes": [

website/docs/language/meta-arguments/lifecycle.mdx

@@ -149,7 +149,7 @@ The arguments available within a `lifecycle` block are `create_before_destroy`,
   }
   ```
 
-  `replace_triggered_by` allows only resource addresses because the decision is based on the planned actions for all of the given resources. Plain values such as local values or input variables do not have planned actions of their own, but you can treat them with a resource-like lifecycle by using them with [the `terraform_data` resource type](/terraform/language/resources/terraform-data).
+  `replace_triggered_by` allows only resource addresses because the decision is based on the planned actions for all of the given resources. Plain values such as local values or input variables do not have planned actions of their own, but you can treat them with a resource-like lifecycle by using them with [the `terraform_data` resource type](/terraform/language/resources/tf-data).
 
 ## Custom Condition Checks
 

website/docs/language/resources/provisioners/null_resource.mdx

@@ -10,7 +10,7 @@ description: >-
 If you need to run provisioners that aren't directly associated with a specific
 resource, you can associate them with a `terraform_data`.
 
-Instances of [`terraform_data`](/terraform/language/resources/terraform-data) are treated
+Instances of [`terraform_data`](/terraform/language/resources/tf-data) are treated
 like normal resources, but they don't do anything. Like with any other resource
 type, you can configure [provisioners](/terraform/language/resources/provisioners/syntax)
 and [connection details](/terraform/language/resources/provisioners/connection) on a

website/docs/language/settings/backends/configuration.mdx

@@ -8,7 +8,7 @@ description: >-
 
 A backend defines where Terraform stores its [state](/terraform/language/state) data files.
 
-Terraform uses persisted state data to keep track of the resources it manages. Most non-trivial Terraform configurations either [integrate with Terraform Cloud](/terraform/language/settings/terraform-cloud) or use a backend to store state remotely. This lets multiple people access the state data and work together on that collection of infrastructure resources.
+Terraform uses persisted state data to keep track of the resources it manages. Most non-trivial Terraform configurations either [integrate with Terraform Cloud](/terraform/language/settings/tf-cloud) or use a backend to store state remotely. This lets multiple people access the state data and work together on that collection of infrastructure resources.
 
 This page describes how to configure a backend by adding the [`backend` block](#using-a-backend-block) to your configuration.
 
@@ -25,7 +25,7 @@ Some of these backends act like plain remote disks for state files, while others
 ## Using a Backend Block
 
 You do not need to configure a backend when using Terraform Cloud because
-Terraform Cloud automatically manages state in the workspaces associated with your configuration. If your configuration includes a [`cloud` block](/terraform/language/settings/terraform-cloud), it cannot include a `backend` block.
+Terraform Cloud automatically manages state in the workspaces associated with your configuration. If your configuration includes a [`cloud` block](/terraform/language/settings/tf-cloud), it cannot include a `backend` block.
 
 To configure a backend, add a nested `backend` block within the top-level
 `terraform` block. The following example configures the `remote` backend.

website/docs/language/settings/index.mdx

@@ -35,7 +35,7 @@ following sections.
 The nested `cloud` block configures Terraform Cloud for enabling its
 [CLI-driven run workflow](/terraform/cloud-docs/run/cli).
 
-- Refer to [Terraform Cloud Configuration](/terraform/language/settings/terraform-cloud) for a summary of the `cloud` block's syntax.
+- Refer to [Terraform Cloud Configuration](/terraform/language/settings/tf-cloud) for a summary of the `cloud` block's syntax.
 
 - Refer to [Using Terraform Cloud](/terraform/cli/cloud) in the
   Terraform CLI documentation for complete details about how to initialize and configure the Terraform Cloud CLI integration.

website/layouts/language.erb

@@ -143,7 +143,7 @@
           </li>
 
           <li>
-            <a href="/docs/language/resources/terraform-data.html">Terraform Data Resource Type</a>
+            <a href="/docs/language/resources/tf-data.html">Terraform Data Resource Type</a>
           </li>
 
         </ul>
@@ -867,7 +867,7 @@
           </li>
 
           <li>
-            <a href="/docs/language/settings/terraform-cloud.html">Terraform Cloud</a>
+            <a href="/docs/language/settings/tf-cloud.html">Terraform Cloud</a>
           </li>
 
           <li>