Lowercased file extension on png files

Author: frwiqueueit

…ntation/ConfigurationProviderExample.PNG Documentation/ConfigProviderExample.pngDocumentation/ConfigurationProviderExample.PNG renamed to Documentation/ConfigProviderExample.png Documentation/ConfigurationProviderExample.PNG renamed to Documentation/ConfigProviderExample.png

@@ -10,7 +10,7 @@ It is recommended to make a timer function that can download and cache the confi
 You can find your configuration file here https://[your-customer-id].queue-it.net/status/integrationconfig/[your-customer-id]?qr=[time-based-query-string] after a succesful publish.
 Please contact Queue-it support through the Go Queue-it self-service portal to get further help on this.
 
-![Configuration Provider flow](https://github.com/queueit/KnownUser.V3.RubyOnRails/blob/master/Documentation/ConfigurationProviderExample.PNG)
+![Configuration Provider flow](https://github.com/queueit/KnownUser.V3.RubyOnRails/blob/master/Documentation/ConfigProviderExample.png)
 
 
 

Documentation/KnownUser flow.PNG Documentation/KnownUserFlow.pngDocumentation/KnownUser flow.PNG renamed to Documentation/KnownUserFlow.png

@@ -14,7 +14,7 @@ The most important fields of the `queueittoken` are:
 
 The high level logic is as follows:
 
-![The KnownUser validation flow](https://github.com/queueit/KnownUser.V3.RubyOnRails/blob/master/Documentation/KnownUser%20flow.PNG)
+![The KnownUser validation flow](https://github.com/queueit/KnownUser.V3.RubyOnRails/blob/master/Documentation/KnownUserFlow.png)
 
  1. User requests a page on your server
  2. The validation method sees that the has no Queue-it session cookie and no `queueittoken` and sends him to the correct queue based on the configuration