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/tils/2020/09/05/oldschool-pr.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'src/content/tils/2020/09/05/oldschool-pr.adoc')

diff --git a/src/content/tils/2020/09/05/oldschool-pr.adoc b/src/content/tils/2020/09/05/oldschool-pr.adoc
index a2c758c..392ec67 100644
--- a/src/content/tils/2020/09/05/oldschool-pr.adoc
+++ b/src/content/tils/2020/09/05/oldschool-pr.adoc
@@ -26,7 +26,7 @@ to be locked in by any of them, putting the "D" back in "DVCS": it’s a
 
 Here’s the raw output of a `git request-pull`:
 
-[source,shell]
+[source,sh]
 ----
 $ git request-pull HEAD public-origin
 The following changes since commit 302c9f2f035c0360acd4e13142428c100a10d43f:
@@ -62,7 +62,7 @@ address ready for public consumption.
 A simple solution for that is for you to add the `public-origin` alias as the
 HTTPS alternative to the SSH version:
 
-[source,shell]
+[source,sh]
 ----
 $ git remote add public-origin https://example.com/user/repo
 ----
@@ -78,7 +78,7 @@ Experiment it yourself, and get acquainted with the CLI.
 Now that you can create the content of a pull request, you can just
 {cli-email}[deliver it] to the interested parties email:
 
-[source,shell]
+[source,sh]
 ----
 # send a PR with your last commit to the author's email
 git request-pull HEAD public-origin | mail author@example.com -s "PR: Add thing to repo"
-- 
cgit v1.2.3

