add images to Referencing Other Projects.

Referencing-Other-Projects.md

@@ -4,11 +4,11 @@ To help get a feel for how Console.Waterworks (C.W.) based projects looks when u
 
 If you look in the Solution Explorer, in Visual Studio, you will see four projects. Two of them are console programs and the other two are libraries. Each library is paired  with a console project. So, in-effect, there are two "projects". Although, there is really on one project. This is because the "two" projects are different flavours on .Net. They both do the same thing, but target different environments. (.Net is in a bit of a mess at the time of writing this.)
 
-IMAGE OF SOLUTION BREAKDOWN.
+![solution overview](attachments/solution-overview.png)
 
 Feel free to focus on either the .Net or .Net Core "projects". They both mirror each other so, if you learn one, you learn the other. The only reason I included both was for the sake of completeness. The important thing to take away, here, is the console-to-library relationship.
 
-IMAGE OF CONSOLE-LIBRARY CONNECTION.
+![console-library relationship](attachments/console-library-relationship.png)
 
 If we wanted to be more exact about the relationship, `ConsoleCommands` is bound to `FunkyFish` (or `FunkyFishCore`). And you can see this in the repositories code.
 
@@ -52,7 +52,7 @@ namespace Commands
 			String.Format("Result: {0}", LibraryTest3 name) // Library Call to FunkyFish.
 ```
 
-IMAGE OF FUNCTION TO FUNCTION RELATIONSHIP.
+![consolecommands library binding](attachments/consolecommands-library-binding.png)
 
 As you can see, once you are inside a command-method, you are free to put any code you want in there. For example, you can call your library code.