diff --git a/content/blog/2021-02-07-infrastructure-as-code.md b/content/blog/2021-02-07-infrastructure-as-code.md
index 056e3a8..2624803 100644
--- a/content/blog/2021-02-07-infrastructure-as-code.md
+++ b/content/blog/2021-02-07-infrastructure-as-code.md
@@ -6,6 +6,9 @@ updated = 2025-03-12
 
 [taxonomies]
 tags = ["Infrastructure", "Automation", "Quality"]
+
+[extra]
+social_media_card = "img/social_cards/blog_infrastructure_as_code.jpg"
 +++
 
 # Introduction
@@ -69,8 +72,10 @@ it. On the other hand, provisioning it through code will make the process reusab
 this server as code, is the better approach. Defining everything as code enables you to leverage speed to improve quality, much like Agile
 uses speed to improve software quality by having tight feedback loops and iterating on that feedback.
 
-Infrastructure code can use declarative or imperative
-languages[^2: "Imperative code is a set of instructions that specifies how to make a thing happen. Declarative code specifies what you want, without specifying how to make it happen."].
+Infrastructure code can use declarative or imperative languages[^2].
+
+[^2]: Imperative code is a set of instructions that specifies how to make a thing happen. Declarative code specifies what you want, without
+specifying how to make it happen.
 
 # Infrastructure stacks
 
diff --git a/static/img/social_cards/blog_infrastructure_as_code.jpg b/static/img/social_cards/blog_infrastructure_as_code.jpg
index fe75bed..c7f994e 100644
Binary files a/static/img/social_cards/blog_infrastructure_as_code.jpg and b/static/img/social_cards/blog_infrastructure_as_code.jpg differ