diff --git a/content/blog/2024-01-07-01-SDBD.md b/content/blog/2024-01-07-01-SDBD.md
index b4d0e40..430646b 100644
--- a/content/blog/2024-01-07-01-SDBD.md
+++ b/content/blog/2024-01-07-01-SDBD.md
@@ -2,7 +2,7 @@
 date: 2024-01-07
 title: Let's Create a Data Format
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 1
 ---
 I have a problem. I want to be able to transfer self-contained binary data with metadata through a variety of protocols with no knowledge of the binary data's format or the protocol being used for transfer.
diff --git a/content/blog/2024-01-07-02-Semantics.md b/content/blog/2024-01-07-02-Semantics.md
index c5b1f0e..efe38c9 100644
--- a/content/blog/2024-01-07-02-Semantics.md
+++ b/content/blog/2024-01-07-02-Semantics.md
@@ -2,7 +2,7 @@
 date: 2024-01-07
 title: Semantics of SDBD
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 2
 ---
 To really start bringing this new data format to life, we need to talk about what's in it. Establishing the semantics of a format gives us the terms and concepts we need to talk about the format abstractly before we get to any concrete details.
diff --git a/content/blog/2024-01-07-03-Data_Format.md b/content/blog/2024-01-07-03-Data_Format.md
index 5bacdfa..4661aef 100644
--- a/content/blog/2024-01-07-03-Data_Format.md
+++ b/content/blog/2024-01-07-03-Data_Format.md
@@ -2,7 +2,7 @@
 date: 2024-01-07
 title: What Does SDBD Actually Look Like?
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 3
 ---
 To turn the semantics into a real file format, we need to define what they look like as actual data. How do you write an SDBD to a stream or a disk? How do we turn our HTTP-like semantics into a real document? That question almost answers itself. I'll keep stealing from HTTP.
diff --git a/content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md b/content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md
index c415c7b..d63bae4 100644
--- a/content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md
+++ b/content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md
@@ -2,7 +2,7 @@
 date: 2024-01-09
 title: Building a Proof of Concept
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 4
 ---
 The format certainly looks sound. Could there be any surprises when we try to implement it? There's one way to find out. I'll write a Proof of Concept. Finally, we get to the code!
diff --git a/content/blog/2024-01-09-02-The_Heart_of_the_Code.md b/content/blog/2024-01-09-02-The_Heart_of_the_Code.md
index 5b5515c..d21b95f 100644
--- a/content/blog/2024-01-09-02-The_Heart_of_the_Code.md
+++ b/content/blog/2024-01-09-02-The_Heart_of_the_Code.md
@@ -2,7 +2,7 @@
 date: 2024-01-09
 title: The Heart of the Code
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 5
 ---
 To complete the proof of concept we need to implement `SDBD.ICodec`. This is what we're proving after all. The most complicated part will be the HPACK encoding. I'd rather not implement that myself, not for something basic. Fortunately there is a NuGet package that should do the trick. It's called simply `hpack`.
diff --git a/content/blog/2024-01-09-03-Improvements.md b/content/blog/2024-01-09-03-Improvements.md
index 1df319d..da158ae 100644
--- a/content/blog/2024-01-09-03-Improvements.md
+++ b/content/blog/2024-01-09-03-Improvements.md
@@ -1,8 +1,8 @@
 ---
 date: 2024-01-09
-title: Improvements
+title: Improvements to SDBD
 series:
-  name: SDBD - Creating a Data Format
+  name: "SDBD: Creating a Data Format"
   number: 6
 ---
 ## Format