README.md in knapsack_pro-1.0.0 vs README.md in knapsack_pro-1.0.1

@@ -317,12 +317,17 @@
 require 'logger'
 KnapsackPro.logger = Logger.new(STDOUT)
 KnapsackPro.logger.level = Logger::DEBUG
 ```
 
-Debug is default log level and this is recommended. [Read more](#how-can-i-change-log-level).
+Debug is default log level and it is recommended. [Read more](#how-can-i-change-log-level).
 
+Note your own logger is configured in `spec_helper.rb` or `rails_helper.rb` and it will start working when those files will be loaded.
+It means the very first request to Knapsack Pro API will be log to `STDOUT` using logger built into knapsack_pro instead of your custom logger.
+
+If you want to change log level globally than just for your custom log level, please [see this](#how-can-i-change-log-level).
+
 ### Setup your CI server (How to set up 2 of 3)
 
 #### Set API key token
 
 Set one or more tokens depending on how many test suites you run on CI server.
@@ -402,16 +407,18 @@
 ### How does queue mode work?
 
 On the Knapsack Pro API side, there is test file queue generated for your CI build. Each CI node periodically requests the Knapsack Pro API for test files
 that should be executed next. Thanks to that each CI node will finish tests at the same time.
 
+See how it works and what problems can be solved with Queue Mode https://youtu.be/hUEB1XDKEFY
+
 ### How to use queue mode?
 
 Please use a separate API token for queue mode from one used already for regular mode.
 
 Use this command to run queue mode:
 
-    # RSpec
+    # RSpec >= 3.x
     bundle exec rake knapsack_pro:queue:rspec
 
     # Minitest
     bundle exec rake knapsack_pro:queue:minitest