From e10cf6dabdcf8c8dfc16edfdf0473893fc8dc5a4 Mon Sep 17 00:00:00 2001 From: Nikolai Vavilov Date: Sun, 11 Nov 2018 23:15:11 +0200 Subject: [PATCH] website: add missing article --- website/intro/getting-started/change.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/intro/getting-started/change.html.md b/website/intro/getting-started/change.html.md index 5784af60de..d65bbe6488 100644 --- a/website/intro/getting-started/change.html.md +++ b/website/intro/getting-started/change.html.md @@ -71,7 +71,7 @@ AMI for an EC2 instance requires recreating it. Terraform handles these details for you, and the execution plan makes it clear what Terraform will do. Additionally, the execution plan shows that the AMI change is what -required resource to be replaced. Using this information, +required the resource to be replaced. Using this information, you can adjust your changes to possibly avoid destroy/create updates if they are not acceptable in some situations.