.config.example.yml in quke-0.2.8 vs .config.example.yml in quke-0.3.0

@@ -23,10 +23,41 @@
 # Specify whether Quke should stop all tests once an error occurs. Useful in
 # Continuous Integration (CI) environments where a quick Yes/No is preferable to
 # a detailed response.
 stop_on_error: 1
 
+# Capybara will attempt to find an element for a period of time, rather than
+# immediately failing because the element cannot be found. This defaults to 2
+# seconds. However if the site you are working with is slow or features
+# elements that take some time to load you can increase this default.
+max_wait_time: 5
+
+# Anything you place under the 'custom' node in the `.config.yml` file will be
+# available within your steps and page objects by calling
+# `Quke::Quke.config.custom`. So using the example below we could access its
+# values in the following ways
+#
+# Quke::Quke.config.custom["default_org_name"] # = "Testy Ltd"
+# Quke::Quke.config.custom["accounts"]["account2"]["username"] # = "[e-mail]"
+# Quke::Quke.config.custom["urls"]["front_office"] # = "http://myservice.service.gov.uk"
+#
+# As long as what you add is valid YAML (check with a tool like
+# http://www.yamllint.com/) Quke will be able to pick it up and make it
+# available in your tests.
+custom:
+  default_org_name: "Testy Ltd"
+  accounts:
+    account1:
+      username: [e-mail]
+      password: Av3rystr*ngone
+    account2:
+      username: [e-mail]
+      password: An*th3rstrongone
+  urls:
+    front_office: "http://myservice.service.gov.uk"
+    back_office: "http://admin-myservice.service.gov.uk"
+
 # If you are running Quke behind a proxy you can configure the proxy details
 # here. You'll need either the hostname or IP of the proxy server (don't include
 # the http:// bit) and the port number (typically 8080). Currently proxy
 # settings will only be applied if you are using the PhantomJS, Chrome or
 # Firefox drivers.
@@ -56,10 +87,10 @@
   # capabilities. Group your tests into builds, and builds further into projects
   build: 'Version 1'
   project: 'Adding browserstack support'
 
   # Allows you to specify an identifier for the test run.
-  # If you intend to repeat a test this might not be that aplicable, but in the
+  # If you intend to repeat a test this might not be that applicable, but in the
   # case of one off tests it might be useful
   name: 'Testing google search'
 
   # MOBILE testing
   # The docs are a little confusing but essentially if you want to test against