src/content/: Normalize [source,$lang] code blocks

4 files changed, 9 insertions, 8 deletions

diff --git a/src/content/blog/2020/08/10/guix-srht.adoc b/src/content/blog/2020/08/10/guix-srht.adoc
index 6411259..a89e86e 100644
--- a/src/content/blog/2020/08/10/guix-srht.adoc
+++ b/src/content/blog/2020/08/10/guix-srht.adoc
@@ -18,7 +18,7 @@ heavily on interactive input.
 I developed the following set of scripts that I have been using for some time to
 run Guix tasks inside builds.sr.ht jobs.  First, `install-guix.sh`:
 
-[source,shell]
+[source,sh]
 ----
 #!/usr/bin/env bash
 set -x
@@ -67,7 +67,7 @@ guixbuild users and authorize the `ci.guix.gnu.org.pub` signing key.
 After installing Guix, we perform a `guix pull` to update Guix inside
 `start-guix.sh`:
 
-[source,shell]
+[source,sh]
 ----
 #!/usr/bin/env bash
 set -x
diff --git a/src/content/blog/2020/10/05/cargo2nix.adoc b/src/content/blog/2020/10/05/cargo2nix.adoc
index 38f3bfa..a2d478e 100644
--- a/src/content/blog/2020/10/05/cargo2nix.adoc
+++ b/src/content/blog/2020/10/05/cargo2nix.adoc
@@ -60,7 +60,7 @@ internal to Cargo.
 
 Try out the demo (also taken from the repo's README):
 
-[source,shell]
+[source,sh]
 ----
 pushd "$(mktemp -d)"
 wget -O- https://euandre.org/static/attachments/cargo2nix-demo.tar.gz |
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
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