diff --git a/content/roadmaps/102-devops/content/105-infrastructure-as-code/readme.md b/content/roadmaps/102-devops/content/105-infrastructure-as-code/readme.md
index d3656afcf..bfcfd4f0b 100644
--- a/content/roadmaps/102-devops/content/105-infrastructure-as-code/readme.md
+++ b/content/roadmaps/102-devops/content/105-infrastructure-as-code/readme.md
@@ -1,6 +1,6 @@
 # Infrastructure as Code
 
-Sometimes referred to as IaaC, this section refers to the techniques and tools used to define infrastructure, typically in a markup language like YAML or JSON. Infrastructure as code allows DevOps Engineers to use the same workflows used by software developers to version, roll back, and otherwise manage changes.  
+Sometimes referred to as IaC, this section refers to the techniques and tools used to define infrastructure, typically in a markup language like YAML or JSON. Infrastructure as code allows DevOps Engineers to use the same workflows used by software developers to version, roll back, and otherwise manage changes.  
 
 The term Infrastructure as Code encompasses everything from bootstrapping to configuration to orchestration, and it is considered a best practice in the industry to manage all infrastructure as code.  This technique precipitated the explosion in system complexity seen in modern DevOps organizations.