add modules and name-spaces table to D.S. Internal Flow.

DeathSockets-Internal-Flow.md

@@ -1,6 +1,6 @@
 Although the system has a restricted input-output (I/O) flow from the outside, the internal flow is a bit more flexible. There is still a rigidity to it but it is not as one-dimensional. To help explain, please consider the image below.
 
-INTERFLOW FLOW IMAGE.
+![deathsocket internal flow](deathsocket-internal-flow.png)
 
 How this works is `GridPainter` receives input, usually a record type from `Domain`. From there, `GridPainter` utilises the various functions from the other files to complete the task it received. Because everything runs through`GridPainter`, it doubles up as the libraries co-ordinator. There is (for lack of a better word) no cross-pollination of function calls between the other files.
 
@@ -8,4 +8,11 @@ If you decide to add new features to the library, please try to keep to this flo
 
 **Note**: The modules listed above are situated in files with the same names -- for example, `GridPainter` resides in "GridPainter.fs", `Domain` resides in "Domain.fs" Etc.
 
-![deathsocket internal flow](attachments/deathsocket-internal-flow.png)
+|Module Name         |Name-Space   |File Location        |
+|:------------------:|:-----------:|:-------------------:|
+|`GridPainter`       |`DeathSocket`|GridPainter.fs       |
+|`ColourServices`    |N.A.         |ColourServices.fs    |
+|`Domain`            |`DeathSocket`|Domain.fs            |
+|`ImageServices`     |N.A.         |ImageServices.fs     |
+|`ImagePrep`         |N.A.         |ImagePrep.fs         |
+|`ValidationServices`|N.A.         |ValidationServices.fs|