Revert restructuring the learning go titles

src/blog/posts/2024/5/learning-go-day-2.md

@@ -1,5 +1,5 @@
 ---
-title: "Learning Go Day Two: Code organisation"
+title: "Learning Go: Day Two"
 date: 2024-05-02T08:00:00.0Z
 tags:
     - learning

src/blog/posts/2024/5/learning-go-day-3.md

@@ -1,5 +1,5 @@
 ---
-title: "Learning Go Day Three: Controls"
+title: "Learning Go: Day Three"
 date: 2024-05-03T08:00:00.0Z
 tags:
     - learning

src/blog/posts/2024/5/learning-go-day-4.md

@@ -1,5 +1,5 @@
 ---
-title: "Learning Go Day Four: Data structures"
+title: "Learning Go: Day Four"
 date: 2024-05-04T08:00:00.0Z
 tags:
     - learning

src/blog/posts/2024/5/learning-go-day-5.md

@@ -1,5 +1,5 @@
 ---
-title: "Learning Go Day Five: Tests"
+title: "Learning Go: Day Five"
 date: 2024-05-05T08:00:00.0Z
 tags:
     - learning

src/blog/posts/2024/5/learning-go-day-6.md

@@ -1,5 +1,5 @@
 ---
-title: "Learning Go Day Six: Picking a project"
+title: "Learning Go: Day Six"
 date: 2024-05-06T08:00:00.0Z
 tags:
     - learning
@@ -15,9 +15,9 @@ I'm going to make a simple uptime dashboard for my blog, in the same vein as [br
 * Give some up/downtime statistics
 * Display the current status, especially if things are broken
 
-Which means I'm going to need to:
+Which means it's going to need to:
 
-* Create a web server
+* Run a web server
 * Render web pages with some dynamic content
 * Store & read data from/to a database
 * Send requets to a server & handle the responses