README.md in knapsack_pro-0.15.2 vs README.md in knapsack_pro-0.16.0

@@ -85,10 +85,12 @@
     - [Info for semaphoreapp.com users](#info-for-semaphoreappcom-users)
     - [Info for buildkite.com users](#info-for-buildkitecom-users)
     - [Info for snap-ci.com users](#info-for-snap-cicom-users)
 - [FAQ](#faq)
   - [How to run tests for particular CI node in your development environment](#how-to-run-tests-for-particular-ci-node-in-your-development-environment)
+  - [What happens when Knapsack Pro API is not available/not reachable temporarily?](#what-happens-when-knapsack-pro-api-is-not-availablenot-reachable-temporarily)
+  - [How can I change log level?](#how-can-i-change-log-level)
 - [Gem tests](#gem-tests)
   - [Spec](#spec)
 - [Contributing](#contributing)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
@@ -547,9 +549,21 @@
     KNAPSACK_PRO_CI_NODE_TOTAL=2 \
     KNAPSACK_PRO_CI_NODE_INDEX=0 \
     bundle exec rake "knapsack_pro:rspec[--seed 123]"
 
 Above example is for RSpec. You can use respectively rake task name and token environment variable when you want to run tests for minitest, cucumber or spinach.
+
+### What happens when Knapsack Pro API is not available/not reachable temporarily?
+
+knapsack_pro gem has fallback behaviour and it will split test files across CI nodes based on popular test directory names.
+
+### How can I change log level?
+
+You can change log level by specifying the `KNAPSACK_PRO_LOG_LEVEL` environment variable.
+
+    KNAPSACK_PRO_LOG_LEVEL=warn bundle exec rake knapsack_pro:rspec
+
+Available values are `debug`, `info`, and `warn`. The default log level is `info`.
 
 ## Gem tests
 
 ### Spec