Updates

feed.xml

@@ -107,9 +107,7 @@
   issuers can contact you if there is a problem with your certificates.
 </p>
 <p><code>/etc/caddy/Caddyfile</code></p>
-<pre
-  class="language-undefined"
-><code class="language-undefined"># Global options block
+<pre class="language-caddy"><code class="language-caddy"># Global options block
 {
 	email you@example.com # <<<< CHANGE THIS <<<<
 	on_demand_tls {
@@ -341,27 +339,28 @@ https:// {
 </h2>
 <p>
   It works!<br />
-  This repo is in my Forgejo instance:
+  Here is
   <a
     href="https://git.apps.seigler.net/joshua/marklink.pages.seigler.net"
     target="_blank"
     rel="noopener"
-    >https://git.apps.seigler.net/joshua/marklink.pages.seigler.net</a
-  ><br />
-  And its contents are visible here on my Caddy server:
-  <a href="https://marklink.pages.seigler.net/" target="_blank" rel="noopener"
-    >https://marklink.pages.seigler.net/</a
+    >the marklink repo in my Forgejo instance</a
   >
+  and
+  <a href="https://marklink.pages.seigler.net/" target="_blank" rel="noopener"
+    >its contents on my Caddy server</a
+  >.
 </p>
 <p>
-  For repos with npm build scripts, I use
+  That repo is just HTML and JS with only a gh-pages branch, but for repos with
+  npm build scripts, I use
   <a
     href="https://www.npmjs.com/package/gh-pages"
     target="_blank"
     rel="noopener"
     >gh-pages @ npm</a
   >
-  to push the build to the gh-pages branch and up to the server.
+  to push the build to a gh-pages branch and up to the server.
 </p>
 <p>
   I’m putting off rolling my own CI server, but I imagine that’s the next stage