From ff40caa62ab4430b81e9c8d38d77d3b64814185e Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Tue, 30 Nov 2021 21:58:45 +0000
Subject: Publishing new version

---
 gemfeed/2021-05-16-personal-bash-coding-style-guide.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'gemfeed/2021-05-16-personal-bash-coding-style-guide.html')

diff --git a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
index 97cd3eca..4ac1124c 100644
--- a/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
+++ b/gemfeed/2021-05-16-personal-bash-coding-style-guide.html
@@ -83,7 +83,7 @@ p.quote:after {
 //  \\               //  \\ |===||  hjw
 "\__/"---------------"\__/"-+---+'
 </pre>
-<p class="quote"><i>Written by Paul Buetow 2021-05-16</i></p>
+<p class="quote"><i>Published by Paul Buetow 2021-05-16</i></p>
 <p>Lately, I have been polishing and writing a lot of Bash code. Not that I never wrote a lot of Bash, but now as I also looked through the Google Shell Style Guide, I thought it is time also to write my thoughts on that. I agree with that guide in most, but not in all points. </p>
 <a class="textlink" href="https://google.github.io/styleguide/shellguide.html">Google Shell Style Guide</a><br />
 <h2>My modifications</h2>
-- 
cgit v1.2.3