From 0b178d586733bf4e74f04646e0382236c659d176 Mon Sep 17 00:00:00 2001 From: Mukesh Kumar Date: Wed, 19 Jan 2022 11:49:25 +0530 Subject: [PATCH] Update website/docs/language/state/purpose.mdx Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> --- website/docs/language/state/purpose.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/language/state/purpose.mdx b/website/docs/language/state/purpose.mdx index 21639a1404..cc68a17ccc 100644 --- a/website/docs/language/state/purpose.mdx +++ b/website/docs/language/state/purpose.mdx @@ -24,7 +24,7 @@ shifting massive amounts of complexity from one place (state) to another place Terraform requires some sort of database to map Terraform config to the real world. For example, when you have a resource `resource "aws_instance" "foo"` in your configuration, Terraform uses this mapping to know that the resource `resource "aws_instance" "foo"` -represents a real world object having instance ID `i-abcd1234` on a remote system. +represents a real world object with the instance ID `i-abcd1234` on a remote system. For some providers like AWS, Terraform could theoretically use something like AWS tags. Early prototypes of Terraform actually had no state files and used