README.md in license_finder-5.10.2 vs README.md in license_finder-5.11.0

@@ -28,11 +28,12 @@
 ### Supported project types
 
 | Project Type | Package Manager | Tested on Version |
 | ------------ | --------------- | -------:|
 | Ruby Gems    | bundler         | 1.16.6  |
-| Python Eggs  | pip             | 19.0.2  |
+| Python 2.7 Eggs  | pip2             | 19.0.2  |
+| Python 3.5 Eggs  | pip3             | 8.1.1  |
 | Node.js      | npm             | 6.4.1   |
 | Bower        | bower           | 1.8.4   |
 | Nuget (without license discovery) | nuget | 4.7.1.5393 |
 | Godep        | Godep           | 80      |
 | Go workspace (via a `.envrc` file) | Go lang | 1.11.5 |
@@ -200,11 +201,11 @@
 
 ## Approving Dependencies
 
 `license_finder` will inform you whenever you have an unapproved dependency.
 If your business decides this is an acceptable risk, the easiest way to approve
-the dependency is by running `license_finder approval add`.
+the dependency is by running `license_finder approvals add`.
 
 For example, let's assume you've added the `awesome_gpl_gem`
 to your Gemfile, which `license_finder` reports is unapproved:
 
 ```sh
@@ -215,20 +216,26 @@
 
 Your business tells you that in this case, it's acceptable to use this
 gem. You now run:
 
 ```sh
-$ license_finder approval add awesome_gpl_gem
+$ license_finder approvals add awesome_gpl_gem
 ```
 
 If you rerun `license_finder`, you should no longer see
 `awesome_gpl_gem` in the output.
 
+To approve specific version
+
+```sh
+$ license_finder approvals add awesome_gpl_gem --version=1.0.0
+```
+
 To record who approved the dependency and why:
 
 ```sh
-$ license_finder approval add awesome_gpl_gem --who CTO --why "Go ahead"
+$ license_finder approvals add awesome_gpl_gem --who CTO --why "Go ahead"
 ```
 
 ### Whitelisting
 
 Approving packages one-by-one can be tedious.  Usually your business has
@@ -277,9 +284,16 @@
 xml-simple, 1.1.1, unknown
 ```
 
 You can customize the format of the output in the same way that you customize
 [output from `report`](#output-from-report).
+
+### Output from `project_roots`
+
+The `license_finder project_roots` command will output the current working directory as a string in an array.
+
+Using the `--recursive` option means the array will include subdirectories that contain a known package manager. With the exception that Gradle and Maven subprojects will not be included.
+
 
 ### Output from `report`
 
 The `license_finder report` command will output human-readable reports that you
 could send to your non-technical business partners, lawyers, etc.  You can