Apply suggestions from code review

Co-authored-by: Brian McClain <brianmmcclain@gmail.com>

Author: trujillo-adam

content/terraform/v1.13.x/docs/language/meta-arguments/count.mdx

@@ -19,14 +19,14 @@ You can use the `count` argument as a conditional for creating resources. For ex
 
 </Tip>
 
-### `count` objects
+### `count` object
 
 In blocks where `count` is set, an additional `count` object is available in expressions, so you can modify the configuration of each instance. This object has the following attribute:
 
 - `count.index`: The distinct index number starting with `0` corresponding
   to this instance.
 
-In the folllowing example,  Terraform creates four `aws_instance.server` resources that use the same AMI and instance type:
+In the folllowing example, Terraform creates four `aws_instance.server` resources that use the same AMI and instance type. The `count.index` attribute gives each `aws_instance` a unique `Name` tag:
 
 ```hcl
 resource "aws_instance" "server" {
@@ -43,12 +43,11 @@ resource "aws_instance" "server" {
 
 ### Expressions in `count`
 
-The `count` meta-argument accepts numeric [expressions](/terraform/language/expressions), but unlike most arguments, the `count` value must be known before Terraform performs any remote resource operations. `count` can't refer to any resource attributes that are only known after a
-configuration is applied, such as a unique ID generated by the remote API when an object is created.
+The `count` meta-argument accepts numeric [expressions](/terraform/language/expressions), but unlike most arguments, the `count` value must be known before Terraform performs any remote resource operations. `count` cannot refer to any resource attributes that are only known after a configuration is applied, such as a unique ID generated by the remote API when an object is created.
 
 ### Referring to instances
 
-When `count` is set, Terraform distinguishes between the block, itself, and the multiple resource or module instances associated with it. Terraform identifies instances index number starting at `0`.
+Terraform makes a distinction between the block containing the `count` argument and the instances associated with it. Terraform identifies instances index number starting at `0`.
 
 - `<TYPE>.<NAME>` or `module.<NAME>`, for example, `aws_instance.server` refers to the resource block.
 - `<TYPE>.<NAME>[<INDEX>]` or `module.<NAME>[<INDEX>]`, for example, `aws_instance.server[0]` and
@@ -78,7 +77,6 @@ You can use `count` in the following Terraform configuration blocks:
 - [`module` blocks](/terraform/language/block/module)
 - [`resource` blocks](/terraform/language/block/resource)
 
-
 ## Example use cases
 
 The following use cases describe common patterns for the `count` argument.
@@ -89,7 +87,7 @@ In the following example, Terraform creates three EC2 instances, each with a uni
 
 ```hcl
 locals {
-  instance_names = ["example-instance-1", "example-instance-2", "example-instance-3"]
+  instance_names = ["web", "api", "batch"]
 }
 
 module "ec2_instance" {

content/terraform/v1.13.x/docs/language/meta-arguments/depends_on.mdx

@@ -25,8 +25,8 @@ resource "aws_iam_role" "example" {
 }
 
 resource "aws_iam_instance_profile" "example" {
-  # Because this expression refers to the role, Terraform can infer
-  # automatically that the role must be created first.
+  # Because this expression refers to the role, Terraform automatically
+  # infers that the role must be created first.
   role = aws_iam_role.example.name
 }
 
@@ -52,9 +52,9 @@ resource "aws_instance" "example" {
   iam_instance_profile = aws_iam_instance_profile.example
 
   # However, if software running in this EC2 instance needs access
-  # to the S3 API in order to boot properly, there is also a "hidden"
+  # to the S3 API in order to boot properly, there is also a 
   # dependency on the aws_iam_role_policy that Terraform cannot
-  # automatically infer, so it must be declared explicitly:
+  # automatically infer, so you must declare it explicitly:
   depends_on = [
     aws_iam_role_policy.example
   ]
@@ -153,42 +153,49 @@ check "database_connection" {
 }
 ```
 
-### Specify a dependency when querying a data source
+### Create a database service that other services depend on 
 
-In the following example, Terraform gets an AMI for use in the `aws_instance` resource after creating the `aws_subnet.example_subnet` resource:
+In the following example, Terraform must launch the `aws_db_instance`  service first so that `aws_instance` can connect to it:
 
 ```hcl
-resource "aws_vpc" "example_vpc" {
-  cidr_block = "10.0.0.0/16"
+provider "aws" {
+  region = "us-east-2"
 }
 
-resource "aws_subnet" "example_subnet" {
-  vpc_id     = aws_vpc.example_vpc.id
-  cidr_block = "10.0.1.0/24"
-}
-
-data "aws_ami" "example_ami" {
+data "aws_ami" "ubuntu" {
   most_recent = true
-  owners      = ["amazon"]
+
   filter {
     name   = "name"
-    values = ["amzn2-ami-hvm-*"]
+    values = ["ubuntu/images/hvm-ssd-gp3/ubuntu-noble-24.04-amd64-server-*"]
   }
+
   filter {
-    name   = "architecture"
-    values = ["x86_64"]
+    name   = "virtualization-type"
+    values = ["hvm"]
   }
-  depends_on = [aws_subnet.example_subnet]
+
+  owners = ["099720109477"] # Canonical
 }
 
-resource "aws_instance" "example_instance" {
-  ami           = data.aws_ami.example_ami.id
-  instance_type = "t2.micro"
-  subnet_id     = aws_subnet.example_subnet.id
+resource "aws_db_instance" "api" {
+  allocated_storage   = 10
+  db_name             = "api_db"
+  engine              = "postgres"
+  engine_version      = "17.4"
+  instance_class      = "db.t3.micro"
+  username            = "foo"
+  password            = "foobarbaz"
+  skip_final_snapshot = true
+}
+
+resource "aws_instance" "api" {
+  ami           = data.aws_ami.ubuntu.id
+  instance_type = "t3.micro"
+
+  depends_on = [aws_db_instance.api]
 }
-```
 
-Note that this is a simplified example and does not represent a real-world use case. The `depends_on` argument changes the dependency graph so that Terraform creates the resources in a linear order. Without the argument, Terraform would still successfully create the resources.
 
 ### Specify a dependency on the parent module
 

content/terraform/v1.13.x/docs/language/meta-arguments/for_each.mdx

@@ -15,7 +15,7 @@ The `for_each` meta-argument accepts a map or a set of strings and creates an in
 
 You can use pure functions, such as `toset()` and `tomap()`, to create a map or set for use in the `for_each` argument. Whether iterating over the keys of a map or set of strings, all must be known values. Otherwise, Terraform prints an error message that `for_each` has dependencies that it cannot determine before applying the configuration.
 
-The following example creates two instances that reference a map created using the `tomap()` function:
+The following example creates two `azurerm_resource_group` resources that reference a map created using the `tomap()` function:
 
 ```hcl
 resource "azurerm_resource_group" "rg" {
@@ -28,7 +28,7 @@ resource "azurerm_resource_group" "rg" {
 }
 ```
 
-The following example creates four instances using a set created with the `toset()` function:
+The following example creates four `aws_iam_user` resources using a set created with the `toset()` function:
 
 ```hcl
 resource "aws_iam_user" "the-accounts" {
@@ -37,7 +37,7 @@ resource "aws_iam_user" "the-accounts" {
 }
 ```
 
-### `each` objects
+### `each` object
 
 In blocks where `for_each` is set, an additional `each` object is
 available in expressions, so you can modify the configuration of each instance.
@@ -128,9 +128,7 @@ maintainers.
 
 ### Referring to instances
 
-When `for_each` is set, Terraform distinguishes between the block, itself,
-and the multiple resource or module instances associated with it. Instances are
-identified by a map key or set member from the value provided to `for_each`.
+Terraform makes a distinction between the block containing the `for_each` argument and the instances associated with it. Terraform identifies instances by the map key or set member using the value provided to `for_each`.
 
 - `<TYPE>.<NAME>` or `module.<NAME>`: For example, `azurerm_resource_group.rg` refers to the block.
 - `<TYPE>.<NAME>[<KEY>]` or `module.<NAME>[<KEY>]`: For example, `azurerm_resource_group.rg["a_group"]` and `azurerm_resource_group.rg["another_group"]` refer to individual instances.
@@ -231,7 +229,7 @@ ephemeral "random_password" "db_passwords" {
 resource "aws_db_instance" "databases" {
   for_each = local.environments
 
-  identifier                = "${each.key}-database-${var.environment_suffix}"
+  identifier                = "${each.key}-database"
   db_name                   = "${each.key}db"
   username                  = "dbadmin"
   password_wo               = ephemeral.random_password.db_passwords[each.key].result

content/terraform/v1.13.x/docs/language/meta-arguments/lifecycle.mdx

@@ -9,7 +9,7 @@ Terraform performs the following operations when you apply a configuration:
 
 1. Creates resources defined in the configuration that are not associated with a real infrastructure object in the state.
 1. Destroys resources that exist in the state but not in the configuration.
-1. Updates in-place resources whose arguments have changed.
+1. Updates resources in-place whose arguments have changed.
 1. Destroys and re-create resources whose arguments have changed but that Terraform cannot update in-place because of remote API limitations.
 
 The `lifecycle` block accepts a rule that customizes how Terraform performs the lifecycle stages for each resource.