Apply suggestions from code review

Co-authored-by: Daniel Banck <dbanck@users.noreply.github.com>
Co-authored-by: Samsondeen <40821565+dsa0x@users.noreply.github.com>

Author: 3 people

content/terraform/v1.14.x (alpha)/data/language-nav-data.json

@@ -338,7 +338,7 @@
     ]
   },
   {
-    "title": "tfquery blocks",
+    "title": "Query blocks",
     "routes": [
       {
         "title": "list",

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

@@ -84,5 +84,5 @@ $ terraform query -generate-config=to-import/file.tf
 The following command prints `import` and `resource` blocks for the query results as json:
 
 ```shell-session
-$ terraform query -generate-config=to-import -json
+$ terraform query -generate-config=file.tf -json
 ```

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

@@ -55,19 +55,21 @@ You must set the following arguments for every `list` block:
 
 ### `provider`
 
-The `provider` argument instructs Terraform to use an alternate provider configuration.
+The `provider` argument specifies which provider configuration Terraform uses to query infrastructure.
 
 ```hcl
 list "<TYPE>" "<LABEL>" {
-  provider = <provider>.<alias>
+  provider = <provider>
 }
 ```
 
-Terraform uses the default `provider` configuration to query resources, but you can create multiple provider configurations and use a non-default configuration for specific queries. Refer to the [`provider` block reference](/terraform/language/block/provider) for information about defining alternate provider configurations. 
+Terraform does not implicitly use the default `provider` configuration when querying resources. As a result, the `provider` argument is required. 
+
+You can create multiple provider configurations and use a non-default configuration for specific queries. Refer to the [`provider` block reference](/terraform/language/block/provider) for information about defining alternate provider configurations. 
 
 Use the `<PROVIDER>.<ALIAS>` syntax to reference a provider configuration in the `provider` argument. Refer to [Select an alternate provider configuration](#select-an-alternate-provider-configuration) for an example of how to reference a specific provider configuration.
 
-The `provider` 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.
+The `provider` argument is a meta-argument, which is built into Terraform and controls the way that Terraform queries resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
 
 #### Summary
 
@@ -289,7 +291,7 @@ list "azurerm_resource_group" "rg" {
 The following example creates four lists using a set created with the `toset()` function:
 
 ```hcl
-resource "aws_iam_user" "the-accounts" {
+list "aws_iam_user" "the-accounts" {
    provider = aws
    for_each = toset(["Todd", "James", "Alice", "Dottie"])
 }

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

@@ -21,9 +21,6 @@ Complete the following steps to find and import resources in bulk:
 - After importing resources, you can remove the generated `import` block or keep it as an historical record.
 
 
-## Requirements
-
-Terraform v1.12 or newer is required to uniquely ID resources according the resource identity. For v1.11 and older, Terraform uses the cloud provider ID attribute. 
 
 ## Define a query
 
@@ -63,6 +60,7 @@ The following example queries AWS for `aws_instance` resources that match {. . .
 
 ```hcl
 list "aws_instance" "prod" {
+  provider = aws
   include_resource = true
   limit = 50
   config {

content/terraform/v1.14.x (alpha)/docs/partials/beta.mdx

@@ -1,4 +1,4 @@
-<!-- Use this parital for general beta callouts -->
+<!-- Use this partial for general beta callouts -->
 <Note>
 
 This feature is currently in beta. Do not use beta functionality in production environments.