diff --git a/content/blog/02_learning_emulation.md b/content/blog/02_learning_emulation.md
index 24c5095..70af90a 100644
--- a/content/blog/02_learning_emulation.md
+++ b/content/blog/02_learning_emulation.md
@@ -3,7 +3,7 @@ title: Learning Emulation, Part 2
date: 2016-11-23 23:23:18.664038
tags: ["C and C++", "Emulation"]
---
-_This is the second post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< ref "/blog/01_learning_emulation.md" >}})._
+_This is the second post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< relref "/blog/01_learning_emulation.md" >}})._
Now that we have an understanding of the physical capabilities of a Chip-8 system, we can write code that will represent such a system on our computer. In this post we'll start writing some basic code - be prepared.
diff --git a/content/blog/03_learning_emulation.md b/content/blog/03_learning_emulation.md
index 2a9ade6..bbfe34c 100644
--- a/content/blog/03_learning_emulation.md
+++ b/content/blog/03_learning_emulation.md
@@ -3,7 +3,7 @@ title: Learning Emulation, Part 2.5 - Implementation
date: 2016-11-23 23:23:56.633942
tags: ["C and C++", "Emulation"]
---
-_This is the third post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< ref "/blog/01_learning_emulation.md" >}})._
+_This is the third post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< relref "/blog/01_learning_emulation.md" >}})._
In the previous part of this tutorial, we created a type to represent a basic Chip-8 machine. However, we've done nothing to make it behave like one! Let's start working on that.
diff --git a/content/blog/haskell_language_server_again.md b/content/blog/haskell_language_server_again.md
index ce678f5..8debdaf 100644
--- a/content/blog/haskell_language_server_again.md
+++ b/content/blog/haskell_language_server_again.md
@@ -21,7 +21,7 @@ GHC IDE is a Haskell-based program that uses the
{{< sidenote "right" "lsp-note" "language server protocol" >}}
You don't really need to know what the language server protocol (LSP) is
to use GHC IDE. If you are nonetheless interested, I wrote a little
-bit about it }}#prelude-language-server-protocol">in the previous iteration of this post.
+bit about it }}#prelude-language-server-protocol">in the previous iteration of this post.
If you want more information, check out the official Microsoft page on LSP.
{{< /sidenote >}} to communicate with any editor that supports it. Editors
with support the the LSP include Atom, Visual Studio Code, Emacs, and Vim. Thus,
@@ -61,7 +61,7 @@ export PATH=$PATH:/home//.local/bin
On Windows, this is done by
{{< sidenote "right" "path-note" "editing your PATH variable." >}}
If you need to know how to change your PATH, I wrote
-about it briefly in the }}
+about it briefly in the }}
#installation-of-v0-5-0-0-windows-systems">previous iteration of this post.
{{< /sidenote >}} I don't run Windows,
so I don't know where `cabal install` will place the executable, but I do know