Restored images in docs

Author: JakeGinnivan

docs/ScreenObjects/RefactoringToUseScreenObjects.md

@@ -74,7 +74,7 @@ So the example becomes like this.
 Setup method (as it has the SetUpAttribute on it) would be executed before every test. Also common stuff between two tests has been extracted into a method.
 From the point of organizing the tests I would put these two tests in a class (TestFixture in NUnit terminology) like CreateCustomerTest.
 
-![RefactoringToUseScreenObjects](../../img/White/ScreenObjects/RefactoringToUseScreenObjects.png)
+![RefactoringToUseScreenObjects](../images/ScreenObjects/RefactoringToUseScreenObjects.png)
 
 ## Reusing code across different tests
 We have written test for create customer. Lets write a test for searching a customer.
@@ -248,7 +248,7 @@ Using these screen objects, this is how our test looks like.
 
 Functional tests (like any other program) should be readable. The intent of test here is lot clearer than when test was dealing with the UIItems on the screen. This is what we have built.
 
-![RefactoringToUseScreenObjects](../../img/White/ScreenObjects/RefactoringToUseScreenObjects1.png)
+![RefactoringToUseScreenObjects](../images/ScreenObjects/RefactoringToUseScreenObjects1.png)
 
 
 We have now got to the point where we have written our own Screen Objects. White takes this further!

docs/ScreenObjects/TestEntities.md

@@ -101,4 +101,4 @@ The test now uses the Customer object
 
 Our current design now looks like this.
 
-![TestEntities](../../img/White/ScreenObjects/TestEntities.png)
+![TestEntities](../images/ScreenObjects/TestEntities.png)

docs/Windows.md

@@ -32,7 +32,7 @@ any window, including it child controls can have only one visible tooltip at a t
 
 	string message = window.ToolTip;
 
-In some applications the tool tip is associated to an error provider which looks like ![Windows](../img/White/Windows.png). 
+In some applications the tool tip is associated to an error provider which looks like ![Windows](images/Windows.png). 
 
 When mouse is hovered on it, a message is shown as tooltip. This need not be implemented by user as it is pretty standard behaviour and white provides it out of the box. If the message is set on the error provider for ComboBox then:
 

docs/index.md

@@ -3,7 +3,7 @@ White is a framework for automating rich client applications based on Win32, Win
 ##How white works?
 
 At runtime white programs stack would look like this.
-![Index](../img/White/Index.png)
+![Index](images/Index.png)
 
 White programs **must** run in a different process from the AUT (Application Under Test) process.
 
@@ -40,7 +40,7 @@ See Working with window for more.
 UIItems can be searched based on a lot of parameters. For more look here: UIItem Identification
 
 ## Architecture
-![Index1](../img/White/Index1.png)
+![Index1](images/Index1.png)
 
 ## Silverlight Support
 You would need to add reference to white.webbrowser.dll along with TestStack.White.dll.