From df033af96a4c0a45e66fa761611e7cbd71b71e18 Mon Sep 17 00:00:00 2001
From: Suraj Singh <36315541+mannusillegal@users.noreply.github.com>
Date: Tue, 31 May 2022 18:39:22 +0530
Subject: [PATCH] Update README.md

---
 14-Meta-Argument-for_each-Chaining/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/14-Meta-Argument-for_each-Chaining/README.md b/14-Meta-Argument-for_each-Chaining/README.md
index ad957b4..f921248 100644
--- a/14-Meta-Argument-for_each-Chaining/README.md
+++ b/14-Meta-Argument-for_each-Chaining/README.md
@@ -8,7 +8,7 @@ description: Learn Terraform Resource Meta-Argument for_each Chaining
 - Because a resource using `for_each` appears as a `map of objects` or `set of strings` when used in expressions elsewhere, you can directly use one resource as the `for_each of another in situations` where there is a `one-to-one relationship` between two sets of objects.
 - In our case, we will use the `azurerm_network_interface.myvmnic` resource directly in `azurerm_linux_virtual_machine.mylinuxvm` Resource. 
 
-## Step-02: Review Terarform Manifests
+## Step-02: Review Terraform Manifests
 - Copy the `terraform-manifests` from Section `11-Meta-Argument-count\terraform-manifests-v2` and re-implement this usecase using `for_each`. 
 - Also apply `for_each` chaining concept
 1. c1-versions.tf