From 89f982b2b3017560d043b235dc8ec8c4c89d5129 Mon Sep 17 00:00:00 2001
From: battery <chaselonas@gmail.com>
Date: Fri, 2 Feb 2024 08:19:16 -0500
Subject: [PATCH] improved readability in terraform topic README (#395)

---
 topics/terraform/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/topics/terraform/README.md b/topics/terraform/README.md
index 38c9bd6..1f01fd5 100644
--- a/topics/terraform/README.md
+++ b/topics/terraform/README.md
@@ -359,7 +359,7 @@ False. You can specify any provider from any URL, not only those from hashicorp.
 #### Input Variables
 
 <details>
-<summary>What input variables are good for in Terraform?</summary><br><b>
+<summary>What are input variables good for in Terraform?</summary><br><b>
 
 Variables allow you define piece of data in one location instead of repeating the hardcoded value of it in multiple different locations. Then when you need to modify the variable's value, you do it in one location instead of changing each one of the hardcoded values.
 </b></details>
@@ -1874,4 +1874,4 @@ If it's a matter of changing a resource name, you could make use of `terraform s
 
 Use the meta-argument `depends_on` in the app resource definition. This way the app will depend on the cluster resource and order will be maintained in creation of the resources.
 
-</b></details>
\ No newline at end of file
+</b></details>