From d36c2e459a74ec67e523539eb98b78b95b01432a Mon Sep 17 00:00:00 2001
From: EuAndreh <eu@euandre.org>
Date: Wed, 16 Apr 2025 11:20:43 -0300
Subject: src/content/: Normalize [source,$lang] code blocks

---
 src/content/blog/2020/11/14/local-first-review.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'src/content/blog/2020/11/14/local-first-review.adoc')

diff --git a/src/content/blog/2020/11/14/local-first-review.adoc b/src/content/blog/2020/11/14/local-first-review.adoc
index 2a57664..f9dd4b0 100644
--- a/src/content/blog/2020/11/14/local-first-review.adoc
+++ b/src/content/blog/2020/11/14/local-first-review.adoc
@@ -46,7 +46,7 @@ ____
 They give examples of artificial restrictions, like this artificial restriction
 I've come up with:
 
-[source,bash]
+[source,sh]
 ----
 #!/bin/sh
 
@@ -63,7 +63,7 @@ echo $((2 + 2))
 
 Now when using this very useful program:
 
-[source,bash]
+[source,sh]
 ----
 # today
 $ ./useful-adder.sh
@@ -84,7 +84,7 @@ or similar restriction, and stopped working after days pass?  Or what if the
 programmer added a constant to make the development simpler, and this led to
 unintentionally restricting the user?
 
-[source,bash]
+[source,sh]
 ----
 # today
 $ useful-program
-- 
cgit v1.2.3

