diff --git a/Home.md b/Home.md
index 6dc64f3..4d8ac4e 100644
--- a/Home.md
+++ b/Home.md
@@ -3,25 +3,25 @@
 * Email: [craig@craigoates.net](mailto:craig@craigoates.net)
 * License: [MIT](https://gitlab.com/craig.oates/Brittle-Fish/blob/master/LICENSE)
 
-Welcome to the wiki of Brittle-Fish. If you are looking to learn about using Console.Waterworks in a F#-only environment, you have come to the right place. The aim of this wiki is to teach you about using Console.Waterworks in an F# context. I recommend you read the actual Console.Waterworks wiki if you want to know how it works. You can head over to the wiki by clicking the following link,
+Welcome to the wiki of Brittle-Fish. If you are looking to learn about **using** Console.Waterworks in a F#-only environment, you have come to the right place. The aim of this wiki is to teach you about using Console.Waterworks in an F# context. I recommend you read the actual Console.Waterworks wiki if you want to know how it works. You can head over to the wiki by clicking the following link,
 
 * [Console.Waterworks Wiki](https://gitlab.com/craig.oates/Console.Waterworks/wikis/home)
 
 Before continuing, I recommend you are familiar with the following;
 
-* .Net 4.7+ and/or .Net Core 2.0+
-* Visual Studio 17 (15.3.9+)
-* F# 4.1+
-* NuGet
+* [.Net 4.7+ and/or .Net Core 2.0+](https://dotnet.microsoft.com)
+* [Visual Studio 17 (15.3.9+)](https://visualstudio.microsoft.com)
+* [F# 4.1+](https://fsharp.org)
+* [NuGet](https://www.nuget.org)
 
 ## Notes on Writing Style
 
 1. Because Console.Waterworks and Console.Waterworks.Core are wordy, I will usually refer them as "C.W." and "C.W.C".
 2. Because C.W.C. is just the .Net Core version of C.W., I will sometimes say C.W. when I mean both. Hopefully, this grouping makes sense when viewed in context.
-3. I will sometimes use "console program" and "console project" interchangeably. This because how Visual Studio's "file system" works. Overall, there is a "solution" which holds "projects". A project can consist of things like a console program. In-effect, this makes it a "program" and a "project". Hopefully, this makes sense when viewed in context.
+3. I will sometimes use "console program" and "console project" interchangeably. This is because how Visual Studio's "file system" works. Overall, there is a "solution" which holds "projects". A project can consist of things like a console program. In-effect, this makes it a "program" and a "project". Hopefully, this makes sense when viewed in context.
+4. In an attempt to keep a level of consistency, I will abbreviate words with a full-stop. So, "HTML" will be written as H.T.M.L. This is because I usually abbreviate "non-tech." words this way and I am not keen on using the different styles in the same text.
 
-## Where to go Next
+## Table of Contents
 
-* [Table of Contents](Table-Of-Contents)
 * [Code Snippets for Common Tasks](https://gitlab.com/craig.oates/Brittle-Fish/snippets)
-* [Next Page: Introduction to Brittle-Fish](Introduction to Brittle-Fish)
+