README.md in gridium-1.1.24 vs README.md in gridium-1.1.25

@@ -30,13 +30,14 @@
 Gridium.configure do |config|
   config.report_dir = '/path/to/automation/project'
   config.browser_source = :local
   config.selenium_log_level = 'OFF' #OFF, SEVERE, WARNING, INFO, DEBUG, ALL https://github.com/SeleniumHQ/selenium/wiki/Logging
   config.target_environment = "Integration"
-  config.browser = :firefox
+  config.browser = :chrome
   config.url = "http://www.applicationundertest.com"
   config.page_load_timeout = 30
+  config.page_load_retry = 0
   config.element_timeout = 30
   config.visible_elements_only = true
   config.log_level = :debug
   config.highlight_verifications = true
   config.highlight_duration = 0.100
@@ -100,9 +101,10 @@
 `config.selenium_log_level = 'OFF'`: This tells gridium which level to use for Selenium's loggingPrefs, which are then logged at the debug level.
 `config.target_environment = "Stage"`: This is a simple log entry to tell remind you which environment you're testing.  
 `config.browser = :firefox`: This tells gridium which browser you will be testing.  Only firefox is working currently.  Future browsers to come.  
 `config.url = "http://www.applicationundertest.com"`: Where's the entry point for your web application?  
 `config.page_load_timeout = 30` Along with Element Timeout, how long (in seconds) should Selenium wait when finding an element?  
+`config.page_load_retry = 1` On a failure to load the requested page, Gridium will retry loading the page this many times.  
 `config.visible_elements_only = true`: With this enabled Gridium will only find VISIBLE elements on the page.  Hidden elements or non-enabled elements will not be matched.  
 `config.log_level = :debug`: There are a few levels here `:debug` `:info` `:warn` `:error` and `:fatal`.  Your Gridium tests objects can have different levels of logging.  Adjusting this setting will turn those log levels on or off depending on your needs at the time.  
 `config.highlight_verifications = true`: Will highlight the element Gridium finds in the browser.  This makes watching tests run easier to follow, although it does slow the test execution time down.  Recommend this is turned off for automated tests running in Jenkins or headless mode.  
 `config.highlight_duration = 0.100`: How long should the element be highlighted (in milliseconds) before the action is performed on the element.  
 `config.screenshot_on_failure = false`: Take a screenshot on failure.  On or off. Obviously.