From 4441fcfec0a2e24c78f70f6dd4a3061d540ec37a Mon Sep 17 00:00:00 2001
From: trujillo-adam <ajosetru@gmail.com>
Date: Thu, 14 Nov 2024 16:08:41 -0800
Subject: [PATCH 1/2] restructure language reference

---
 website/data/language-nav-data.json           |  76 ++---
 .../index.mdx}                                |  11 +-
 .../provisioners/connect.mdx}                 |   0
 .../provisioners/define.mdx}                  |   0
 .../define-resource/provisioners/index.mdx    |   0
 .../provisioners/null_resource.mdx            |   2 +-
 .../terraform-data.mdx                        |  11 +-
 .../language/{resources => }/ephemeral.mdx    |   0
 website/docs/language/provisioner.mdx         | 320 ++++++++++++++++++
 website/docs/language/resource.mdx            |  72 ++++
 website/docs/language/resources/index.mdx     |  36 --
 .../language/resources/provisioners/file.mdx  | 129 -------
 .../resources/provisioners/local-exec.mdx     | 104 ------
 .../resources/provisioners/remote-exec.mdx    |  89 -----
 website/docs/language/resources/syntax.mdx    | 214 ------------
 15 files changed, 431 insertions(+), 633 deletions(-)
 rename website/docs/language/{resources/behavior.mdx => define-resource/index.mdx} (94%)
 rename website/docs/language/{resources/provisioners/connection.mdx => define-resource/provisioners/connect.mdx} (100%)
 rename website/docs/language/{resources/provisioners/syntax.mdx => define-resource/provisioners/define.mdx} (100%)
 create mode 100644 website/docs/language/define-resource/provisioners/index.mdx
 rename website/docs/language/{resources => define-resource}/provisioners/null_resource.mdx (97%)
 rename website/docs/language/{resources => define-resource}/terraform-data.mdx (87%)
 rename website/docs/language/{resources => }/ephemeral.mdx (100%)
 create mode 100644 website/docs/language/provisioner.mdx
 create mode 100644 website/docs/language/resource.mdx
 delete mode 100644 website/docs/language/resources/index.mdx
 delete mode 100644 website/docs/language/resources/provisioners/file.mdx
 delete mode 100644 website/docs/language/resources/provisioners/local-exec.mdx
 delete mode 100644 website/docs/language/resources/provisioners/remote-exec.mdx
 delete mode 100644 website/docs/language/resources/syntax.mdx

diff --git a/website/data/language-nav-data.json b/website/data/language-nav-data.json
index b23ca5d1502d..b17bf1e06224 100644
--- a/website/data/language-nav-data.json
+++ b/website/data/language-nav-data.json
@@ -70,75 +70,33 @@
     ]
   },
   {
-    "title": "Resources",
+    "title": "Define resources",
     "routes": [
-      { "title": "Overview", "path": "resources" },
-      { "title": "Resource Blocks", "path": "resources/syntax" },
+      { "title": "Overview", "path": "define-resource" },
       {
-        "title": "Resource Behavior",
-        "path": "resources/behavior"
-      },
-      {
-        "title": "Meta-Arguments",
+        "title": "Apply provisioners",
         "routes": [
           {
-            "title": "<code>depends_on</code>",
-            "href": "/language/meta-arguments/depends_on"
-          },
-          {
-            "title": "<code>count</code>",
-            "href": "/language/meta-arguments/count"
-          },
-          {
-            "title": "<code>for_each</code>",
-            "href": "/language/meta-arguments/for_each"
+            "title": "Overview",
+            "path": "define-resource/provisioners"
           },
-          {
-            "title": "<code>provider</code>",
-            "href": "/language/meta-arguments/resource-provider"
-          },
-          {
-            "title": "<code>lifecycle</code>",
-            "href": "/language/meta-arguments/lifecycle"
-          }
-        ]
-      },
-      {
-        "title": "Provisioners",
-        "routes": [
           {
             "title": "Declaring Provisioners",
-            "path": "resources/provisioners/syntax"
+            "path": "define-resource/provisioners/define"
           },
           {
             "title": "Provisioner Connections",
-            "path": "resources/provisioners/connection"
-          },
-          {
-            "title": "Provisioners Without a Resource",
-            "path": "resources/provisioners/null_resource"
-          },
-          {
-            "title": "file",
-            "path": "resources/provisioners/file"
-          },
-          {
-            "title": "local-exec",
-            "path": "resources/provisioners/local-exec"
+            "path": "define-resource/provisioners/connect"
           },
           {
-            "title": "remote-exec",
-            "path": "resources/provisioners/remote-exec"
+            "title": "Run commands on standard lifecycle resources",
+            "path": "define-resource/provisioners/null_resource"
           }
         ]
       },
       {
-        "title": "The <code>terraform_data</code> Resource Type",
-        "path": "resources/terraform-data"
-      },
-      {
-        "title": "Ephemeral Resources",
-        "path": "resources/ephemeral"
+        "title": "Apply standard lifecycle",
+        "path": "define-resource/terraform-data"
       }
     ]
   },
@@ -257,6 +215,14 @@
       }
     ]
   },
+  {
+    "title": "Resource block",
+    "path": "resource"
+  },
+  {
+    "title": "Ephemeral block",
+    "path": "ephemeral"
+  },
   {
     "title": "Moved block",
     "path": "moved"
@@ -265,6 +231,10 @@
     "title": "Terraform block",
     "path": "terraform"
   },
