blog: added corrections to past posts

2 files changed, 7 insertions, 11 deletions

diff --git a/content/posts/switching-to-hugo-one/index.md b/content/posts/switching-to-hugo-one/index.md
index 1217434..53b89c5 100644
--- a/content/posts/switching-to-hugo-one/index.md
+++ b/content/posts/switching-to-hugo-one/index.md
@@ -15,7 +15,7 @@ Hello friends, and welcome [back] to my blog! It has been quite some time since
 my last post, and I thought I'd take a moment to catch everyone up to speed on
 the changes I've made since then.
 
-## A "new" website.
+## A "New" Website.
 For those reading via RSS, you will notice little to no change. However, if you
 point your browser to https://tdback.net, things will look noticeably
 different.
@@ -51,5 +51,3 @@ So far my experience with Hugo has been great! After just a few hours I had a
 working site, RSS feed, and an established workflow for writing. If you're
 interested in the technical details of how I host my website, read onwards to
 [part two](/posts/switching-to-hugo-two/).
-
-Happy hacking!
diff --git a/content/posts/switching-to-hugo-two/index.md b/content/posts/switching-to-hugo-two/index.md
index 2b95f51..22f7d56 100644
--- a/content/posts/switching-to-hugo-two/index.md
+++ b/content/posts/switching-to-hugo-two/index.md
@@ -10,13 +10,13 @@ draft = false
 website. For an explanation as to why I made the switch, read
 [part one](/posts/switching-to-hugo-one/).*
 
-# Hosting my website
-My website is hosted on [caddy](https://caddyserver.com), a popular HTTPS
+# Hosting My Website
+My website is hosted using [caddy](https://caddyserver.com), a popular HTTPS
 server and reverse proxy. Caddy automatically obtains and renews TLS
 certificates for my domains, which makes TLS certificate management a breeze.
 The caddy server runs on one of my home servers, which itself runs NixOS.
 
-## Configuring a web server on NixOS
+## Configuring the Web Server
 [NixOS](https://nixos.org) allows for reproducible and declarative system
 configurations, which makes the process of configuring and deploying a web
 server quite trivial. One benefit of running my website on NixOS - aside from
@@ -26,7 +26,7 @@ same, regardless of the server it's running on. This alleviates the headache of
 dependency management and reduces setup times down to just
 `nixos-rebuild switch`, should I have the need to move my website to different
 hardware. The [nix flake for my system
-configurations](https://codeberg.org/tdback/nix-config) is tracked in a remote
+configurations](https://github.com/tdback/nix-config) is tracked in a remote
 repository with `git`, making configuration changes a single `git pull` away.
 
 The following module defined in `modules/services/proxy/default.nix` enables
@@ -72,7 +72,7 @@ https://tdback.net to my web server's IPv6 address (including requests made to
 the server using IPv4!) but that's pretty much it in regards to the server
 configuration.
 
-## Writing and managing content
+## Writing and Managing Content
 The following is a nix flake I've written to create a development environment
 on my desktop for managing the content and generation of my website.
 
@@ -128,7 +128,7 @@ defined in the `shellHook` attribute are *only available when I'm in the
 temporary shell environment*, thus reducing the clutter of programs, their
 dependencies, environment variables, and function definitions.
 
-## Deployment of the site
+## Deployment of the Site
 When I make a change to the website, the entire site can be regenerated and
 deployed to the NixOS server by running the following one-liner:
 
@@ -140,5 +140,3 @@ I've placed this command in a shell script to make deployments as simple as
 typing `./deploy.sh`. This results in near-zero downtime between changes: a
 simple refresh of the page on a client's device will load the newest version of
 the site.
-
-Happy hacking!