feedback from draft reviews

Author: trujillo-adam

content/terraform/v1.14.x (alpha)/docs/cli/commands/query.mdx

@@ -71,12 +71,12 @@ The following command loads variable values defined in `my-vars.tfvars`:
 $ terraform query -var-file=my-vars.tfvars
 ```
 
-### Generate inport configuration
+### Generate import configuration
 
 The following command generates `import` and `resource` blocks for the query results to a file in the `/to-import` directory:
 
 ```shell-session
-$ terraform query -generate-config=to-import
+$ terraform query -generate-config=to-import/file.tf
 ```
 
 The following command prints `import` and `resource` blocks for the query results as json:

content/terraform/v1.14.x (alpha)/docs/language/block/tfquery/list.mdx

@@ -16,7 +16,6 @@ A `list` block supports the following configuration:
   - [`provider`](#provider) &nbsp reference | required
   - [`count`](#count) number &nbsp | mutually exclusive with `for_each`
   - [`for_each`](#for_each) &nbsp map or set of strings | mutually exclusive with `count`
-  - [`depends_on`](#depends_on) &nbsp list of references
   - [`include_resource`](#include_resource)  boolean
   - [`limit`](#limit) number | `100`
   - [`config`](#config)  block
@@ -33,7 +32,6 @@ list "<TYPE>" "<LABEL>" {
   for_each [ # `for_each` and `count` are mutually exclusive
     <KEY> = <VALUE>
   ]
-  depends_on = [ <RESOURCE.ADDRESS.EXPRESSION> ]
   include_resource = <false>
   limit = 100
   config {
@@ -90,7 +88,7 @@ The value must be a whole number. You can reference variables or local values an
 
 In blocks where `count` is set, Terraform exposes an additional `count` object. You can reference the object to modify the configuration of each list of query results. The `count` object has an `index` attribute starting from `0`.
 
-To refer to an individual list of query results, use the `<TYPE>.<NAME>[INDEX]` syntax. For example, `aws_instance.server[0]` refers to the first list of query results for the `aws_instance` resource named `server`.
+To refer to an individual list of query results, use the `list.<TYPE>.<NAME>[INDEX]` syntax. For example, `list.aws_instance.server[0]` refers to the first list of query results for the `aws_instance` resource named `server`.
 
 <Tip>
 
@@ -106,31 +104,6 @@ The `count` argument is a meta-argument, which is built into Terraform and contr
 - Default: None.
 - Example: [Create multiple lists of query results](#create-multiple-lists-of-query-results).
 
-### `depends_on`
-
-The `depends_on` meta-argument specifies an upstream resource that the `list` block  depends on. Terraform must complete all operations on the upstream resource before performing operations on the `list` block containing the `depends_on` argument.
-
-```hcl
-list "<TYPE>" "<LABEL>" {
-  depends_on = [ <reference resource> ]
-}
-```
-
-When a query configuration refers to another resource, Terraform identifies the dependency and creates the upstream resource first. In some cases, you may need Terraform to create a resource before creating a list of query results, even though the objects are configured independently.
-
-Use the `depends_on` argument when the objects do not reference each other. We recommend always including a comment to explain resource dependencies when using a `depends_on` argument.
-
-When using the `depends_on` meta-argument, you can only reference resources or child modules in the same root module. The list cannot include arbitrary expressions. Any values referenced in the `depends_on` list must be known before Terraform begins the operation so that it can evaluate dependencies.
-
-Specifying an entire module in the `depends_on` argument affects the order in which Terraform provisions all of the resources and data sources associated with that module. Refer to [Resource dependencies](/terraform/language/resources/configure#specify-resource-dependencies) and [Data resource dependencies](/terraform/language/data-sources#dependencies) for more information.
-
-The `depends_on` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
-
-#### Summary
-
-- Data type: List.
-- Default: None.
-
 ### `for_each`
 
 The `for_each` meta-argument instructs Terraform to create similar lists of query results without requiring separate configuration blocks for each list.
@@ -184,7 +157,7 @@ The `for_each` argument exposes an `each` object that you can reference within t
 - `each.key`: Map key or list member that corresponds to list.
 - `each.value`: Map value that corresponds to a list.
 
-Use the `<TYPE>.<NAME>[<KEY>]` syntax to access an instance of a resource created using `for_each`. For example, `azurerm_resource_group.rg["a_group"]` refers to a list of query results for the `azurrm_resource_group` resource named `rg` created from the `a_group` key.
+Use the `list.<TYPE>.<NAME>[<KEY>]` syntax to access an instance of a resource created using `for_each`. For example, `list.azurerm_resource_group.rg["a_group"]` refers to a list of query results for the `azurrm_resource_group` resource named `rg` created from the `a_group` key.
 
 The `for_each` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
 
@@ -322,4 +295,23 @@ resource "aws_iam_user" "the-accounts" {
 
 </Tab>
 
-</Tabs>
+</Tabs>
+
+### Reference a list block
+
+In the following example, the `include_resource` argument is set to `true` in the `list.concept_pet.animals_with_legs` block. As a result, the query returns complete resource state information to the list of results for `animals_with_legs`. This lets the `list.concept_pet.more_pets` block reference the `length` attribute from `animals_with_legs` as the value for its `count` argument.
+
+```hcl
+list "concept_pet" "animals_with_legs" {
+  provider = concept
+  include_resource = true
+}
+
+list "concept_pet" "more_pets" {
+  provider = concept
+
+  config {
+    count = list.concept_pet.animals_with_legs.data[0].state.length
+  }
+}
+```

content/terraform/v1.14.x (alpha)/docs/language/import/bulk.mdx

@@ -14,9 +14,10 @@ For organizations with large sets of infrastructure resources, manually identify
 Complete the following steps to find and import resources in bulk:
 
 - Search for resources: Create `list` blocks to search for existing resources.
-- Generate configuration: Use the Terraform command to generate `resource` and `import` blocks for importing the resources. The configuration also includes the resource ID.
+- Generate configuration: Use the Terraform command to generate `resource` and `import` blocks for importing the resources. The configuration also includes the [resource identity](#resource-identity). 
+
 - Import resources: Copy the generated configuration into your main.tf file and run a `terraform apply` command to import the resources.
-- After importing resources, you can remove the generated configuration or keep it as an historical record.
+- After importing resources, you can remove the generated `import` block or keep it as an historical record.
 
 ### Resource identity
 
@@ -62,7 +63,7 @@ Add the following arguments to your `list` block:
 
 - `include_resource`: By default, Terraform retrieves only resource identities, but you can set the `include_resource` argument to `true` so that Terraform can also retrieve all available resource attributes. To reference resource attributes retrieved by the list block, you must enable the `include_resource` argument. Setting this argument to `true` may affect performance.  
 
-- `limit`: By default, Terraform retrieves up to 100 resources per query, but you can use the `limit` argument to specify a higher or lower number of results.
+- `limit`: By default, Terraform retrieves up to 100 resources per list block, but you can use the `limit` argument to specify a higher or lower number of results.
 
 The `list` block also supports several Terraform **meta-arguments**, which are arguments built into Terraform configuration language that configure how Terraform creates and manages infrastructure objects. For example, you can use the `count` meta-argument to create multiple instances of the resource list returned by the query. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
 

content/terraform/v1.14.x (alpha)/docs/language/import/index.mdx

@@ -21,4 +21,4 @@ When you need to identify and import large sets of infrastructure resources, you
 
 The workflow for importing single resources or small batches of resources works best when you can easily access unique infrastructure resource IDs and other attributes from your cloud provider. In this workflow, manually write `import` and `resource` blocks and run the `terraform apply` command to import the resources. 
 
-Alternatively, you can write only the `import` block and run the `terraform apply` command with the `generate-config` flag to generate the `resource` blocks. Refer to [Import a single resource](/terraform/language/import/single-resource) for more information.  
+Alternatively, you can write only the `import` block and run the `terraform plan` command with the `generate-config-out` flag to generate the `resource` blocks. Refer to [Import a single resource](/terraform/language/import/single-resource) for more information.  

content/terraform/v1.14.x (alpha)/docs/language/meta-arguments.mdx

@@ -71,6 +71,7 @@ Integer index. You cannot use both a `count` and ` for_each` argument in the sam
 
 - [`count` argument in `data` blocks](/terraform/language/block/data#count)
 - [`count` argument in `ephemeral` blocks](/terraform/language/block/ephemeral#count)
+- [`count` argument in `list` blocks](/terraform/language/block/tfquery/list#count)
 - [`count` argument in `module` blocks](/terraform/language/block/module#count)
 - [`count` argument in `resource` block ](/terraform/language/block/resource#count)
 
@@ -109,6 +110,7 @@ You cannot use both a `count` and ` for_each` argument in the same block.
 
 - [`for_each` argument in `data` blocks](/terraform/language/block/data#for_each)
 - [`for_each` argument in `ephemeral` blocks](/terraform/language/block/ephemeral#for_each)
+- [`for_each` argument in `list` blocks](/terraform/language/block/tfquery/list#for_each)
 - [`for_each` argument in `module` blocks](/terraform/language/block/module#for_each)
 - [`for_each` argument in. `resource` blocks](/terraform/language/block/resource#for_each)
 
@@ -139,6 +141,7 @@ The `provider` argument is distinct from the `provider` block, which contains pr
 - [`provider` argument in `data` blocks](/terraform/language/block/data#provider)
 - [`provider` argument in `ephemeral` blocks](/terraform/language/block/ephemeral#provider)
 - [`provider` argument in `import` block ](/terraform/language/block/import#provider)
+- [`provider` argument in `list` blocks](/terraform/language/block/tfquery/list#provider)
 - [`provider` argument in `resource` blocks](/terraform/language/block/resource#provider)
 
 ## `providers`