add image to Using Death Socket in Your Project.

Using-Death-Socket-in-Your-Project.md

@@ -33,7 +33,7 @@ If you look at the source code for D.S., you will see I have included two graphi
 
 I have included these two libraries because D.S. is a .Net Standard 2.0 library. This means the code in D.S. can run on the traditional .Net framework and .Net Core. If you are building a traditional .Net application (E.G. a W.P.F. app.), I recommend you use *System.Drawing*. If you are creating a cross-platform application (E.G. a Xamarin app.), you will need to use the *SkiaSharp* parts of D.S. This means the general flow of the system looks like this,
 
-IMAGE OF SYSTEM FLOW.
+![deathsocket graphics lib. divide](attachments/deathsocket-graphics-lib-divide.png)
 
  If you would like to know more about these graphics libraries, please use the following links;
 
@@ -46,7 +46,7 @@ This next bit is an aside; So, feel free to skip over this bit and jump straight
 
 As a consumer of D.S., you will not have access to every part of it. Instead, you work with two modules within a single name-space, called `DeathSocket`. The module's names are `Domain` and `GridPainter`.
 
-IMAGE OF THE MODULES AND THEIR RELATIONSHIPS.
+![deathsocket public modules](attachments/deathsocket-pubic-modules.png)
 
 The above image shows the flow of a typical code-base using D.S. Looking at this, you would think the `GridPainter` module is where you should focus most of your time. This is not immediately true, though. If anything, forming good image-specifications is the more time consuming task.