README.md in license_finder-6.5.0 vs README.md in license_finder-6.6.0

@@ -377,11 +377,31 @@
 that has exclusively restricted licenses will always appear in the action
 items, even if someone attempts to manually approve or permit it.  However,
 if a dependency has even one license that is not restricted, it can still be
 manually approved or permitted.
 
+## Decision inheritance
 
+Add or remove decision files you want to inherit from - see `license_finder inherited_decisions help` for more information.
+
+This allows you to have a centralized decision file for approved/restricted licenses. If you have multiple projects it's way easier to have one single place where you approved or restricted licenses defined.
+
+Add one or more decision files to the inherited decisions
+```bash
+license_finder inherited_decisions add DECISION_FILE
+```
+
+Remove one or more decision files from the inherited decisions
+```bash
+license_finder inherited_decisions remove DECISION_FILE
+```
+
+List all the inherited decision files
+```bash
+license_finder inherited_decisions list
+```
+
 ## Configuration
 
 Be default, `license_finder` expects the decisions file to be stored at
 `doc/dependency_decisions.yml`.  All commands can be passed `--decisions_file`
 to override this location.
@@ -464,9 +484,11 @@
 
 `license_finder` requires ruby >= 1.9.3, or jruby.
 
 
 ## Upgrading
+
+To upgrade to `license_finder` version >= 6.0, you have to replace the terminology `whitelist` with `permit` and  `blacklist` with `restrict` in your `dependency_decisions.yml`. See [Changelog](https://github.com/pivotal/LicenseFinder/blob/master/CHANGELOG.md#600--2020-01-22) for more details.
 
 To upgrade from `license_finder` version 1.2 to 2.0, see
 [`license_finder_upgrade`](https://github.com/mainej/license_finder_upgrade).
 To upgrade to 2.0 from a version lower than 1.2, first upgrade to 1.2, and run
 `license_finder` at least once.  This will ensure that the `license_finder`