Fix incorrect resource reference

Author: hsnabszhdn

content/terraform/v1.10.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.11.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.12.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.2.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.3.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.4.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.6.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.7.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.8.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>
 

content/terraform/v1.9.x/docs/language/style.mdx

@@ -162,7 +162,7 @@ The order of the resources and data sources in your code does not affect how Ter
 
 How you order your resources largely depends on the size and complexity of your code, but we recommend defining data sources alongside the resources that reference them. For readability, your Terraform code should “build on itself” — you should define a data source before the resource that references it.
 
-The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zone`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
+The following example defines an `aws_instance` that relies on two data sources, `aws_ami` and `aws_availability_zones`. For readability and continuity, it defines the data sources before the `aws_instance` resource.
 
 <CodeBlockConfig hideClipboard>