+  {
+    "title": "Provisioner block",
+    "path": "provisioner"
+  },
   {
     "title": "Backend block",
     "routes": [
diff --git a/website/docs/language/resources/behavior.mdx b/website/docs/language/define-resource/index.mdx
similarity index 94%
rename from website/docs/language/resources/behavior.mdx
rename to website/docs/language/define-resource/index.mdx
index c65de9d1f45f..7f43fdec20fe 100644
--- a/website/docs/language/resources/behavior.mdx
+++ b/website/docs/language/define-resource/index.mdx
@@ -1,11 +1,14 @@
 ---
-page_title: Resource Behavior - Configuration Language
+page_title: Manage resources in Terraform configuration language
 description: >-
-  Learn how Terraform uses resource blocks to create infrastructure objects.
-  Also learn about resource dependencies and how to access resource attributes.
+  Resource blocks define real-world resources. Learn how to define resource blocks to create and manage infrastructure resources with Terraform.
 ---
 
-# Resource Behavior
+# Manage resources in Terraform configuration language
+
+This topic provides an overview of the Terraform `resource` block.
+
+## Introduction
 
 A `resource` block declares that you want a particular infrastructure object
 to exist with the given settings. If you are writing a new configuration for
diff --git a/website/docs/language/resources/provisioners/connection.mdx b/website/docs/language/define-resource/provisioners/connect.mdx
similarity index 100%
rename from website/docs/language/resources/provisioners/connection.mdx
rename to website/docs/language/define-resource/provisioners/connect.mdx
diff --git a/website/docs/language/resources/provisioners/syntax.mdx b/website/docs/language/define-resource/provisioners/define.mdx
similarity index 100%
rename from website/docs/language/resources/provisioners/syntax.mdx
rename to website/docs/language/define-resource/provisioners/define.mdx
diff --git a/website/docs/language/define-resource/provisioners/index.mdx b/website/docs/language/define-resource/provisioners/index.mdx
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/website/docs/language/resources/provisioners/null_resource.mdx b/website/docs/language/define-resource/provisioners/null_resource.mdx
similarity index 97%
rename from website/docs/language/resources/provisioners/null_resource.mdx
rename to website/docs/language/define-resource/provisioners/null_resource.mdx
index b91430807b14..2d22f0b4c8b9 100644
--- a/website/docs/language/resources/provisioners/null_resource.mdx
+++ b/website/docs/language/define-resource/provisioners/null_resource.mdx
@@ -5,7 +5,7 @@ description: >-
   are not directly associated with a single existing resource.
 ---
 
-# Provisioners Without a Resource
+# Run commands on standard lifecycle resources
 
 If you need to run provisioners that aren't directly associated with a specific
 resource, you can associate them with a `terraform_data`.
diff --git a/website/docs/language/resources/terraform-data.mdx b/website/docs/language/define-resource/terraform-data.mdx
similarity index 87%
rename from website/docs/language/resources/terraform-data.mdx
rename to website/docs/language/define-resource/terraform-data.mdx
index 4e82c4481575..598bedfdffd8 100644
--- a/website/docs/language/resources/terraform-data.mdx
+++ b/website/docs/language/define-resource/terraform-data.mdx
@@ -1,13 +1,18 @@
 ---
-page_title: The terraform_data Managed Resource Type
+page_title: Apply the standard Terraform resource lifecycle
 description: >-
   Retrieves the root module output values from a Terraform state snapshot stored
   in a remote backend.
 ---
 
-# The `terraform_data` Managed Resource Type
+# Apply the standard Terraform resource lifecycle
+
+This topic describes how to configure resources to follow the standard Terraform resource lifecycle. 
+
+## Configure the `terraform_data` resource type
+
+The `terraform_data` resource type implements the standard resource lifecycle for the resource but does not directly take any other actions. 
 
-The `terraform_data` implements the standard resource lifecycle, but does not directly take any other actions. 
 You can use the `terraform_data` resource without requiring or configuring a provider. It is always available through a built-in provider with the [source address](/terraform/language/providers/requirements#source-addresses) `terraform.io/builtin/terraform`.
 
 The `terraform_data` resource is useful for storing values which need to follow a manage resource lifecycle, and for triggering provisioners when there is no other logical managed resource in which to place them.
diff --git a/website/docs/language/resources/ephemeral.mdx b/website/docs/language/ephemeral.mdx
similarity index 100%
rename from website/docs/language/resources/ephemeral.mdx
rename to website/docs/language/ephemeral.mdx
diff --git a/website/docs/language/provisioner.mdx b/website/docs/language/provisioner.mdx
new file mode 100644
index 000000000000..362a133aca59
--- /dev/null
+++ b/website/docs/language/provisioner.mdx
@@ -0,0 +1,320 @@
+---
+page_title: provisioner block reference
+description: Learn how to configure the Terraform `resource` block.
+---
+
+# `provisioner` block
+
+This topic provides reference information about the `provisioner` block in the Terraform configuration language. Add `provisioner` blocks to `resource` blocks in your Terraform configurations to perform additional actions during Terraform operations.
+
+Refer to the following topics for additional information:
+
+- [`resource` block reference](/terraform/language/resource)
+- [Usage topics for provisioners](linky-link)
+
+## Configuration model
+
+Add `provisioner` blocks to `resource` blocks in your configuration. You can specify the following types of `provisioner` blocks:
+
+- `provisioner "file" "<LABEL>"`
+- `provisioner "local-exec" "<LABEL>"`
+- `provisioner "remote-exec" "<LABEL>"`
+
+### `provisioner "file"`
+
+The `file` provisioner copies files or directories from the machine
+running Terraform to the newly created resource. The `file` provisioner
+supports both `ssh` and `winrm` type [connections](/terraform/language/resources/provisioners/connection).
+
+~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
+[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
+
+## Example usage
+
+```hcl
+resource "aws_instance" "web" {
+  # ...
+
+  # Copies the myapp.conf file to /etc/myapp.conf
+  provisioner "file" {
+    source      = "conf/myapp.conf"
+    destination = "/etc/myapp.conf"
+  }
+
+  # Copies the string in content into /tmp/file.log
+  provisioner "file" {
+    content     = "ami used: ${self.ami}"
+    destination = "/tmp/file.log"
+  }
+
+  # Copies the configs.d folder to /etc/configs.d
+  provisioner "file" {
+    source      = "conf/configs.d"
+    destination = "/etc"
+  }
+
+  # Copies all files and folders in apps/app1 to D:/IIS/webapp1
+  provisioner "file" {
+    source      = "apps/app1/"
+    destination = "D:/IIS/webapp1"
+  }
+}
+```
+
+-> **Note:** When the `file` provisioner communicates with a Windows system over SSH, you must configure OpenSSH to run the commands with `cmd.exe` and not PowerShell. PowerShell causes file parsing errors because it is incompatible with both Unix shells and the Windows command interpreter.
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `source` - The source file or directory. Specify it either relative to the
+  current working directory or as an absolute path.
+  This argument cannot be combined with `content`.
+
+* `content` - The direct content to copy on the destination.
+  If destination is a file, the content will be written on that file. In case
+  of a directory, a file named `tf-file-content` is created inside that
+  directory. We recommend using a file as the destination when using `content`.
+  This argument cannot be combined with `source`.
+
+* `destination` - (Required) The destination path to write to on the remote
+  system. See [Destination Paths](#destination-paths) below for more
+  information.
+
+## Destination Paths
+
+The path you provide in the `destination` argument will be evaluated by the
+remote system, rather than by Terraform itself. Therefore the valid values
+for that argument can vary depending on the operating system and remote access
+software running on the target.
+
+When connecting over SSH, the `file` provisioner passes the given destination
+path verbatim to the `scp` program on the remote host. By default, OpenSSH's
+`scp` implementation runs in the remote user's home directory and so you can
+specify a relative path to upload into that home directory, or an absolute
+path to upload to some other location. The remote `scp` process will run with
+the access level of the user specified in the `connection` block, and so
+permissions may prevent writing directly to locations outside of the home
+directory.
+
+Because WinRM has no corresponding file transfer protocol, for WinRM
+connections the `file` provisioner uses a more complex process:
+
+1. Generate a temporary filename in the directory given in the remote system's
+   `TEMP` environment variable, using a pseudorandom UUID for uniqueness.
+2. Use sequential generated `echo` commands over WinRM to gradually append
+   base64-encoded chunks of the source file to the chosen temporary file.
+3. Use an uploaded PowerShell script to read the temporary file, base64-decode,
+   and write the raw result into the destination file.
+
+In the WinRM case, the destination path is therefore interpreted by PowerShell
+and so you must take care not to use any meta-characters that PowerShell might
+interpret. In particular, avoid including any untrusted external input in
+your `destination` argument when using WinRM, because it can serve as a vector
+for arbitrary PowerShell code execution on the remote system.
+
+Modern Windows systems support running an OpenSSH server, so we strongly
+recommend choosing SSH over WinRM whereever possible, and using WinRM only as
+a last resort when working with obsolete Windows versions.
+
+## Directory Uploads
+
+The `file` provisioner can upload a complete directory to the remote machine.
+When uploading a directory, there are some additional considerations.
+
+When using the `ssh` connection type the destination directory must already
+exist. If you need to create it, use a remote-exec provisioner just prior to
+the file provisioner in order to create the directory
+
+When using the `winrm` connection type the destination directory will be
+created for you if it doesn't already exist.
+
+The existence of a trailing slash on the source path will determine whether the
+directory name will be embedded within the destination, or whether the
+destination will be created. For example:
+
+* If the source is `/foo` (no trailing slash), and the destination is `/tmp`,
+  then the contents of `/foo` on the local machine will be uploaded to
+  `/tmp/foo` on the remote machine. The `foo` directory on the remote machine
+  will be created by Terraform.
+
+* If the source, however, is `/foo/` (a trailing slash is present), and the
+  destination is `/tmp`, then the contents of `/foo` will be uploaded directly
+  into `/tmp`.
+
+## `provider "local-exec"` 
+
+The `local-exec` provisioner invokes a local executable after a resource is
+created. This invokes a process on the machine running Terraform, not on the
+resource. See the `remote-exec`
+[provisioner](/terraform/language/resources/provisioners/remote-exec) to run commands on the
+resource.
+
+Note that even though the resource will be fully created when the provisioner is
+run, there is no guarantee that it will be in an operable state - for example
+system services such as `sshd` may not be started yet on compute resources.
+
+~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
+[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
+
+## Example usage
+
+```hcl
+resource "aws_instance" "web" {
+  # ...
+
+  provisioner "local-exec" {
+    command = "echo ${self.private_ip} >> private_ips.txt"
+  }
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `command` - (Required) This is the command to execute. It can be provided
+  as a relative path to the current working directory or as an absolute path.
+  The `command` is evaluated in a shell and can use environment variables for
+  variable substitution. We do not recommend using Terraform variables for variable
+  substitution because doing so can lead to shell injection vulnerabilities. Instead, you should pass Terraform variables to a command
+  through the `environment` parameter and use environment variable substitution
+  instead. Refer to the following OWASP article for additional information about injection flaws: [Code Injection](https://owasp.org/www-community/attacks/Code_Injection).
+
+* `working_dir` - (Optional) If provided, specifies the working directory where
+  `command` will be executed. It can be provided as a relative path to the
+  current working directory or as an absolute path. The directory must exist.
+
+* `interpreter` - (Optional) If provided, this is a list of interpreter
+  arguments used to execute the command. The first argument is the
+  interpreter itself. It can be provided as a relative path to the current
+  working directory or as an absolute path.  The remaining arguments are
+  appended prior to the command.  This allows building command lines of the
+  form "/bin/bash", "-c", "echo foo". If `interpreter` is unspecified,
+  sensible defaults will be chosen based on the system OS.
+
+* `environment` - (Optional) block of key value pairs representing the
+  environment of the executed command. inherits the current process environment.
+
+* `when` - (Optional) If provided, specifies when Terraform will execute the command.
+  For example, `when = destroy` specifies that the provisioner will run when the associated resource
+  is destroyed. Refer to [Destroy-Time Provisioners](/terraform/language/resources/provisioners/syntax#destroy-time-provisioners)
+  for details.
+  
+*  `quiet` - (Optional) If set to `true`, Terraform will not print the command to be executed to stdout, and will instead print "Suppressed by quiet=true". Note that the output of the command will still be printed in any case.
+
+### Interpreter Examples
+
+```hcl
+resource "terraform_data" "example1" {
+  provisioner "local-exec" {
+    command = "open WFH, '>completed.txt' and print WFH scalar localtime"
+    interpreter = ["perl", "-e"]
+  }
+}
+```
+
+```hcl
+resource "terraform_data" "example2" {
+  provisioner "local-exec" {
+    command = "Get-Date > completed.txt"
+    interpreter = ["PowerShell", "-Command"]
+  }
+}
+```
+
+```hcl
+resource "aws_instance" "web" {
+  # ...
+
+  provisioner "local-exec" {
+    command = "echo $FOO $BAR $BAZ >> env_vars.txt"
+
+    environment = {
+      FOO = "bar"
+      BAR = 1
+      BAZ = "true"
+    }
+  }
+}
+```
+
+## `provisioner "remote-exec"` Provisioner`"
+
+The `remote-exec` provisioner invokes a script on a remote resource after it
+is created. This can be used to run a configuration management tool, bootstrap
+into a cluster, etc. To invoke a local process, see the `local-exec`
+[provisioner](/terraform/language/resources/provisioners/local-exec) instead. The `remote-exec`
+provisioner requires a [connection](/terraform/language/resources/provisioners/connection)
+and supports both `ssh` and `winrm`.
+
+~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
+[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
+
+## Example usage
+
+```hcl
+resource "aws_instance" "web" {
+  # ...
+
+  # Establishes connection to be used by all
+  # generic remote provisioners (i.e. file/remote-exec)
+  connection {
+    type     = "ssh"
+    user     = "root"
+    password = var.root_password
+    host     = self.public_ip
+  }
+
+  provisioner "remote-exec" {
+    inline = [
+      "puppet apply",
+      "consul join ${aws_instance.web.private_ip}",
+    ]
+  }
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `inline` - This is a list of command strings. The provisioner uses a default
+  shell unless you specify a shell as the first command (eg., `#!/bin/bash`). 
+  You cannot provide this with `script` or `scripts`.
+
+* `script` - This is a path (relative or absolute) to a local script that will
+  be copied to the remote resource and then executed. This cannot be provided
+  with `inline` or `scripts`.
+
+* `scripts` - This is a list of paths (relative or absolute) to local scripts
+  that will be copied to the remote resource and then executed. They are executed
+  in the order they are provided. This cannot be provided with `inline` or `script`.
+
+-> **Note:** Since `inline` is implemented by concatenating commands into a script, [`on_failure`](/terraform/language/resources/provisioners/syntax#failure-behavior) applies only to the final command in the list. In particular, with `on_failure = fail` (the default behaviour) earlier commands will be allowed to fail, and later commands will also execute. If this behaviour is not desired, consider using `"set -o errexit"` as the first command.
+
+## Script Arguments
+
+You cannot pass any arguments to scripts using the `script` or
+`scripts` arguments to this provisioner. If you want to specify arguments,
+upload the script with the
+[file provisioner](/terraform/language/resources/provisioners/file)
+and then use `inline` to call it. Example:
+
+```hcl
+resource "aws_instance" "web" {
+  # ...
+
+  provisioner "file" {
+    source      = "script.sh"
+    destination = "/tmp/script.sh"
+  }
+
+  provisioner "remote-exec" {
+    inline = [
+      "chmod +x /tmp/script.sh",
+      "/tmp/script.sh args",
+    ]
+  }
+}
+```
diff --git a/website/docs/language/resource.mdx b/website/docs/language/resource.mdx
new file mode 100644
index 000000000000..911c74140c06
--- /dev/null
+++ b/website/docs/language/resource.mdx
@@ -0,0 +1,72 @@
+---
+page_title: resource block reference
+description: Learn how to configure the Terraform `resource` block.
+---
+
+# `resource` block
+
+This topic provides reference information about the `resource` block in the Terraform configuration language. 
+
+## Introduction
+
+Add `resource` blocks to your Terraform configuration to describe one or more infrastructure objects, such as virtual networks, compute instances, or higher-level components such as DNS records. Specific arguments that you can define in your configuration depend on the providers you import. 
+
+Refer to the following topics for additional information:
+
+[usage topic about configuring the resource block]()
+[usage topic about configuring the provider block]()
+[provider block reference]()
+
+## Configuration model
+
+The following list provides an overview of the attributes you can declare in the `resource` block:
+
+`resource "<TYPE>" "<LABEL>"`
+- `<PROVIDER_ARGUMENTS>`
+- `count`: number 
+- `depends_on`: list
+- `for_each`:  map or set of one element
+- `provider`: short desc of value
+- `lifecycle`: short desc of value
+- `provisioner "<TYPE>" "<LABEL>"` 
+
+## Specification
+
+This section provides details about the arguments you can configure in the `resource` block. Specific providers and backends may support additional fields.
+
+### `resource`
+
+The main `resource` block accepts the following attributes:
+
+`TYPE`: Specifies the type of resource you can declare depends on the provider you import. Refer to the documentation for your provider for details. You can also specify the `terraform_data` resource type to implement a standard resource lifecycle. Refer [Implement the standard resource lifecycle](linky-link) for additional information
+`LABEL`: Specifies an arbitrary name for the resource that you can use to reference the resource from other configuration elements. Refer to [Resource naming](/terraform/language/style#resource-naming) in the style guide for label recommendations.
+
+### `PROVIDER_ARGUMENTS`
+
+Specific arguments that you can define in your configuration depend on the providers you import. Refer to the documentation for your provider for details.  
+### `resource{}.count`
+
+Meta-argument that instructs Terraform to provision the number of identical resources specified. Additional information. Refer to [`count` reference](/terraform/language/meta-arguments/count) for details.   
+### `resource{}.depends_on`
+
+### `resource{}.for_each`
+
+### `resource{}.provider`
+
+### `resource{}.lifecycle`
+
+## Examples
+
+The following examples describe common patterns for specific use cases.
+
+### Define an AWS instance
+
+The following example defines an `aws_instance` resource named `web`. 
+
+resource "aws_instance" "web" {
+  ami           = "ami-a1b2c3d4"
+  instance_type = "t2.micro"
+}
+
+
+
diff --git a/website/docs/language/resources/index.mdx b/website/docs/language/resources/index.mdx
deleted file mode 100644
index 0c3d230f91d6..000000000000
--- a/website/docs/language/resources/index.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-page_title: Resources Overview - Configuration Language
-description: >-
-  Resources describe infrastructure objects in Terraform configurations. Find
-  documentation for resource syntax, behavior, and meta-arguments.
----
-
-# Resources
-
-> **Hands-on:** Try the [Terraform: Get Started](/terraform/tutorials/aws-get-started?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorials.
-
-_Resources_ are the most important element in the Terraform language.
-Each resource block describes one or more infrastructure objects, such
-as virtual networks, compute instances, or higher-level components such
-as DNS records.
-
-- [Resource Blocks](/terraform/language/resources/syntax) documents
-  the syntax for declaring resources.
-
-- [Resource Behavior](/terraform/language/resources/behavior) explains in
-  more detail how Terraform handles resource declarations when applying a
-  configuration.
-
-- The Meta-Arguments section documents special arguments that can be used with
-  every resource type, including
-  [`depends_on`](/terraform/language/meta-arguments/depends_on),
-  [`count`](/terraform/language/meta-arguments/count),
-  [`for_each`](/terraform/language/meta-arguments/for_each),
-  [`provider`](/terraform/language/meta-arguments/resource-provider),
-  and [`lifecycle`](/terraform/language/meta-arguments/lifecycle).
-
-- [Provisioners](/terraform/language/resources/provisioners/syntax)
-  documents configuring post-creation actions for a resource using the
-  `provisioner` and `connection` blocks. Since provisioners are non-declarative
-  and potentially unpredictable, we strongly recommend that you treat them as a
-  last resort.
diff --git a/website/docs/language/resources/provisioners/file.mdx b/website/docs/language/resources/provisioners/file.mdx
deleted file mode 100644
index 9655e8a3de6a..000000000000
--- a/website/docs/language/resources/provisioners/file.mdx
+++ /dev/null
@@ -1,129 +0,0 @@
----
-page_title: 'Provisioner: file'
-description: >-
-  The `file` provisioner is used to copy files or directories from the machine
-  executing Terraform to the newly created resource. The `file` provisioner
-  supports both `ssh` and `winrm` type connections.
----
-
-# File Provisioner
-
-The `file` provisioner copies files or directories from the machine
-running Terraform to the newly created resource. The `file` provisioner
-supports both `ssh` and `winrm` type [connections](/terraform/language/resources/provisioners/connection).
-
-~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
-[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
-
-## Example usage
-
-```hcl
-resource "aws_instance" "web" {
-  # ...
-
-  # Copies the myapp.conf file to /etc/myapp.conf
-  provisioner "file" {
-    source      = "conf/myapp.conf"
-    destination = "/etc/myapp.conf"
-  }
-
-  # Copies the string in content into /tmp/file.log
-  provisioner "file" {
-    content     = "ami used: ${self.ami}"
-    destination = "/tmp/file.log"
-  }
-
-  # Copies the configs.d folder to /etc/configs.d
-  provisioner "file" {
-    source      = "conf/configs.d"
-    destination = "/etc"
-  }
-
-  # Copies all files and folders in apps/app1 to D:/IIS/webapp1
-  provisioner "file" {
-    source      = "apps/app1/"
-    destination = "D:/IIS/webapp1"
-  }
-}
-```
-
--> **Note:** When the `file` provisioner communicates with a Windows system over SSH, you must configure OpenSSH to run the commands with `cmd.exe` and not PowerShell. PowerShell causes file parsing errors because it is incompatible with both Unix shells and the Windows command interpreter.
-
-## Argument Reference
-
-The following arguments are supported:
-
-* `source` - The source file or directory. Specify it either relative to the
-  current working directory or as an absolute path.
-  This argument cannot be combined with `content`.
-
-* `content` - The direct content to copy on the destination.
-  If destination is a file, the content will be written on that file. In case
-  of a directory, a file named `tf-file-content` is created inside that
-  directory. We recommend using a file as the destination when using `content`.
-  This argument cannot be combined with `source`.
-
-* `destination` - (Required) The destination path to write to on the remote
-  system. See [Destination Paths](#destination-paths) below for more
-  information.
-
-## Destination Paths
-
-The path you provide in the `destination` argument will be evaluated by the
-remote system, rather than by Terraform itself. Therefore the valid values
-for that argument can vary depending on the operating system and remote access
-software running on the target.
-
-When connecting over SSH, the `file` provisioner passes the given destination
-path verbatim to the `scp` program on the remote host. By default, OpenSSH's
-`scp` implementation runs in the remote user's home directory and so you can
-specify a relative path to upload into that home directory, or an absolute
-path to upload to some other location. The remote `scp` process will run with
-the access level of the user specified in the `connection` block, and so
-permissions may prevent writing directly to locations outside of the home
-directory.
-
-Because WinRM has no corresponding file transfer protocol, for WinRM
-connections the `file` provisioner uses a more complex process:
-
-1. Generate a temporary filename in the directory given in the remote system's
-   `TEMP` environment variable, using a pseudorandom UUID for uniqueness.
-2. Use sequential generated `echo` commands over WinRM to gradually append
-   base64-encoded chunks of the source file to the chosen temporary file.
-3. Use an uploaded PowerShell script to read the temporary file, base64-decode,
-   and write the raw result into the destination file.
-
-In the WinRM case, the destination path is therefore interpreted by PowerShell
-and so you must take care not to use any meta-characters that PowerShell might
-interpret. In particular, avoid including any untrusted external input in
-your `destination` argument when using WinRM, because it can serve as a vector
-for arbitrary PowerShell code execution on the remote system.
-
-Modern Windows systems support running an OpenSSH server, so we strongly
-recommend choosing SSH over WinRM whereever possible, and using WinRM only as
-a last resort when working with obsolete Windows versions.
-
-## Directory Uploads
-
-The `file` provisioner can upload a complete directory to the remote machine.
-When uploading a directory, there are some additional considerations.
-
-When using the `ssh` connection type the destination directory must already
-exist. If you need to create it, use a remote-exec provisioner just prior to
-the file provisioner in order to create the directory
-
-When using the `winrm` connection type the destination directory will be
-created for you if it doesn't already exist.
-
-The existence of a trailing slash on the source path will determine whether the
-directory name will be embedded within the destination, or whether the
-destination will be created. For example:
-
-* If the source is `/foo` (no trailing slash), and the destination is `/tmp`,
-  then the contents of `/foo` on the local machine will be uploaded to
-  `/tmp/foo` on the remote machine. The `foo` directory on the remote machine
-  will be created by Terraform.
-
-* If the source, however, is `/foo/` (a trailing slash is present), and the
-  destination is `/tmp`, then the contents of `/foo` will be uploaded directly
-  into `/tmp`.
diff --git a/website/docs/language/resources/provisioners/local-exec.mdx b/website/docs/language/resources/provisioners/local-exec.mdx
deleted file mode 100644
index c3bd88290836..000000000000
--- a/website/docs/language/resources/provisioners/local-exec.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
----
-page_title: 'Provisioner: local-exec'
-description: >-
-  The `local-exec` provisioner invokes a local executable after a resource is
-  created. This invokes a process on the machine running Terraform, not on the
-  resource. See the `remote-exec` provisioner to run commands on the resource.
----
-
-# local-exec Provisioner
-
-The `local-exec` provisioner invokes a local executable after a resource is
-created. This invokes a process on the machine running Terraform, not on the
-resource. See the `remote-exec`
-[provisioner](/terraform/language/resources/provisioners/remote-exec) to run commands on the
-resource.
-
-Note that even though the resource will be fully created when the provisioner is
-run, there is no guarantee that it will be in an operable state - for example
-system services such as `sshd` may not be started yet on compute resources.
-
-~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
-[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
-
-## Example usage
-
-```hcl
-resource "aws_instance" "web" {
-  # ...
-
-  provisioner "local-exec" {
-    command = "echo ${self.private_ip} >> private_ips.txt"
-  }
-}
-```
-
-## Argument Reference
-
-The following arguments are supported:
-
-* `command` - (Required) This is the command to execute. It can be provided
-  as a relative path to the current working directory or as an absolute path.
-  The `command` is evaluated in a shell and can use environment variables for
-  variable substitution. We do not recommend using Terraform variables for variable
-  substitution because doing so can lead to shell injection vulnerabilities. Instead, you should pass Terraform variables to a command
-  through the `environment` parameter and use environment variable substitution
-  instead. Refer to the following OWASP article for additional information about injection flaws: [Code Injection](https://owasp.org/www-community/attacks/Code_Injection).
-
-* `working_dir` - (Optional) If provided, specifies the working directory where
-  `command` will be executed. It can be provided as a relative path to the
-  current working directory or as an absolute path. The directory must exist.
-
-* `interpreter` - (Optional) If provided, this is a list of interpreter
-  arguments used to execute the command. The first argument is the
-  interpreter itself. It can be provided as a relative path to the current
-  working directory or as an absolute path.  The remaining arguments are
-  appended prior to the command.  This allows building command lines of the
-  form "/bin/bash", "-c", "echo foo". If `interpreter` is unspecified,
-  sensible defaults will be chosen based on the system OS.
-
-* `environment` - (Optional) block of key value pairs representing the
-  environment of the executed command. inherits the current process environment.
-
-* `when` - (Optional) If provided, specifies when Terraform will execute the command.
-  For example, `when = destroy` specifies that the provisioner will run when the associated resource
-  is destroyed. Refer to [Destroy-Time Provisioners](/terraform/language/resources/provisioners/syntax#destroy-time-provisioners)
-  for details.
-  
-*  `quiet` - (Optional) If set to `true`, Terraform will not print the command to be executed to stdout, and will instead print "Suppressed by quiet=true". Note that the output of the command will still be printed in any case.
-
-### Interpreter Examples
-
-```hcl
-resource "terraform_data" "example1" {
-  provisioner "local-exec" {
-    command = "open WFH, '>completed.txt' and print WFH scalar localtime"
-    interpreter = ["perl", "-e"]
-  }
-}
-```
-
-```hcl
-resource "terraform_data" "example2" {
-  provisioner "local-exec" {
-    command = "Get-Date > completed.txt"
-    interpreter = ["PowerShell", "-Command"]
-  }
-}
-```
-
-```hcl
-resource "aws_instance" "web" {
-  # ...
-
-  provisioner "local-exec" {
-    command = "echo $FOO $BAR $BAZ >> env_vars.txt"
-
-    environment = {
-      FOO = "bar"
-      BAR = 1
-      BAZ = "true"
-    }
-  }
-}
-```
diff --git a/website/docs/language/resources/provisioners/remote-exec.mdx b/website/docs/language/resources/provisioners/remote-exec.mdx
deleted file mode 100644
index ef548d5ddd3e..000000000000
--- a/website/docs/language/resources/provisioners/remote-exec.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-page_title: 'Provisioner: remote-exec'
-description: >-
-  The `remote-exec` provisioner invokes a script on a remote resource after it
-  is created. This can be used to run a configuration management tool, bootstrap
-  into a cluster, etc. To invoke a local process, see the `local-exec`
-  provisioner instead. The `remote-exec` provisioner supports both `ssh` and
-  `winrm` type connections.
----
-
-# remote-exec Provisioner
-
-The `remote-exec` provisioner invokes a script on a remote resource after it
-is created. This can be used to run a configuration management tool, bootstrap
-into a cluster, etc. To invoke a local process, see the `local-exec`
-[provisioner](/terraform/language/resources/provisioners/local-exec) instead. The `remote-exec`
-provisioner requires a [connection](/terraform/language/resources/provisioners/connection)
-and supports both `ssh` and `winrm`.
-
-~> **Important:** Use provisioners as a last resort. There are better alternatives for most situations. Refer to
-[Declaring Provisioners](/terraform/language/resources/provisioners/syntax) for more details.
-
-## Example usage
-
-```hcl
-resource "aws_instance" "web" {
-  # ...
-
-  # Establishes connection to be used by all
-  # generic remote provisioners (i.e. file/remote-exec)
-  connection {
-    type     = "ssh"
-    user     = "root"
-    password = var.root_password
-    host     = self.public_ip
-  }
-
-  provisioner "remote-exec" {
-    inline = [
-      "puppet apply",
-      "consul join ${aws_instance.web.private_ip}",
-    ]
-  }
-}
-```
-
-## Argument Reference
-
-The following arguments are supported:
-
-* `inline` - This is a list of command strings. The provisioner uses a default
-  shell unless you specify a shell as the first command (eg., `#!/bin/bash`). 
-  You cannot provide this with `script` or `scripts`.
-
-* `script` - This is a path (relative or absolute) to a local script that will
-  be copied to the remote resource and then executed. This cannot be provided
-  with `inline` or `scripts`.
-
-* `scripts` - This is a list of paths (relative or absolute) to local scripts
-  that will be copied to the remote resource and then executed. They are executed
-  in the order they are provided. This cannot be provided with `inline` or `script`.
-
--> **Note:** Since `inline` is implemented by concatenating commands into a script, [`on_failure`](/terraform/language/resources/provisioners/syntax#failure-behavior) applies only to the final command in the list. In particular, with `on_failure = fail` (the default behaviour) earlier commands will be allowed to fail, and later commands will also execute. If this behaviour is not desired, consider using `"set -o errexit"` as the first command.
-
-## Script Arguments
-
-You cannot pass any arguments to scripts using the `script` or
-`scripts` arguments to this provisioner. If you want to specify arguments,
-upload the script with the
-[file provisioner](/terraform/language/resources/provisioners/file)
-and then use `inline` to call it. Example:
-
-```hcl
-resource "aws_instance" "web" {
-  # ...
-
-  provisioner "file" {
-    source      = "script.sh"
-    destination = "/tmp/script.sh"
-  }
-
-  provisioner "remote-exec" {
-    inline = [
-      "chmod +x /tmp/script.sh",
-      "/tmp/script.sh args",
-    ]
-  }
-}
-```
diff --git a/website/docs/language/resources/syntax.mdx b/website/docs/language/resources/syntax.mdx
deleted file mode 100644
index 9cdf9b14105a..000000000000
--- a/website/docs/language/resources/syntax.mdx
+++ /dev/null
@@ -1,214 +0,0 @@
----
-page_title: Resources - Configuration Language
-description: >-
-  Resources correspond to infrastructure objects like virtual networks or
-  compute instances. Learn about resource types, syntax, behavior, and
-  arguments.
----
-
-# Resource Blocks
-
-> **Hands-on:** Try the [Terraform: Get Started](/terraform/tutorials/aws-get-started?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) tutorials.
-
-_Resources_ are the most important element in the Terraform language.
-Each resource block describes one or more infrastructure objects, such
-as virtual networks, compute instances, or higher-level components such
-as DNS records.
-
-For information about how Terraform manages resources after applying a configuration, refer to
-[Resource Behavior](/terraform/language/resources/behavior).
-
-## Resource Syntax
-
-A `resource` block declares a resource of a specific type 
-with a specific local name. Terraform uses the name when referring to the resource 
-in the same module, but it has no meaning outside that module's scope.
-
-In the following example,  the `aws_instance` resource type is named `web`. The resource type and name must be unique within a module because they serve as an identifier for a given resource.
-
-```hcl
-resource "aws_instance" "web" {
-  ami           = "ami-a1b2c3d4"
-  instance_type = "t2.micro"
-}
-```
-
-Within the block body (between `{` and `}`) are the configuration arguments
-for the resource itself. The arguments often depend on the
-resource type. In this example, both `ami` and `instance_type` are special 
-arguments for [the `aws_instance` resource type](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance).
-
--> **Note:** Resource names must start with a letter or underscore, and may
-contain only letters, digits, underscores, and dashes.
-
-Resource declarations can include more advanced features, such as single 
-resource declarations that produce multiple similar remote objects, but only
-a small subset is required for initial use. 
-
-## Resource Types
-
-Each resource is associated with a single _resource type_, which determines
-the kind of infrastructure object it manages and what arguments and other
-attributes the resource supports.
-
-### Providers
-
-A [provider](/terraform/language/providers/requirements) is a plugin for Terraform 
-that offers a collection of resource types. Each resource type is implemented by a provider. A
-provider provides resources to manage a single cloud or on-premises
-infrastructure platform. Providers are distributed separately from Terraform, 
-but Terraform can automatically install most providers when initializing
-a working directory.
-
-To manage resources, a Terraform module must specify the required providers. Refer to 
-[Provider Requirements](/terraform/language/providers/requirements) for additional information.
-
-Most providers need some configuration to access their remote API, 
-which is provided by the root module. Refer to 
-[Provider Configuration](/terraform/language/providers/configuration) for additional information.
-
-Based on a resource type's name, Terraform can usually determine which provider to use. 
-By convention, resource type names start with their provider's preferred local name.
-When using multiple configurations of a provider or non-preferred local provider names, 
-you must use [the `provider` meta-argument](/terraform/language/meta-arguments/resource-provider) 
-to manually choose a provider configuration.
-
-### Resource Arguments
-
-Most of the arguments within the body of a `resource` block are specific to the
-selected resource type. The resource type's documentation lists which arguments
-are available and how their values should be formatted.
-
-The values for resource arguments can make full use of
-[expressions](/terraform/language/expressions) and other dynamic Terraform
-language features.
-
-[Meta-arguments](#meta-arguments) are defined by Terraform
-and apply across all resource types. 
-
-### Documentation for Resource Types
-
-Every Terraform provider has its own documentation, describing its resource
-types and their arguments.
-
-Some provider documentation is still part of Terraform's core documentation, 
-but the [Terraform Registry](https://registry.terraform.io/browse/providers) 
-is the main home for all publicly available provider docs.
-
-When viewing a provider's page on the Terraform
-Registry, you can click the **Documentation** link in the header to browse its
-documentation. The documentation is versioned. To choose a different version of the provider documentation, click on the version in the provider breadcrumbs to choose a version from the drop-down menu.
-
-## Meta-Arguments
-
-The Terraform language defines the following meta-arguments, which can be used with
-any resource type to change the behavior of resources:
-
-- [`depends_on`, for specifying hidden dependencies](/terraform/language/meta-arguments/depends_on)
-- [`count`, for creating multiple resource instances according to a count](/terraform/language/meta-arguments/count)
-- [`for_each`, to create multiple instances according to a map, or set of strings](/terraform/language/meta-arguments/for_each)
-- [`provider`, for selecting a non-default provider configuration](/terraform/language/meta-arguments/resource-provider)
-- [`lifecycle`, for lifecycle customizations](/terraform/language/meta-arguments/lifecycle)
-- [`provisioner`, for taking extra actions after resource creation](/terraform/language/resources/provisioners/syntax)
-
-## Removing Resources
-
--> **Note:** The `removed` block is available in Terraform v1.7 and later. For earlier Terraform versions, you can use the [`terraform state rm` CLI command](/terraform/cli/commands/state/rm) as a separate step.
-
-To remove a resource from Terraform, simply delete the `resource` block from your Terraform configuration.
-
-By default, after you remove the `resource` block, Terraform will plan to destroy any real infrastructure object managed by that resource.
-
-Sometimes you may wish to remove a resource from your Terraform configuration without destroying the real infrastructure object it manages. In this case, the resource will be removed from the [Terraform state](/terraform/language/state), but the real infrastructure object will not be destroyed.
-
-To declare that a resource was removed from Terraform configuration but that its managed object should not be destroyed, remove the `resource` block from your configuration and replace it with a `removed` block:
-
-```hcl
-removed {
-  from = aws_instance.example
-
-  lifecycle {
-    destroy = false
-  }
-}
-```
-
-The `from` argument is the address of the resource you want to remove, without any instance keys (such as "aws_instance.example[1]").
-
-The `lifecycle` block is required. The `destroy` argument determines whether Terraform will attempt to destroy the object managed by the resource or not. A value of `false` means that Terraform will remove the resource from state without destroying it.
-
-A `removed` block may also contain a [Destroy-Time Provisioner](/terraform/language/resources/provisioners/syntax#destroy-time-provisioners), so that the provisioner can remain in the configuration even though the `resource` block has been removed.
-
-```hcl
-removed {
-  from = aws_instance.example
-
-  lifecycle {
-    destroy = true
-  }
-
-  provisioner "local-exec" {
-    when    = destroy
-    command = "echo 'Instance ${self.id} has been destroyed.'"
-  }
-}
-```
-
-The same referencing rules apply as in normal destroy-time provisioners, with only `count.index`, `each.key`, and `self` allowed. The provisioner must specify `when = destroy`, and the `removed` block must use `destroy = true` in order for the provisioner to execute.
-
-## Custom Condition Checks
-
-You can use `precondition` and `postcondition` blocks to specify assumptions and guarantees about how the resource operates. The following example creates a precondition that checks whether the AMI is properly configured.
-
-```hcl
-resource "aws_instance" "example" {
-  instance_type = "t2.micro"
-  ami           = "ami-abc123"
-
-  lifecycle {
-    # The AMI ID must refer to an AMI that contains an operating system
-    # for the `x86_64` architecture.
-    precondition {
-      condition     = data.aws_ami.example.architecture == "x86_64"
-      error_message = "The selected AMI must be for the x86_64 architecture."
-    }
-  }
-}
-```
-
-[Custom condition checks](/terraform/language/expressions/custom-conditions#preconditions-and-postconditions) 
-can help capture assumptions so that future maintainers 
-understand the configuration design and intent. They also return useful 
-information about errors earlier and in context, helping consumers to diagnose 
-issues in their configuration.
-
-## Operation Timeouts
-
-Some resource types provide a special `timeouts` nested block argument that
-allows you to customize how long certain operations are allowed to take
-before being considered to have failed.
-For example, [`aws_db_instance`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_instance)
-allows configurable timeouts for `create`, `update`, and `delete` operations.
-
-Timeouts are handled entirely by the resource type implementation in the
-provider, but resource types offering these features follow the convention
-of defining a child block called `timeouts` that has a nested argument
-named after each operation that has a configurable timeout value.
-Each of these arguments takes a string representation of a duration, such
-as `"60m"` for 60 minutes, `"10s"` for ten seconds, or `"2h"` for two hours.
-
-```hcl
-resource "aws_db_instance" "example" {
-  # ...
-
-  timeouts {
-    create = "60m"
-    delete = "2h"
-  }
-}
-```
-
-The set of configurable operations is chosen by each resource type. Most
-resource types do not support the `timeouts` block at all. Consult the
-documentation for each resource type to see which operations it offers
-for configuration, if any.

From 0d0e97a09cb929ee50d269c0ed6ee742b8d911af Mon Sep 17 00:00:00 2001
From: trujillo-adam <ajosetru@gmail.com>
Date: Fri, 15 Nov 2024 08:47:14 -0800
Subject: [PATCH 2/2] renamed usage section for resources

---
 website/data/language-nav-data.json                | 14 +++++++-------
 .../{define-resource => create-resource}/index.mdx |  0
 .../provisioners/connect.mdx                       |  0
 .../provisioners/define.mdx                        |  0
 .../provisioners/index.mdx                         |  0
 .../provisioners/null_resource.mdx                 |  0
 .../terraform-data.mdx                             |  0
 7 files changed, 7 insertions(+), 7 deletions(-)
 rename website/docs/language/{define-resource => create-resource}/index.mdx (100%)
 rename website/docs/language/{define-resource => create-resource}/provisioners/connect.mdx (100%)
 rename website/docs/language/{define-resource => create-resource}/provisioners/define.mdx (100%)
 rename website/docs/language/{define-resource => create-resource}/provisioners/index.mdx (100%)
 rename website/docs/language/{define-resource => create-resource}/provisioners/null_resource.mdx (100%)
 rename website/docs/language/{define-resource => create-resource}/terraform-data.mdx (100%)

diff --git a/website/data/language-nav-data.json b/website/data/language-nav-data.json
index b17bf1e06224..abe4b5387954 100644
--- a/website/data/language-nav-data.json
+++ b/website/data/language-nav-data.json
@@ -70,33 +70,33 @@
     ]
   },
   {
-    "title": "Define resources",
+    "title": "Create resources",
     "routes": [
-      { "title": "Overview", "path": "define-resource" },
+      { "title": "Overview", "path": "create-resource" },
       {
         "title": "Apply provisioners",
         "routes": [
           {
             "title": "Overview",
-            "path": "define-resource/provisioners"
+            "path": "create-resource/provisioners"
           },
           {
             "title": "Declaring Provisioners",
-            "path": "define-resource/provisioners/define"
+            "path": "create-resource/provisioners/define"
           },
           {
             "title": "Provisioner Connections",
-            "path": "define-resource/provisioners/connect"
+            "path": "create-resource/provisioners/connect"
           },
           {
             "title": "Run commands on standard lifecycle resources",
-            "path": "define-resource/provisioners/null_resource"
+            "path": "create-resource/provisioners/null_resource"
           }
         ]
       },
       {
         "title": "Apply standard lifecycle",
-        "path": "define-resource/terraform-data"
+        "path": "create-resource/terraform-data"
       }
     ]
   },
diff --git a/website/docs/language/define-resource/index.mdx b/website/docs/language/create-resource/index.mdx
similarity index 100%
rename from website/docs/language/define-resource/index.mdx
rename to website/docs/language/create-resource/index.mdx
diff --git a/website/docs/language/define-resource/provisioners/connect.mdx b/website/docs/language/create-resource/provisioners/connect.mdx
similarity index 100%
rename from website/docs/language/define-resource/provisioners/connect.mdx
rename to website/docs/language/create-resource/provisioners/connect.mdx
diff --git a/website/docs/language/define-resource/provisioners/define.mdx b/website/docs/language/create-resource/provisioners/define.mdx
similarity index 100%
rename from website/docs/language/define-resource/provisioners/define.mdx
rename to website/docs/language/create-resource/provisioners/define.mdx
diff --git a/website/docs/language/define-resource/provisioners/index.mdx b/website/docs/language/create-resource/provisioners/index.mdx
similarity index 100%
rename from website/docs/language/define-resource/provisioners/index.mdx
rename to website/docs/language/create-resource/provisioners/index.mdx
diff --git a/website/docs/language/define-resource/provisioners/null_resource.mdx b/website/docs/language/create-resource/provisioners/null_resource.mdx
similarity index 100%
rename from website/docs/language/define-resource/provisioners/null_resource.mdx
rename to website/docs/language/create-resource/provisioners/null_resource.mdx
diff --git a/website/docs/language/define-resource/terraform-data.mdx b/website/docs/language/create-resource/terraform-data.mdx
similarity index 100%
rename from website/docs/language/define-resource/terraform-data.mdx
rename to website/docs/language/create-resource/terraform-data.mdx