Writing-Command-Methods.md

@@ -23,7 +23,7 @@ public static string CommandMethodName()
 
 More examples can be found at the following link:
 
-- [CW_Core_Console's ConsoleCommands.cs](https://git.abbether.net/craig.oates/Console.Waterworks.Core/blob/master/CW_Core_Console/ConsoleCommands.cs)
+- [CW_Core_Console's ConsoleCommands.cs](https://git.abbether.net/craig.oates/Console.Waterworks.Core/src/branch/master/CW_Core_Console/ConsoleCommands.cs)
 
 What is important to note here is the importance of the command-method names. The names you use are the exact same commands your end-user will enter at run-time. The console's input is, also, case-sensitive. This means you can have two command-methods called `Test` and `test` and have them do different things.
 
@@ -37,6 +37,6 @@ Another feature of C.W.C. is it parses and coerces input arguments. This means y
 
 To be clear, there are limits to the amount of types you can use with your command-methods. For a full, list of all the coercion types, please refer to the Coercion Types List in the main Console.Waterworks wiki. The link for it is as follows:
 
-- [Coercion Types List](https://git.abbether.net/craig.oates/Console.Waterworks/wikis/Coercion-Types-List) (in the main C.W. wiki)
+- [Coercion Types List](https://git.abbether.net/craig.oates/Console.Waterworks/wiki/Coercion-Types-List) (in the main C.W. wiki)
 
 If you write command-methods with arguments **not** on the coercion list, you will get a run-time error. With that said, you are free to use whatever types you want **inside** the command-methods.