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/10/05/swift2nix.adoc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'src/content/blog/2020/10/05/swift2nix.adoc')

diff --git a/src/content/blog/2020/10/05/swift2nix.adoc b/src/content/blog/2020/10/05/swift2nix.adoc
index 4e0ae36..ba0125f 100644
--- a/src/content/blog/2020/10/05/swift2nix.adoc
+++ b/src/content/blog/2020/10/05/swift2nix.adoc
@@ -15,6 +15,7 @@ I wrote a simple little tool called {swift2nix}[swift2nix] that allows you trick
 Swift's package manager into assuming everything is set up.  Here's the example
 from swift2nix's README file:
 
+[source,nix]
 ----
 let
   niv-sources = import ./nix/sources.nix;
@@ -143,7 +144,7 @@ This is something that {node2nix}[node2nix] does right.  It allows you to build
 the Node.js environment to satisfy NPM, and you can keep using NPM for
 everything else:
 
-[source,shell]
+[source,sh]
 ----
 ln -s ${node2nix-package.shell.nodeDependencies}/lib/node_modules ./node_modules
 npm test
@@ -165,7 +166,7 @@ nice-to-have.
 swift2nix itself could provide an "easy" interface, something that allows you to
 write:
 
-[source,shell]
+[source,sh]
 ----
 nix-build -A swift2nix.release
 nix-build -A swift2nix.test
-- 
cgit v1.2.3

